mcpbeat Sign in

Mcpulse MCP Server

by getmcpulse Your server? Claim it
answering

Mcpulse is answering right now. Last checked 1 min ago.

Analytics for MCP servers. Query your tool calls, first-call success, retries and schema cost.

Uptime history 55 days of history · worst day 0%
55 days agonow
100.0%
Uptime 24h
92 of 92 checks
—
Tools
hidden behind auth
276 ms
Response time
average over 24h
OAuth sign-in
Access
streamable-http

Mcpulse does not always answer

Over the last week it answered 89.9% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

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 1 min ago.

run in your terminal
claude mcp add mcpulse --transport http https://api.getmcpulse.com/mcp
Settings → Connectors → Add custom connector, then paste this address
https://api.getmcpulse.com/mcp
~/.codex/config.toml
[mcp_servers.mcpulse]
url = "https://api.getmcpulse.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "mcpulse": {
      "url": "https://api.getmcpulse.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "mcpulse": {
      "type": "http",
      "url": "https://api.getmcpulse.com/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://api.getmcpulse.com/mcp streamable-http sign-in 276 ms 1 min ago

Alternatives to Mcpulse

same job, measured the same way
Wireboard
by wireboard

Official MCP server for WireBoard. Lets LLM agents query your analytics in conversation.

47 installs/wk local only
Nvoip MCP Server
by com-nvoip

Secure Nvoip MCP server for reports, call analytics, service quality, and business insights.

answering
yandex-metrika-mcp
by theyahia

MCP server for Yandex Metrika — web analytics, counters, goals, traffic (Russia)

125 installs/wk local only
Yandex Metrica MCP
by askads

MCP server for Yandex Metrica API: list counters, goals and pull web-analytics statistics.

195 installs/wk local only
Google Analytics 4
by mindstone

Google Analytics 4 MCP server with reporting, schema discovery, and admin visibility tools

64 installs/wk local only
Yandex Webmaster MCP
by stufently

MCP server for Yandex Webmaster API — site analytics, indexing, search queries

82 installs/wk local only
Scanduro
by sssnl-nl

Remote MCP server for Scanduro QR codes, scan analytics and controlled code actions.

answering
Framedash MCP Server
by crane-valley

MCP server for Framedash game telemetry: query analytics, heatmaps, perf regressions, and alerts

62 installs/wk local only

Mcpulse — questions

Answers built from our own checks of this server.

Why is there no tool list for Mcpulse?
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 Mcpulse working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 276 ms. The bar chart above shows every period we have measured.
How do I connect Mcpulse?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form 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 Mcpulse?
No API key is involved. Mcpulse 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 Mcpulse?
It answers our handshake in 276 ms on average, which is faster than 52% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.