io.github.meloliva14/verity-mcp
verity
Is the io.github.meloliva14/verity-mcp MCP server down? No. Installed with mcp<2, it started and listed its tools on 2026-11-01.
Fail-closed verify-before-you-act gate for AI agents. Signed receipts. Pay-per-call via x402.
needs mcp<2 probed 2026-11-15 · unchanged since 2026-11-01
A plain install of the package stops at the import below. These tool definitions are from a second install with mcp<2, started in a container with the network off, on 2026-11-01.
MCP error -32000: Connection closed ModuleNotFoundError: No module named 'mcp.server.fastmcp'. This is mcp 2.x, where FastMCP was renamed to MCPServer (from mcp
- Run it
- uvx --with 'mcp<2' verity-mcp@0.3.0 (stdio, probed in a container with the network off)
- Host
- pypi.org
- Reports itself as
- verity 1.30.0
- Capabilities
- experimental, prompts, resources, tools
- Repository
- https://github.com/meloliva14/verity-mcp
- Website
- https://veritylayer.dev
- Registry
- active, updated 2026-07-05 · registry entry
- Changes
- 2 recorded, reachable in 0 of them. A row is added when the result, the tool count or the cost changes.
Most expensive tools
Estimates with the o200k_base tokenizer.
| Tool | o200k estimate | Share of this server |
|---|---|---|
| guard_action | 375 | 16 % |
| quick_verify | 325 | 14 % |
| grounded_verify | 325 | 14 % |
| pro_verify | 303 | 13 % |
| detect_injection | 290 | 12 % |
Compare this server with others.
More servers
Other registry entries on pypi.org, the ones next to this name; all of them.
- io.github.mdefrance/autocarver · install failed
- agent-godmode io.github.mdvohra/agent-godmode · needs mcp<2
- io.github.mechreaper007x/clipacanvas · crashed on start
- pubmed-stream io.github.melhzy/pubmed-stream · alive
- Context Engine io.github.melonelish/context-engine · crashed on start
- io.github.memtomem/memtomem · alive
- Euclid-MCP io.github.meob/euclid-mcp · alive
- PostgreSQL CVE & Release Intelligence io.github.meob/pg-cve-mcp · needs env
Servers that mention verity.
- US Drought Monitor com.olyport/drought · alive
- Scanverity Resolution Rules com.scanverity/resolution-rules · alive
- Verity RMS MCP Server com.verityrms/rms-mcp · needs your URL
- WizerAPI Contract Intelligence com.wizerapi/contract-intelligence · server error
- Verity Skills io.github.cchurctrip/verity · needs auth
- io.github.cyanheads/nist-nvd-mcp-server · alive
- Verity io.github.veritylabsai/verity · server error
- Rattlewatch io.github.veritylabsai/rattlewatch · timeout
History
We add a row when the result changes. A server with no change keeps its last row.
| Probed | Result | Init | Tools | Claude | o200k |
|---|---|---|---|---|---|
| 2026-11-01 08:13 | needs mcp<2 | 1.5 s | 8 | 4.2k | 2.4k |
| 2026-10-18 06:41 | crashed on start |
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- The package imports FastMCP from mcp.server.fastmcp. mcp 2.0, the Python SDK of 28 July 2026, renamed FastMCP to MCPServer, and the package asks for mcp with no upper bound, so a plain install (uvx, pip) gets mcp 2.x and the server stops at the import. Installed with mcp<2, it starts and lists its tools. The fix for the publisher: pin mcp<2 in the dependencies, for example mcp>=1.2,<2, and publish a new version, or move to MCPServer as the SDK's migration guide says. Until then, run it with uvx --with 'mcp<2'.
The cause and the fix, with the code before and after: ModuleNotFoundError: No module named 'mcp.server.fastmcp'