Verity MCP
The Verity MCP server provides fail-closed trust and safety tools for AI agents, operating on the principle that uncertainty escalates to review and real red flags result in blocking. All tools are OWASP-aligned and produce audit artifacts for security and compliance.
verify_fact— Check whether a factual claim is supported by live web data. Catches hallucinations, fabricated citations, and wrong numbers. Returns a verdict (supported|unsupported|uncertain), confidence score, reasoning, and evidence.detect_injection— Screen untrusted text or tool output for prompt injection, instruction-overrides, task/persona switching, jailbreaks, and multilingual attacks. Returns a verdict, threat score, detected techniques, and a recommended action (pass/sanitize/quarantine).moderate_content— Evaluate whether content is safe to publish or surface, applying a configurable policy or conservative default. Returns a decision (publish|review|block), violation risk, flagged categories, and reasons.redact_pii— Detect and redact PII (names, emails, IDs, financial data) and secrets (API keys, passwords, tokens) before transmission, storage, or logging. Returns a verdict, severity, findings, and a redacted payload.guard_action— The primary "money-line" gate that decides whether a proposed irreversible action (spending, sending, destructive commands, data sharing) should proceed. Returns a decision (allow|review|block), a risk score, concrete reasons, specific concerns, and safer alternatives.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Verity MCPVerify the fact that the Earth orbits the Sun."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
mcp-name: io.github.meloliva14/verity-mcp
Verity MCP — verify before you act
The official Model Context Protocol server for VerityLayer: independent, fail-closed trust checks any MCP-capable agent can discover and call. Fact-check a claim, screen for prompt-injection, catch PII, and gate irreversible actions — each check returns a calibrated verdict and abstains rather than guess. Payment is pay-per-call via x402 (USDC on Base mainnet). Verity holds no private key and never charges silently.
Name note: this is VerityLayer's official server — PyPI package
verity-mcp, npm package@veritylayer/mcp. The npm package namedverity-mcpis an unrelated third-party project.
Tools & pricing (every docstring states its price up front)
Tool | Price | Grounded? | What it's for |
| $0.02 | no (Haiku) | Cheap reality-check on a claim — the loopable default. Run everywhere, escalate the load-bearing ones. |
| $0.25 | yes (Sonnet, live web citations) | The default product — web-grounded with cited evidence, for facts that matter before you act on them. |
| $0.35 | yes (Opus, premium synthesis) | The deepest tier — high-stakes claims where the grounded answer isn't confident enough to act on. |
| free | — | Statelessly verify a signed Ed25519 verdict receipt — the audit trail / second opinion, no payment. |
| $0.02 | — | Screen untrusted text / tool output for prompt-injection before acting on it. |
| $0.02 | — | Is this safe to publish? (allow / review / block priced identically — no block-to-bill.) |
| $0.02 | — | Does this leak PII or secrets? Returns findings + a redacted version. |
| $0.02 | — | The money-line gate: allow / review / block right before an irreversible action. |
Related MCP server: Enterprise MCP Gateway and Tool Registry
Quickstart
With uv (recommended — Claude Desktop / any MCP client):
{
"mcpServers": {
"verity": {
"command": "uvx",
"args": ["verity-mcp"]
}
}
}Or with pip:
pip install verity-mcp
verity-mcp # stdio MCP serverThat gets you the tools and the free verify_receipt. To get paid verdicts, read the next section — it's the part most people trip on.
How payment works
Verity's endpoints answer HTTP 402 (Payment Required) until the disclosed USDC micro-payment is settled. There are two ways to do that.
Wallet mode — get real verdicts (recommended)
{
"mcpServers": {
"verity": {
"command": "uvx",
"args": ["--from", "verity-mcp[x402]", "verity-mcp"],
"env": { "VERITY_WALLET_KEY": "0x…" }
}
}
}Point VERITY_WALLET_KEY at a funded Base-mainnet wallet and this server settles each call itself — the paid tools return real verdicts. Your key never leaves the process: it signs an EIP-3009 authorization locally for the exact amount each challenge discloses, and Verity only ever receives the signature. Nothing is charged silently; every price is disclosed up front.
Use a dedicated, low-balance wallet. This key can spend. Fund it with a few dollars of USDC on Base — calls cost $0.02–$0.35.
Keyless — the default
With no key set, this server holds nothing and pays nothing: a 402 is surfaced transparently (price restated, challenge attached) for an x402-capable caller to settle.
Be aware of the honest caveat: no shipping MCP client — Claude Desktop, Claude Code, Cursor, Windsurf — settles x402 today. So in keyless mode the paid tools will return payment_required and no verdict, forever. That's not a bug and it isn't hidden: the response says NO VERDICT WAS PRODUCED. Do not proceed as if this returned allow. If you want verdicts from an ordinary MCP client, use wallet mode.
verify_receipt is a free route, never 402s, and needs no wallet — you can check our signatures before you ever pay us.
Signed receipts — don't take Verity's word for it
Every paid verdict ships with an Ed25519-signed receipt: self-contained cryptographic proof of exactly what Verity said about exactly what claim, verifiable forever. Check any receipt free with the verify_receipt tool, offline against the public key at /.well-known/verity-pubkey.json, or live: curl https://api.veritylayer.dev/receipt/selftest.
Configuration (all optional)
Env var | Default | Purpose |
| (unset — keyless) | Optional. Private key of a funded Base wallet. Set it (with the |
|
| Flagship claim-verification engine |
|
| Trust-check suite (injection/moderation/PII/guardrail) |
|
| HTTP timeout (seconds) |
|
| Disclosed price echo for |
|
| Disclosed price echo for |
|
| Disclosed price echo for |
|
| Disclosed price echo for the suite checks |
Referral tag (reserved)
Every tool accepts an optional affiliate_id, forwarded as an X-Verity-Ref header. It never changes price, gating, or the verdict — it only tags who routed the call, and it is reserved for a future referral program: no split is paid today, and none will be until public terms are published at veritylayer.dev.
Links
Website: https://veritylayer.dev · Manifesto: https://veritylayer.dev/manifesto/
Live API + discovery: https://api.veritylayer.dev/llms.txt ·
/.well-known/x402.jsonnpm client:
@veritylayer/mcpContact: veritylayer@gmail.com
Independent · fail-closed · keyless · pay-per-call. The only trust form an autonomous agent can pick up mid-task with no human and no account.
Maintenance
Related MCP Servers
- Alicense-qualityCmaintenanceEnables AI agents to discover and execute tools via a secure MCP server with JWT authentication, RBAC, rate limiting, and audit logging.Last updated1MIT
- AlicenseAqualityBmaintenanceMCP server exposing AIMarket's verifiable oracle capabilities (Platon VRF, Chronos VDF, LUMEN reputation) as agent-callable tools with pay-per-call.Last updated10MIT
- Alicense-qualityDmaintenanceEnables trust, reputation, and economic accountability for MCP by proxying between clients and servers, enriching every tool invocation with trust evaluation, KYA tiers, spending limits, and delegation chains.Last updatedMIT
Related MCP Connectors
Security firewall for AI agents — scans MCP calls for injection, secrets, and risks.
Crypto transaction firewall and risk tools for MCP agents.
AI Reasoning Cache & Consensus Layer with 11 MCP tools via Streamable HTTP.
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/meloliva14/verity-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server