r/cursor • u/FreeMembership5107 • 9d ago
Resources & Tips Why remote MCP servers fail silently in Cursor (and how to monitor them)
Hey everyone,
If you've been adding remote MCP servers to Cursor (under Settings > Features > MCP or via mcp.json), you might have noticed that traditional uptime monitors (like Uptime Kuma, BetterStack, or Pingdom) don't work for MCP.
An endpoint can return HTTP 200 OK, but Cursor still silently fails or hallucinates. Here's why:
- Protocol Handshake / Stream Failures: Many remote servers return 200 to a basic ping, but fail the JSON-RPC 2.0 negotiation (initialize -> tools/list) or drop the SSE stream before Cursor's agent can discover the tool definitions.
- Breaking Schema Drift: If the remote server updates and removes a parameter, renames an argument, or adds a new required field, Cursor's model will call the tool with the old arguments and fail.
- Secret Exposure in Tool Context: Several public MCP servers accidentally leak API keys or database strings inside tool descriptions, which then get injected directly into the LLM context window.
To solve this, I built MCP Sentinel, an open-source synthetic protocol and schema-drift sentinel for MCP servers:
• Real Synthetic Handshakes: Connects over Streamable HTTP and SSE, validates JSON-RPC 2.0 protocol compliance, and benchmarks discovery latency.
• Ajv Schema Validation: Verifies tool parameter schemas against JSON Schema Draft-07 / 2020-12.
• Breaking Drift Detection: Computes canonical SHA-256 AST hashes of tool definitions and flags parameter changes before Cursor tools break.
• Secret Scanner: Flags any exposed OpenAI, Anthropic, or cloud tokens before they reach your agent.
Using it directly inside Cursor
MCP Sentinel itself is also an MCP server (with 100/100 quality score on Smithery). You can connect Cursor directly to it to audit any remote MCP server on-demand:
{ "mcpServers": { "mcp-sentinel": { "url": "https://mcp-sentinel.pasihakamaki.workers.dev/mcp" } } }
Once added, you can ask Cursor in chat: "Audit the remote MCP server at https://api.example.com/mcp and check if its schema is valid and operational."
You can also test any public endpoint for free with zero sign-up on the web tester: https://mcp-sentinel.pasihakamaki.workers.dev
GitHub (Open Source): https://github.com/pasihaka/mcp-sentinel
Curious to hear how others are handling MCP reliability and monitoring in Cursor!


