Is your MCP server
actually healthy?
Thousands of MCP servers are live. Agents pick the ones that respond fast, conform to spec, and document their tools. Paste your streamable-HTTP endpoint — get a real handshake-based score in 10 seconds.
What we check
MCP Pulse speaks the protocol — it doesn't just ping your URL:
initialize handshake, protocol version negotiation, serverInfo identity, declared capabilities.
tools/list round-trip and description coverage — agents choose tools by their descriptions, not their code.
handshake latency, HTTPS, session handling, authentication posture.
Why this matters now
The MCP ecosystem passed 5,800+ community servers in the official registry, with Google and Microsoft shipping their own agent registries. Discovery is exploding — but trust and reliability tooling hasn't kept up. A server with a slow handshake or undocumented tools silently loses agent traffic to a better-run competitor. And if your MCP server is paid, every minute of downtime is lost revenue nobody alerts you about. That's the gap MCP Pulse fills.
Show your score — get a README badge
Once your server scores well, prove it. Drop a live MCP Pulse badge in your README or docs — it re-scans and updates itself, and links back to your full report:
Markdown (swap in your endpoint):
[](https://mcppulse.agiscorecard.com/?url=YOUR_ENDPOINT)
Monitoring (Pro)
$0
Instant scan, unlimited · full conformance report
$19/mo
5-minute uptime + latency checks · schema-drift alerts (tools added/removed/changed) · weekly report · status badge for your README
No charge today — founding price locked when monitoring ships.
$59/mo
10 servers · Slack/webhook alerts · API access
FAQ
Streamable HTTP (the current spec transport), including SSE responses. Legacy SSE-only and stdio servers can't be scanned remotely.
Yes — we detect and report the auth posture (a good sign!). Full introspection of authenticated servers comes with Pro monitoring.
No. Scans run live and aren't persisted in the MVP. Only waitlist emails are stored.