RMCP
REMOTE · RMCP.DEV
Search remote Model Context Protocol servers and tools discovered by BuiltWith, without an API key.
Available components
Last scanned (21 hours ago)
Scores higher than 65% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Search and Retrieval
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security66
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 8 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability67
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 598 tokens (~74/item across 8 items; 8 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage68
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 5% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Checks we ran (12)
- TLS certificate
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 8 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 14 Nov 26 +10
- Transport: fail → pass ▲ security
- 13 Nov 26 −10
- Transport: pass → fail ▼ security
- 9 Nov 26 0
- Stability: 0.97 → pass security
- 8 Nov 26 0
- Stability: pass → 0.97 functional
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Probed https://rmcp.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=rmcp.dev | CN=YE2,O=Let's Encrypt,C=US | 15 Oct 2026 | 13 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 6dc796e280414d9e69a44f18542c2ac73bb |
| SANs: rmcp.dev, www.rmcp.dev | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of rmcp.dev. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | DS published | 60074 | 8 | Verified |
| rmcp.dev. | DS published | 52198 | 13 | Verified |
| rmcp.dev. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| content-security-policy | default-src 'self';base-uri 'self';font-src 'self';form-action 'self';frame-ancestors 'self';img-src 'self' data: https://www.google.com https://t2.gstatic.com;object-src 'none';script-src 'self';script-src-attr 'none';style-src 'self';upgrade-insecure-requests;connect-src 'self' |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | no-referrer |
| permissions-policy | tools=(self) |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://rmcp.dev/mcp | Verified | 200 | |
| http (plaintext) | http://rmcp.dev/mcp | HTTPS enforced | 301 | https://rmcp.dev/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_mcp_endpoint ~35
Return the most recently stored check for an indexed endpoint. This never scans an arbitrary URL.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
No output schema declared.
No examples provided.
compare_mcp_servers ~58
Compare two to four known RMCP servers by capabilities, tools, auth, transport, evidence, risk, latency and installation complexity.
| Name | Type | Req | Description |
|---|---|---|---|
| ids | array | yes | – |
| query | string | – | Optional intended capability used to select relevant tools. |
No output schema declared.
No examples provided.
get_install_instructions ~45
Generate client-specific, copyable installation instructions without embedding credentials.
| Name | Type | Req | Description |
|---|---|---|---|
| client | string | yes | – |
| endpoint_index | integer | – | – |
| server_id | string | yes | – |
No output schema declared.
No examples provided.
get_mcp_endpoint ~41
Get stored transport, authentication, protocol, availability, latency, TLS, redirect and schema-change information for an indexed endpoint.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
No output schema declared.
No examples provided.
get_mcp_server ~39
Get a complete structured server record, endpoints, tools, evidence-based trust, risks, warnings and install options.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
No output schema declared.
No examples provided.
get_mcp_tool ~36
Get one tool schema, parent server, endpoint, availability, inferred risk and parent installation instructions.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
No output schema declared.
No examples provided.
search_mcp_servers ~92
Search indexed remote MCP servers by intended task, capability, product, category, endpoint metadata, or associated tools.
| Name | Type | Req | Description |
|---|---|---|---|
| authentication | string | – | – |
| category | string | – | – |
| limit | integer | – | – |
| online_only | boolean | – | – |
| query | string | yes | – |
| read_only_only | boolean | – | – |
| transport | string | – | – |
| verified_only | boolean | – | – |
No output schema declared.
No examples provided.
search_mcp_tools ~64
Search individual tool capabilities across every indexed MCP server and identify each matching parent server.
| Name | Type | Req | Description |
|---|---|---|---|
| authentication | string | – | – |
| limit | integer | – | – |
| online_only | boolean | – | – |
| query | string | yes | – |
| read_only_only | boolean | – | – |
No output schema declared.
No examples provided.
How do I install the RMCP MCP server?
RMCP is a hosted endpoint at https://rmcp.dev/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · rmcp.dev
claude mcp add --transport http dev-rmcp-rmcp 'https://rmcp.dev/mcp'
What is the RMCP MCP server?
RMCP is an MCP server listed in the public MCP registry as dev.rmcp/rmcp. Search remote Model Context Protocol servers and tools discovered by BuiltWith, without an API key. This page covers its hosted endpoint (https://rmcp.dev/mcp).
Is the RMCP MCP server safe to use?
RMCP scores 76 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the RMCP MCP server expose?
RMCP exposes 8 tools: search_mcp_servers, search_mcp_tools, get_mcp_server, get_mcp_tool, get_mcp_endpoint, and 3 more. Their descriptions and schemas cost roughly 410 tokens of context every time the server is loaded.
Does the RMCP MCP server require authentication?
No. We connected to RMCP without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the RMCP MCP server still maintained?
RMCP is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the RMCP MCP server?
VerifyMCP ran 12 checks on RMCP, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about RMCP: Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.