mcpbeat

ResolveMesh Compatibility Intelligence MCP Server

com.resolvemesh/compatibility
not responding

ResolveMesh Compatibility Intelligence is listed as active in the registry but did not answer our last check. It exposes 2 tools.

Read-only, source-backed compatibility lookups and approved changes for ResolveMesh's catalog.

Uptime history 41 hours of history · worst hour 0%
41 hours agonow
2.2%
Uptime 24h
2 of 91 checks
2
Tools
read from the server
373 ms
Response time
average over 24h
open, no key
Access
streamable-http

Connect this server

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

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

Available tools 2

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

compatibility
compatibility_changes
Return cursor-paginated, approved ResolveMesh compatibility events using the same allowlisted filters as the public JSON API.
compatibility_lookup
Return the source-backed ResolveMesh compatibility result for one allowlisted client and hosted-tool pair.

Endpoints

URLTransportStateLatencyChecked
https://resolvemesh.com/mcp/public streamable-http answering 242 ms 7 min ago

ResolveMesh Compatibility Intelligence — questions

Answers built from our own checks of this server.

What can ResolveMesh Compatibility Intelligence do?
It exposes 2 tools, read directly from the server on our last check. Among them: compatibility_changes, compatibility_lookup. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is ResolveMesh Compatibility Intelligence working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 2 of 91 checks got a reply (2.2%), average response time 373 ms. The bar chart above shows every period we have measured.
The registry lists ResolveMesh Compatibility Intelligence as active — why does it not respond?
The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.
How do I connect ResolveMesh Compatibility Intelligence?
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.
Does ResolveMesh Compatibility Intelligence need an API key?
No. ResolveMesh Compatibility Intelligence completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 2 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is ResolveMesh Compatibility Intelligence?
It answers our handshake in 373 ms on average, which is faster than 37% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.