VerifyMCP
Owner verifiedREMOTE · MCP.VERIFYMCP.IO
Independent trust scores, tool surfaces and change history for MCP servers.
Available components
Last scanned (10 hours ago)
Scores higher than 99% of remote servers
Reachable. Last reached 22 Oct 2026.
Category Security
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 Security100
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- 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
- The authorisation server supports Client ID Metadata Documents, the current MCP client-registration mechanism. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability96
- 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 1263 tokens (~60/item across 21 items; 9 tools + 12 resources), lean.Pass
- Tools include usage examples.Pass
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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
- Supports UI / widget rendering.Pass
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.
- 17 Oct 26 0
- Tool “get_server_alternatives” rewrote its description, which is the text the model reads security
- 4 Oct 26 0
- Stability: 0.97 → pass security
- 3 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Sept 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.
- 28 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Sept 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.
- 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
- 24 Sept 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.
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 22 Oct 2026 · Probed https://mcp.verifymcp.io
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=verifymcp.io | CN=WE1,O=Google Trust Services,C=US | 24 Aug 2026 | 22 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 5fe9a089f5677e820ecfce18b444b6f9 |
| SANs: verifymcp.io, *.verifymcp.io | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of mcp.verifymcp.io. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 8 | Verified |
| verifymcp.io. | present | 2371 | 13 | Verified |
| mcp.verifymcp.io. | Verified address RRset verified with the apex keys |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer error="invalid_token", error_description="Missing Authorization header", scope="directory:read", resource_metadata="https://mcp.verifymcp.io/.well-known/oauth-protected-resource"
Bearer error="invalid_token", error_description="Missing Authorization header", scope="directory:read", resource_metadata="https://mcp.verifymcp.io/.well-known/oauth-protected-resource"| Header | Value |
|---|---|
| strict-transport-security | max-age=15552000; includeSubDomains; preload |
| x-content-type-options | nosniff |
Protected resource metadata
| Document | https://mcp.verifymcp.io/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | Yes |
| Resource | https://mcp.verifymcp.io |
| Authorisation server | https://verifymcp.io |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.verifymcp.io | Verified | 200 | |
| http (plaintext) | http://mcp.verifymcp.io | HTTPS enforced | 308 | https://mcp.verifymcp.io/ |
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 →
get_server Get MCP server trust report ~110
Get the full VerifyMCP trust report for one MCP server: score with per-category verdicts and reasons, the tools it exposes with their context-token cost, and its recent change history. Use before installing or trusting a server. Accepts a package name, endpoint URL, registry name or verifymcp slug.
| Name | Type | Req | Description |
|---|---|---|---|
| component | string | – | Which channel to report on when a server ships several. |
| identifier | string | yes | Package name, endpoint URL, registry name or verifymcp slug. |
| Name | Type | Req | Description |
|---|---|---|---|
| asOf | string | yes | When this data was read (UTC). |
| count | integer | yes | Number of entries in items. |
| items | array | yes | – |
| notice | string|null | yes | How to narrow a truncated result, or why an empty one is empty; null when neither applies. |
| source | string | yes | Canonical verifymcp.io page for this result. |
| total | integer | yes | Matches before the 100-item cap. |
| truncated | boolean | yes | True when total exceeds count. |
{"identifier":"@modelcontextprotocol/server-github"}{"identifier":"https://mcp.example.com/mcp"}{"component":"npm","identifier":"io.github.acme/tools"}{"identifier":"acme-tools"}get_server_alternatives Find alternative MCP servers ~67
Other MCP servers doing a similar job to a given one, with their trust scores. Neighbours share a product, publisher namespace or category; this is not a semantic search.
| Name | Type | Req | Description |
|---|---|---|---|
| identifier | string | yes | Package name, endpoint URL, registry name or verifymcp slug. |
| Name | Type | Req | Description |
|---|---|---|---|
| asOf | string | yes | When this data was read (UTC). |
| count | integer | yes | Number of entries in items. |
| items | array | yes | – |
| notice | string|null | yes | How to narrow a truncated result, or why an empty one is empty; null when neither applies. |
| source | string | yes | Canonical verifymcp.io page for this result. |
| total | integer | yes | Matches before the 100-item cap. |
| truncated | boolean | yes | True when total exceeds count. |
{"identifier":"@modelcontextprotocol/server-github"}{"identifier":"https://mcp.example.com/mcp"}{"identifier":"acme-tools"}get_server_comparison Compare MCP servers ~86
Compare up to 5 MCP servers side by side: trust scores, per-category breakdown, tool counts and context-token cost. Use when choosing between candidates that do the same job. Accepts package names, endpoint URLs, registry names or verifymcp slugs.
| Name | Type | Req | Description |
|---|---|---|---|
| identifiers | array | yes | Two to 5 servers to compare, as names, URLs or slugs. |
| Name | Type | Req | Description |
|---|---|---|---|
| asOf | string | yes | When this data was read (UTC). |
| count | integer | yes | Number of entries in items. |
| items | array | yes | – |
| notice | string|null | yes | How to narrow a truncated result, or why an empty one is empty; null when neither applies. |
| source | string | yes | Canonical verifymcp.io page for this result. |
| total | integer | yes | Matches before the 100-item cap. |
| truncated | boolean | yes | True when total exceeds count. |
{"identifiers":["@acme/mcp-server","@other/mcp-server"]}{"identifiers":["acme-tools","beta-tools","gamma-tools"]}get_server_diagnostics Get MCP server diagnostics ~86
The evidence behind one server's score: TLS, DNSSEC, authorization, redirects, transports, provenance, install scripts, known CVEs and dependency health. Use to explain a low score.
| Name | Type | Req | Description |
|---|---|---|---|
| component | string | – | Which channel to report on when a server ships several. |
| identifier | string | yes | Package name, endpoint URL, registry name or verifymcp slug. |
| Name | Type | Req | Description |
|---|---|---|---|
| asOf | string | yes | When this data was read (UTC). |
| count | integer | yes | Number of entries in items. |
| items | array | yes | – |
| notice | string|null | yes | How to narrow a truncated result, or why an empty one is empty; null when neither applies. |
| source | string | yes | Canonical verifymcp.io page for this result. |
| total | integer | yes | Matches before the 100-item cap. |
| truncated | boolean | yes | True when total exceeds count. |
{"identifier":"@modelcontextprotocol/server-github"}{"identifier":"https://mcp.example.com/mcp"}{"component":"npm","identifier":"io.github.acme/tools"}get_server_install_config Get MCP server install config ~109
Ready-to-paste install snippets for one MCP server, for every client we support. An MCPB bundle has no launch command, so it returns the download URL, the registry's SHA-256 and commands to verify the file instead. Read get_server first: this returns configuration, not a safety judgement.
| Name | Type | Req | Description |
|---|---|---|---|
| component | string | – | Which channel to report on when a server ships several. |
| identifier | string | yes | Package name, endpoint URL, registry name or verifymcp slug. |
| Name | Type | Req | Description |
|---|---|---|---|
| asOf | string | yes | When this data was read (UTC). |
| bundle | object|null | yes | MCPB bundles only (null otherwise): the file to download, the SHA-256 the registry declares for it, and commands that check the download against it. Open the verified file with an MCPB-capable host s… |
| context | object|null | yes | What we know about the server being installed. Present whenever a server resolved, including when no snippets could be built; null only when the identifier matched nothing. |
| count | integer | yes | Number of entries in items. |
| items | array | yes | – |
| notice | string|null | yes | How to narrow a truncated result, or why an empty one is empty; null when neither applies. |
| source | string | yes | Canonical verifymcp.io page for this result. |
| total | integer | yes | Matches before the 100-item cap. |
| truncated | boolean | yes | True when total exceeds count. |
{"identifier":"@modelcontextprotocol/server-github"}{"identifier":"https://mcp.example.com/mcp"}{"component":"npm","identifier":"acme-tools"}get_server_tools List an MCP server's tools ~76
Every tool one MCP server exposes, with its parameters, output schema and context-token cost. Use when get_server reported the tool list was truncated.
| Name | Type | Req | Description |
|---|---|---|---|
| component | string | – | Which channel to report on when a server ships several. |
| identifier | string | yes | Package name, endpoint URL, registry name or verifymcp slug. |
| Name | Type | Req | Description |
|---|---|---|---|
| asOf | string | yes | When this data was read (UTC). |
| count | integer | yes | Number of entries in items. |
| items | array | yes | – |
| notice | string|null | yes | How to narrow a truncated result, or why an empty one is empty; null when neither applies. |
| source | string | yes | Canonical verifymcp.io page for this result. |
| total | integer | yes | Matches before the 100-item cap. |
| truncated | boolean | yes | True when total exceeds count. |
{"identifier":"@modelcontextprotocol/server-github"}{"identifier":"https://mcp.example.com/mcp"}{"component":"npm","identifier":"acme-tools"}list_known_malware List known malware ~59
List MCP server components carrying a supply-chain malware finding. Use to check whether anything in the register is flagged before installing.
| Name | Type | Req | Description |
|---|---|---|---|
| status | string | – | Which findings to return: active, unverified, cleared or all. Defaults to active. |
| Name | Type | Req | Description |
|---|---|---|---|
| asOf | string | yes | When this data was read (UTC). |
| count | integer | yes | Number of entries in items. |
| items | array | yes | – |
| notice | string|null | yes | How to narrow a truncated result, or why an empty one is empty; null when neither applies. |
| source | string | yes | Canonical verifymcp.io page for this result. |
| total | integer | yes | Matches before the 100-item cap. |
| truncated | boolean | yes | True when total exceeds count. |
{}{"status":"active"}{"status":"all"}list_products List products ~57
List the products MCP servers integrate with, such as github or notion, and how many servers cover each. Use to find the product slug that list_servers accepts.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | – | Name fragment to match against product names and slugs. |
| Name | Type | Req | Description |
|---|---|---|---|
| asOf | string | yes | When this data was read (UTC). |
| count | integer | yes | Number of entries in items. |
| items | array | yes | – |
| notice | string|null | yes | How to narrow a truncated result, or why an empty one is empty; null when neither applies. |
| source | string | yes | Canonical verifymcp.io page for this result. |
| total | integer | yes | Matches before the 100-item cap. |
| truncated | boolean | yes | True when total exceeds count. |
{}{"query":"git"}{"query":"notion"}list_servers List MCP servers ~188
Filter the VerifyMCP directory of scored MCP servers. Use to discover servers by name fragment, ecosystem, product or trust score. Name matching only: descriptions and capabilities are not searched, so a plain-English question matches nothing. Returns the first 100.
| Name | Type | Req | Description |
|---|---|---|---|
| maxScore | integer | – | Highest trust score to include. |
| minScore | integer | – | Lowest trust score to include. |
| product | string | – | Restrict to servers classified as working with this product, e.g. github. |
| query | string | – | Name fragment to match against server and package names. |
| scored | string | – | Include unscored servers. Defaults to scored only. |
| sort | string | – | Default: best match (then trust) with a query, else trust. A given sort is applied exactly. |
| types | array | – | Restrict to these ecosystems; a server matches any one of them. |
| Name | Type | Req | Description |
|---|---|---|---|
| asOf | string | yes | When this data was read (UTC). |
| count | integer | yes | Number of entries in items. |
| items | array | yes | – |
| notice | string|null | yes | How to narrow a truncated result, or why an empty one is empty; null when neither applies. |
| source | string | yes | Canonical verifymcp.io page for this result. |
| total | integer | yes | Matches before the 100-item cap. |
| truncated | boolean | yes | True when total exceeds count. |
{"query":"github"}{"minScore":70,"product":"github"}{"minScore":80,"sort":"score_desc","types":["remote"]}{"scored":"scored","types":["npm","pypi"]}{"query":"postgres","types":["npm"]}How do I install the VerifyMCP MCP server?
VerifyMCP is a hosted endpoint at https://mcp.verifymcp.io/, 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 · mcp.verifymcp.io
claude mcp add --transport http io-verifymcp-mcp 'https://mcp.verifymcp.io/'
What is the VerifyMCP MCP server?
VerifyMCP is an MCP server listed in the public MCP registry as io.verifymcp/mcp. Independent trust scores, tool surfaces and change history for MCP servers. This page covers its hosted endpoint (https://mcp.verifymcp.io). Its publisher has verified ownership with us.
Is the VerifyMCP MCP server safe to use?
VerifyMCP scores 99 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 VerifyMCP MCP server expose?
VerifyMCP exposes 9 tools: list_servers, get_server, get_server_comparison, list_products, list_known_malware, and 4 more. Their descriptions and schemas cost roughly 838 tokens of context every time the server is loaded.
Does the VerifyMCP MCP server require authentication?
Yes. VerifyMCP asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the VerifyMCP MCP server still maintained?
VerifyMCP is still listed as active in the MCP registry. We last reached this channel on 22 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.