# VerifyMCP (remote · mcp.verifymcp.io)

Independent trust scores, tool surfaces and change history for MCP servers.

- Trust score: 87/100 (high trust)
- Registry status: active
- Liveness: live
- Owner verified: yes
- Last scored: 2026-09-07

## Components

- remote · `mcp.verifymcp.io`: 87/100 (this document), [markdown](https://verifymcp.io/servers/io-verifymcp-mcp/mcp.md), [page](https://verifymcp.io/servers/io-verifymcp-mcp/mcp)

## Channel facts

- Endpoint: `https://mcp.verifymcp.io`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-07.

- **Endpoint Security**: 100/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
  - The authorisation server supports Client ID Metadata Documents, the current MCP client-registration mechanism.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 97/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 1219 tokens (~58/item across 21 items; 9 tools + 12 resources), lean.
  - Tools include usage examples.
- **Stability & Change Management**: 10/100
  - Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).
  - Supports UI / widget rendering.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http io-verifymcp-mcp 'https://mcp.verifymcp.io/'
```

### Cursor

```json
{
  "mcpServers": {
    "io-verifymcp-mcp": {
      "url": "https://mcp.verifymcp.io/"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "io-verifymcp-mcp": {
      "type": "http",
      "url": "https://mcp.verifymcp.io/"
    }
  }
}
```

### Codex

```toml
[mcp_servers.io-verifymcp-mcp]
url = "https://mcp.verifymcp.io/"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-verifymcp-mcp": {
      "type": "remote",
      "url": "https://mcp.verifymcp.io/",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add io-verifymcp-mcp --url 'https://mcp.verifymcp.io/' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-verifymcp-mcp:
    url: "https://mcp.verifymcp.io/"
```

### Netclaw

```json
{
  "McpServers": {
    "io-verifymcp-mcp": {
      "Transport": "http",
      "Url": "https://mcp.verifymcp.io/"
    }
  }
}
```

### Vellum

```bash
assistant mcp add io-verifymcp-mcp -t streamable-http -u 'https://mcp.verifymcp.io/'
```

### Other

```json
{
  "mcpServers": {
    "io-verifymcp-mcp": {
      "type": "http",
      "url": "https://mcp.verifymcp.io/"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-07 (score 87, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-05 (score 86, +5)

- [security improvement] HTTPS: unverified → pass
- [functional improvement] Stability: unverified → 0.03

### 2026-09-04 (score 81)

First indexed and scored.

## MCP tools (9)

### `list_servers` (~176 tokens)

List MCP servers

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.

Input parameters:

- `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): Result ordering; relevance wins when query is set.
- `types` (array): Restrict to these ecosystems; a server matches any one of them.

Output parameters:

- `asOf` (string): When this data was read (UTC).
- `count` (integer): Number of entries in items.
- `items` (array)
- `notice` (string|null): How to narrow a truncated result, or why an empty one is empty; null when neither applies.
- `source` (string): Canonical verifymcp.io page for this result.
- `total` (integer): Matches before the 100-item cap.
- `truncated` (boolean): True when total exceeds count.

### `get_server` (~110 tokens)

Get MCP server trust report

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.

Input parameters:

- `component` (string): Which channel to report on when a server ships several.
- `identifier` (string, required): Package name, endpoint URL, registry name or verifymcp slug.

Output parameters:

- `asOf` (string): When this data was read (UTC).
- `count` (integer): Number of entries in items.
- `items` (array)
- `notice` (string|null): How to narrow a truncated result, or why an empty one is empty; null when neither applies.
- `source` (string): Canonical verifymcp.io page for this result.
- `total` (integer): Matches before the 100-item cap.
- `truncated` (boolean): True when total exceeds count.

### `get_server_comparison` (~86 tokens)

Compare MCP servers

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.

Input parameters:

- `identifiers` (array, required): Two to 5 servers to compare, as names, URLs or slugs.

Output parameters:

- `asOf` (string): When this data was read (UTC).
- `count` (integer): Number of entries in items.
- `items` (array)
- `notice` (string|null): How to narrow a truncated result, or why an empty one is empty; null when neither applies.
- `source` (string): Canonical verifymcp.io page for this result.
- `total` (integer): Matches before the 100-item cap.
- `truncated` (boolean): True when total exceeds count.

### `list_products` (~57 tokens)

List products

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.

Input parameters:

- `query` (string): Name fragment to match against product names and slugs.

Output parameters:

- `asOf` (string): When this data was read (UTC).
- `count` (integer): Number of entries in items.
- `items` (array)
- `notice` (string|null): How to narrow a truncated result, or why an empty one is empty; null when neither applies.
- `source` (string): Canonical verifymcp.io page for this result.
- `total` (integer): Matches before the 100-item cap.
- `truncated` (boolean): True when total exceeds count.

### `list_known_malware` (~59 tokens)

List known malware

List MCP server components carrying a supply-chain malware finding. Use to check whether anything in the register is flagged before installing.

Input parameters:

- `status` (string): Which findings to return: active, unverified, cleared or all. Defaults to active.

Output parameters:

- `asOf` (string): When this data was read (UTC).
- `count` (integer): Number of entries in items.
- `items` (array)
- `notice` (string|null): How to narrow a truncated result, or why an empty one is empty; null when neither applies.
- `source` (string): Canonical verifymcp.io page for this result.
- `total` (integer): Matches before the 100-item cap.
- `truncated` (boolean): True when total exceeds count.

### `get_server_alternatives` (~65 tokens)

Find alternative MCP servers

Other MCP servers doing a similar job to a given one, with their trust scores. Neighbours share a product or publisher namespace; this is not a semantic search.

Input parameters:

- `identifier` (string, required): Package name, endpoint URL, registry name or verifymcp slug.

Output parameters:

- `asOf` (string): When this data was read (UTC).
- `count` (integer): Number of entries in items.
- `items` (array)
- `notice` (string|null): How to narrow a truncated result, or why an empty one is empty; null when neither applies.
- `source` (string): Canonical verifymcp.io page for this result.
- `total` (integer): Matches before the 100-item cap.
- `truncated` (boolean): True when total exceeds count.

### `get_server_diagnostics` (~86 tokens)

Get MCP server diagnostics

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.

Input parameters:

- `component` (string): Which channel to report on when a server ships several.
- `identifier` (string, required): Package name, endpoint URL, registry name or verifymcp slug.

Output parameters:

- `asOf` (string): When this data was read (UTC).
- `count` (integer): Number of entries in items.
- `items` (array)
- `notice` (string|null): How to narrow a truncated result, or why an empty one is empty; null when neither applies.
- `source` (string): Canonical verifymcp.io page for this result.
- `total` (integer): Matches before the 100-item cap.
- `truncated` (boolean): True when total exceeds count.

### `get_server_install_config` (~79 tokens)

Get MCP server install config

Ready-to-paste install snippets for one MCP server, for every client we support. Read get_server first: this returns configuration, not a safety judgement.

Input parameters:

- `component` (string): Which channel to report on when a server ships several.
- `identifier` (string, required): Package name, endpoint URL, registry name or verifymcp slug.

Output parameters:

- `asOf` (string): When this data was read (UTC).
- `context` (object|null): 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): Number of entries in items.
- `items` (array)
- `notice` (string|null): How to narrow a truncated result, or why an empty one is empty; null when neither applies.
- `source` (string): Canonical verifymcp.io page for this result.
- `total` (integer): Matches before the 100-item cap.
- `truncated` (boolean): True when total exceeds count.

### `get_server_tools` (~76 tokens)

List an MCP server's tools

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.

Input parameters:

- `component` (string): Which channel to report on when a server ships several.
- `identifier` (string, required): Package name, endpoint URL, registry name or verifymcp slug.

Output parameters:

- `asOf` (string): When this data was read (UTC).
- `count` (integer): Number of entries in items.
- `items` (array)
- `notice` (string|null): How to narrow a truncated result, or why an empty one is empty; null when neither applies.
- `source` (string): Canonical verifymcp.io page for this result.
- `total` (integer): Matches before the 100-item cap.
- `truncated` (boolean): True when total exceeds count.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/io-verifymcp-mcp/mcp#diagnostics

## Score history

- 2026-09-07: 87
- 2026-09-06: 86
- 2026-09-05: 86
- 2026-09-04: 81

## Common questions

### 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 87 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 794 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 7 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://mcp.verifymcp.io/
- Repository: https://github.com/Im5tu/verifymcp
- Website: https://verifymcp.io/
- Changelog RSS feed: https://verifymcp.io/servers/io-verifymcp-mcp/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-verifymcp-mcp/mcp.json
- HTML version of this page: https://verifymcp.io/servers/io-verifymcp-mcp/mcp