Other · Local MCP server
Verity MCP
Fail-closed verify-before-you-act gate for AI agents. Signed receipts. Pay-per-call via x402.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.meloliva14/verity-mcp- Version
- 0.3.0
- Status
- Active
- Category
- other
- Transport
- stdio (local process)
- Package
- PyPI
- Published
- 2026-07-05
- Updated
- 2026-07-05
- Publisher
- meloliva14 (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/meloliva14) · how
- Website
- veritylayer.dev
- Repository
- github.com/meloliva14/verity-mcp
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| PyPI | verity-mcp | 0.3.0 | stdio |
How to connect Verity MCP
Verity MCP runs locally from a Python package published to PyPI: verity-mcp version 0.3.0. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Python; clients usually start it with uvx (from uv) or after pip install - the usual command is uvx verity-mcp. It reads these environment variables: VERITY_SUITE_URL, VERITY_ENGINE_URL, VERITY_PRICE_QUICK, VERITY_PRICE_GROUNDED, VERITY_PRICE_PRO and VERITY_PRICE_SUITE; set them in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"verity-mcp": {
"command": "uvx",
"args": [
"verity-mcp"
],
"env": {
"VERITY_SUITE_URL": "<value>",
"VERITY_ENGINE_URL": "<value>",
"VERITY_PRICE_QUICK": "<value>",
"VERITY_PRICE_GROUNDED": "<value>",
"VERITY_PRICE_PRO": "<value>",
"VERITY_PRICE_SUITE": "<value>"
}
}
}
}Derived from the registry entry, not tested here. 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 |
|---|---|
| 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 |
| VerityCited product-compliance ground truth for AI agents. Never generates; always cites. | Remote · HTTPLive check: ✓ handshake |
| VerixID VerifierVerify VerixID proof-of-existence records and optionally prove ownership. | Remote · HTTPLive check: ✓ handshake |
| VermarcoMarketplace and payment rail for AI agents: list, buy and settle with signed receipts. | Remote · HTTPLive check: ✓ handshake |
| Version PillProduct management, public changelog, and feature requests - 60 lean MCP tools. | Remote · HTTP, SSELive check: sign-in required |
| VersoMCP server to read Verso-generated documentation sites (e.g., the Lean Language Reference). | Local · stdio |