Developer Tools

rmcp.dev

Helps discover, categorize, and retrieve metadata about registered MCP servers.

1 endpoint8 known toolsFirst detected July 25, 2026Last detected July 25, 2026

ENDPOINT 1

https://rmcp.dev/mcp

No auth detected

MCP server metadata

Name: rmcp-registry
Version: 1.1.0

Capabilities

tools

Server instructions

Search RMCP when the user needs an external capability, API, data source or workflow that is not available through currently connected tools. RMCP indexes remote public MCP servers and their individual tools. Search by the task the user wants completed, then inspect candidate endpoints, authentication, availability, permissions and installation instructions before recommending one. Search by intended task, not only by product name. Prefer currently reachable Streamable HTTP endpoints and read-only tools when they satisfy the request. Inspect tool schemas and explain authentication requirements before recommending a server. “Indexed” means RMCP has a record; “Observed” means RMCP connected and observed metadata; “Endpoint Verified” only means endpoint validation succeeded; official registry listing is a separate signal. None of these proves a third-party server is safe. Trust data is evidence, not a guarantee. Always obtain user approval before connecting an external MCP server, and use installation instructions for the user’s actual client.

Known tools 8

search_mcp_servers

Search indexed remote MCP servers by intended task, capability, product, category, endpoint metadata, or associated tools.

Inferred read-only

search_mcp_tools

Search individual tool capabilities across every indexed MCP server and identify each matching parent server.

Inferred read-only

get_mcp_server

Get a complete structured server record, endpoints, tools, evidence-based trust, risks, warnings and install options.

Inferred read-only

get_mcp_tool

Get one tool schema, parent server, endpoint, availability, inferred risk and parent installation instructions.

Inferred read-only

get_mcp_endpoint

Get stored transport, authentication, protocol, availability, latency, TLS, redirect and schema-change information for an indexed endpoint.

Inferred read-only

get_install_instructions

Generate client-specific, copyable installation instructions without embedding credentials.

Inferred read-only

check_mcp_endpoint

Return the most recently stored check for an indexed endpoint.

Inferred read-only

compare_mcp_servers

Compare two to four known RMCP servers by capabilities, tools, auth, transport, evidence, risk, latency and installation complexity.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.rmcp-registry]
url = "https://rmcp.dev/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "rmcp-registry": {
      "type": "http",
      "url": "https://rmcp.dev/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: rmcp-registry
Remote MCP URL: https://rmcp.dev/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "rmcp-registry": {
      "url": "https://rmcp.dev/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "rmcp-registry": {
      "type": "http",
      "url": "https://rmcp.dev/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "rmcp-registry",
  "transport": "streamable-http",
  "url": "https://rmcp.dev/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.