Other · Remote MCP server
VerifyMCP
Independent trust scores, tool surfaces and change history for MCP servers.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.verifymcp/mcp- Version
- 1.0.0
- Status
- Active
- Category
- other
- Transport
- Streamable HTTP
- Published
- 2026-09-04
- Updated
- 2026-09-04
- Publisher
- io.verifymcp
- Namespace
- Namespace verified by the MCP Registry via the domain verifymcp.io · how
- Website
- verifymcp.io
- Repository
- github.com/Im5tu/verifymcp (folder mcp)
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://mcp.verifymcp.io | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 200)
- Handshake
- mcp 1.0.0 · protocol 2025-06-18
- Tools discovered
- 9:
list_servers,get_server,get_server_comparison,list_products,list_known_malware,get_server_alternatives,get_server_diagnostics,get_server_install_config,get_server_tools - Checked on
- 2026-10-05
How to connect VerifyMCP
VerifyMCP is a remote MCP server: there is nothing to install. Its endpoint is https://mcp.verifymcp.io, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More other servers
| Server | Runs |
|---|---|
| verify-atomSigned proof of web observations for AI agents: Ed25519 proof packets for any URL. | Local · stdio |
| VerifyAPI - fact-check with signed receiptsFact-check any claim with live web sources. Ed25519-signed receipts. Catches hallucinations. | Local · stdio |
| VerifyAXEvaluate, benchmark, and simulate AI agents on the VerifyAX agent-evaluation platform. | Remote & Local · HTTP, stdioLive check: sign-in required |
| verifyfirstLook up what your verification method cannot see: 48 failures that report success. | Local · stdio |
| VerikoValida y consulta transferencias SPEI mediante la API oficial de Veriko. | Local · stdio |
| VeritapCheck whether a real-world fact can be verified before an agent acts on it. Free, no auth. | Remote & Local · HTTP, stdioLive check: ✓ handshake |
| Veritasacta VerifyOffline receipt verifier. Ed25519 signature verification without contacting any server. | Local · stdio |
| VerityReal-time fact-checking MCP. Verifies claims against live sources with structured verdicts. | Local · stdio |