Skip to content
VerifyMCP logo

VerifyMCP MCP server

Which MCP servers are VerifyMCP's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-26

← Back to VerifyMCP

Whose server it is
  • Registry nameio.verifymcp/mcpverified in the MCP registry

The registry name sits under verifymcp.io. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-26
  • Stateanswerschecked 2026-10-26
  • Tools9
  • Server calls itselfmcp
  • Server version1.0.0
  • Protocol version2025-06-18

On 2026-10-26 the server answered initialize and tools/list without a sign-in. First answer in 514 ms.

Should an agent connect itNot proven either way yet
  • Its tools do every use case we checked: Check an MCP server's trust score before installing it; Spot servers flagged for malware or risky dependencies.
  • Checked on 2 of the 7 days it takes to judge reliability.

Once connected

  • For "Check an MCP server's trust score before installing it", the likely first call is get_server.
  • For "Spot servers flagged for malware or risky dependencies", the likely first call is list_known_malware.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured dailydaily checks: 2, the first on 2026-10-26
  • INITE MCP scoreafter a weeka score needs 7 daily checks: 2 so far
  • What an agent can do with it2 of 2 use cases
  • Answeredmeasuring2 of the 7 daily checks it takes to print a share
  • Median first answer536 ms
  • Space in an agent's context≈ 1,707 tokensthe definitions of all its tools (9), which an agent carries on every turn
  • Tool definitionsA · 100 of 100
  • Typed results9 of 9 toolsdeclared outputSchema: results come typed, read once
  • Every tool passes all six checks.

What an agent can do with it

  • can do · Check an MCP server's trust score before installing it
  • not sure · Compare MCP servers by score, coverage and channel
  • can do · Spot servers flagged for malware or risky dependencies

Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?

Worth a look

None of the five warning signs in these definitions.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

Tools it offers9 tools · read 2026-10-26
  • list_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…

  • get_server

    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…

  • get_server_comparison

    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…

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

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

  • get_server_alternatives

    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.

  • get_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.

  • get_server_install_config

    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…

  • get_server_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.

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

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

Add it

Claude Code, in a terminal

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

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://mcp.verifymcp.io as a custom connector in the settings.

OpenAPI spec

6 paths, read 2026-10-26. Open the spec ↗

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.