MCP Rating
REMOTE · MCPRATING.IO · 2 COMPONENTS
Search MCP servers, with our own start-test results, required keys, tools and token cost.
Available components
Last scanned (12 hours ago)
Scores higher than 88% of remote servers
Reachable. Last reached 6 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 Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability87
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 586 tokens (~73/item across 8 items; 6 tools + 2 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 Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
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.
- 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
- 29 Oct 26 +1
- Stability: 0.97 → pass security
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
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 6 Nov 2026 · Probed https://mcprating.io/mcp/sse
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcprating.io | CN=YE1,O=Let's Encrypt,C=US | 20 Oct 2026 | 18 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 688693ed4ea67cbde1b11561790d01649d0 |
| SANs: *.mcprating.io, mcprating.io | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| 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 insecure
Validation of mcprating.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| io. | DS published | 38690 | 8 | Verified |
| mcprating.io. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
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 |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| sse | https://mcprating.io/mcp/sse | Verified | 200 | |
| http (plaintext) | http://mcprating.io/mcp/sse | HTTPS enforced | 301 | https://mcprating.io/mcp/sse |
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 →
discover_server Fetch a server's discovery manifest ~59
Fetch the live .well-known/mcp discovery manifest from an indexed MCP server. Returns transport endpoints, capabilities, and auth requirements needed to connect. Only works for servers that support MCP discovery.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | The server's unique slug identifier |
No output schema declared.
No examples provided.
get_index_stats Get index statistics ~29
Get overall statistics about the MCP Rating index: total servers, top categories, and last crawl time.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_install_config Get install config ~101
Generate a ready-to-paste configuration snippet for connecting a discovered MCP server to Claude Desktop or Cursor. MCP servers cannot auto-install — users must manually add configuration. This tool reduces that friction.
| Name | Type | Req | Description |
|---|---|---|---|
| client | string | – | Target client (default: claude_desktop). 'generic' returns a transport-neutral {command,args,env} object; 'surge' returns the Surge install shape. |
| slug | string | yes | The server's unique slug identifier |
No output schema declared.
No examples provided.
get_server Get MCP server details ~108
Get what is known about one MCP server by slug: whether it started when we ran it ourselves (no credentials, on a schedule), how it is maintained (last release, last code push, open issues, archived or deprecated), how to run it (install command or hosted endpoint), the keys it declares, its tools with their parameters, and roughly how many tokens its tool definitions cost. Listings are informational — verify details before installing.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | The server's unique slug identifier |
No output schema declared.
No examples provided.
list_categories List server categories ~22
List all available MCP server categories with the count of servers in each.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
search_servers Search MCP servers ~136
Search the MCP Rating index of MCP servers. Returns matches for a query, optionally filtered by category and sorted by quality, stars, downloads, recency, or name, each marked with the outcome of our own start test when we have run one, and with its last release and last code push dates where we know them. Quality scores are algorithmic estimates.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Category slug to filter by (e.g. 'developer-tools') |
| limit | number | – | Max results (default 20) |
| query | string | – | Search query to match against server names |
| sortBy | string | – | Sort order |
No output schema declared.
No examples provided.
How do I install the MCP Rating server?
MCP Rating is a hosted endpoint at https://mcprating.io/mcp/sse, 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 · mcprating.io
claude mcp add --transport http io-mcprating-search 'https://mcprating.io/mcp/sse'
What is the MCP Rating server?
MCP Rating is listed in the public MCP registry as io.mcprating/search. Search MCP servers, with our own start-test results, required keys, tools and token cost. This page covers its hosted endpoint (https://mcprating.io/mcp/sse).
Is the MCP Rating server safe to use?
MCP Rating scores 84 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 MCP Rating server expose?
MCP Rating exposes 6 tools: search_servers, get_server, list_categories, get_index_stats, get_install_config, discover_server. Their descriptions and schemas cost roughly 455 tokens of context every time the server is loaded.
Does the MCP Rating server require authentication?
No. We connected to MCP Rating without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the MCP Rating server still maintained?
MCP Rating is still listed as active in the MCP registry. We last reached this channel on 6 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 MCP Rating server?
VerifyMCP ran 13 checks on MCP Rating, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. 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.