mcpField
V
VerityLayer

VerityLayer

Local
veritylayer.devSecurity0Updated 13w ago

About VerityLayer

VerityLayer is an MCP server for agents that need independent checks before acting, covering claims, untrusted text, PII, content, and irreversible actions. Verdicts can abstain rather than guess and include signed receipts; paid checks use disclosed x402 payments in USDC on Base.

Key features

  1. 01Fact verification tiers
  2. 02Prompt-injection screening
  3. 03Content moderation
  4. 04PII detection and redaction
  5. 05Action gating
  6. 06Signed verdict receipts

Use cases

  1. 01Checking claims before relying on them
  2. 02Screening tool output for injection
  3. 03Redacting exposed PII or secrets
  4. 04Gating irreversible agent actions

MCP support

The server exposes verification and trust-check tools to MCP clients, including receipt verification. Paid verdict calls use x402; wallet mode settles them locally, while keyless mode returns payment-required responses without a verdict.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
"mcpServers": {
"meloliva14-verity": {
"command": "uvx",
"args": [
"verity-mcp"
],
"env": {
"VERITY_SUITE_URL": "<VERITY_SUITE_URL>",
"VERITY_ENGINE_URL": "<VERITY_ENGINE_URL>",
"VERITY_PRICE_QUICK": "<VERITY_PRICE_QUICK>",
"VERITY_PRICE_GROUNDED": "<VERITY_PRICE_GROUNDED>",
"VERITY_PRICE_PRO": "<VERITY_PRICE_PRO>",
"VERITY_PRICE_SUITE": "<VERITY_PRICE_SUITE>"
}
}
}
}
Run commanduvx verity-mcp
Environment variables to set
VERITY_SUITE_URLVerity suite base URL
VERITY_ENGINE_URLVerity engine base URL
VERITY_PRICE_QUICKDisclosed per-call price for quick_verify
VERITY_PRICE_GROUNDEDDisclosed per-call price for grounded_verify (Sonnet, web-grounded)
VERITY_PRICE_PRODisclosed per-call price for pro_verify (Opus, premium synthesis)
VERITY_PRICE_SUITEDisclosed per-call price for the suite checks (detect_injection/moderate_content/redact_pii/guard_action, /quick tier)

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
pypiverity-mcp0.3.0

Tools

6

Saved tool list · updated 2w ago

ParameterTypeRequiredDescription
claimstringYesThe factual claim to verify.
contextstringNoOptional surrounding context for the claim.
tierenumNoDepth/price tier: 'quick' $0.02 ungrounded pre-filter; 'grounded' $0.25 live web citations (default); 'pro' $0.35 premium synthesis.quick | grounded | pro
affiliate_idstringNoOptional referral tag (sent as X-Verity-Ref). Reserved for a future referral program; never changes price or behavior.

Details

From the project README

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 named verity-mcp is an unrelated third-party project.

Tools & pricing (every docstring states its price up front)

ToolPriceGrounded?What it's for
quick_verify$0.02no (Haiku)Cheap reality-check on a claim — the loopable default. Run everywhere, escalate the load-bearing ones.
grounded_verify$0.25yes (Sonnet, live web citations)The default product — web-grounded with cited evidence, for facts that matter before you act on them.
pro_verify$0.35yes (Opus, premium synthesis)The deepest tier — high-stakes claims where the grounded answer isn't confident enough to act on.
verify_receiptfree—Statelessly verify a signed Ed25519 verdict receipt — the audit trail / second opinion, no payment.
detect_injection$0.02—Screen untrusted text / tool output for prompt-injection before acting on it.
moderate_content$0.02—Is this safe to publish? (allow / review / block priced identically — no block-to-bill.)
redact_pii$0.02—Does this leak PII or secrets? Returns findings + a redacted version.
guard_action$0.02—The money-line gate: allow / review / block right before an irreversible action.

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 server

That 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 varDefaultPurpose
VERITY_WALLET_KEY(unset — keyless)Optional. Private key of a funded Base wallet. Set it (with the [x402] extra) and this server settles its own payments, so paid tools return real verdicts. Never leaves the process; never logged.
VERITY_ENGINE_URLhttps://api.veritylayer.devFlagship claim-verification engine
VERITY_SUITE_URLhttps://suite.veritylayer.devTrust-check suite (injection/moderation/PII/guardrail)
VERITY_TIMEOUT90HTTP timeout (seconds)
VERITY_PRICE_QUICK$0.02Disclosed price echo for quick_verify
VERITY_PRICE_GROUNDED$0.25Disclosed price echo for grounded_verify
VERITY_PRICE_PRO$0.35Disclosed price echo for pro_verify
VERITY_PRICE_SUITE$0.02Disclosed 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

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.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.