SutramX MCP server monitors check remote Model Context Protocol servers over Streamable HTTP: they run the initialize handshake, negotiate the protocol version (2024-11-05 to 2025-11-25) and list the tools. They alert on protocol errors, version mismatches, missing expected tools and tool-list or schema drift, and never call a tool. On every plan.
What a check does
Each check connects to your server's HTTPS endpoint, sends initialize, negotiates a protocol version between 2024-11-05 and 2025-11-25 (or requires the exact one you set) and calls tools/list. The result is graded against what you expect: no protocol errors, an acceptable version, the expected tools present, and no unapproved change to the tool list.
- Protocol errorsMalformed responses or JSON-RPC errors during the handshake.
- Version mismatchThe server does not offer the protocol version you require.
- Missing toolsA tool you listed as expected is not in tools/list.
- Tool driftTool names, or their schemas if you choose, changed since the accepted baseline.
Authentication
Send a static bearer token or other header with every check. For servers that use OAuth, issue a token for monitoring and add it as a bearer header.
Specifications
| Plans | Every plan, including Free |
|---|---|
| Transport | Streamable HTTP over HTTPS |
| Protocol versions | 2024-11-05 to 2025-11-25 |
| Checks | initialize, version negotiation, tools/list (tools are never called) |
| Drift | Tool names or full schemas; degraded (default) or down |
| Auth | Static headers, such as a bearer token |
Learn more
- Guides: How to Monitor MCP Servers and Monitoring APIs Effectively
- Use cases: Monitoring for Developers & Indie Hackers
- Documentation: MCP servers and MCP server for AI tools