mcpbeat Sign in

Tá Rodando MCP Server

by com-tarodando Your server? Claim it
answering

Tá Rodando is answering right now. Last checked 15 min ago.

Uptime monitoring and public status page: HTTP monitors, down/up alerts and incidents.

Uptime history 5 days of history
5 days agonow
100.0%
Uptime 24h
91 of 91 checks
—
Tools
hidden behind auth
288 ms
Response time
average over 24h
OAuth sign-in
Access
streamable-http

Nothing serious here today

Today is the operative word: we check Tá Rodando every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 15 min ago.

run in your terminal
claude mcp add mcp --transport http https://tarodando.com.br/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "mcp": {
      "url": "https://tarodando.com.br/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.mcp]
url = "https://tarodando.com.br/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "mcp": {
      "url": "https://tarodando.com.br/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "mcp": {
      "url": "https://tarodando.com.br/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.

Endpoints

URLTransportStateLatencyChecked
https://tarodando.com.br/mcp streamable-http sign-in 258 ms 15 min ago

Alternatives to Tá Rodando

same job, measured the same way
StatOSS
by statoss

Status pages and uptime monitoring: read status, monitors and incidents; open incidents.

answering
Uptimely
by getuptimely

Uptime monitoring: monitors, incidents, alerts, maintenance, on-call, status pages and telemetry.

answering
SutramX
by sutramx

SutramX uptime monitoring: monitors, check results, incidents, status pages and uptime/SLO reports.

361 installs/wk local only
Vantaj
by vantaj

Vantaj uptime monitoring via MCP - manage monitors, heartbeats, incidents, and status pages.

13 tools answering
Fettle
by fettle

Uptime monitoring for developers — monitors, incidents, heartbeats and status pages

180 installs/wk answering
Uptimepage
by uptimepage

Monitor uptime and incidents, run checks, and publish status updates from your Uptimepage org.

37 tools answering
SolidPing
by fclairamb

Self-hostable uptime monitoring: create checks, read incidents, manage status pages.

answering
Xitoring
by xitoring

Connect AI assistants to Xitoring monitoring: servers, uptime, incidents, metrics, SSL, and alerts.

answering

Tá Rodando — questions

Answers built from our own checks of this server.

Why is there no tool list for Tá Rodando?
The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.
Is Tá Rodando working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 288 ms. The bar chart above shows every period we have measured.
How do I connect Tá Rodando?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You sign in through your browser once and the client keeps the session: no key to copy, and it refuses anonymous clients.
How do you sign in to Tá Rodando?
No API key is involved. Tá Rodando answers our knock with an OAuth challenge, so you authorise it once in your browser and the client keeps the session. That is also why we see no tool list: it will not describe itself to an anonymous client, and that is the server working as intended, not a fault.
How fast is Tá Rodando?
It answers our handshake in 288 ms on average, which is faster than 49% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.