Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.Clawdio777/verity

NPM · VERITY-MCP · SCANNED SEP 24

Real-time fact-checking MCP. Verifies claims against live sources with structured verdicts.

Available components

npm · verity-mcp 79
0 this week 79 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security90
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects path-to-regexp 6.1.0, reached via @vercel/node > path-to-regexp. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 61 of 299 dependencies flagged as unhealthy (1 deprecated). View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability78
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 301 tokens (~75/item across 4 items; 4 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
  • Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
Install

How do I install the io.github.Clawdio777/verity MCP server?

io.github.Clawdio777/verity runs locally as an npm package, launched with npx -y verity-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · verity-mcp

# add to Claude Code
claude mcp add clawdio777-verity -- npx -y verity-mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "clawdio777-verity": {
      "command": "npx",
      "args": [
        "-y",
        "verity-mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "clawdio777-verity": {
      "command": "npx",
      "args": [
        "-y",
        "verity-mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add clawdio777-verity -- npx -y verity-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "clawdio777-verity": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "verity-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add clawdio777-verity --command npx --arg -y --arg verity-mcp
# ~/.hermes/config.yaml
mcp_servers:
  clawdio777-verity:
    command: "npx"
    args: ["-y", "verity-mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "clawdio777-verity": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "verity-mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add clawdio777-verity -t stdio -c npx -a -y verity-mcp
// mcp.json
{
  "mcpServers": {
    "clawdio777-verity": {
      "command": "npx",
      "args": [
        "-y",
        "verity-mcp"
      ]
    }
  }
}
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 24 Sept 26 +1
    • Stability: 0.97 → pass security
  • 22 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

  • 20 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 17 Sept 26 +1
    • Stability: 0.97 → pass security
  • 16 Sept 26 0
    • CVE-2026-67316 no longer affects this package ▲ security
    • CVE-2026-67313 no longer affects this package ▲ security
    • CVE-2026-67312 no longer affects this package ▲ security
    • CVE-2026-67321 no longer affects this package ▲ security
    • CVE-2026-67315 no longer affects this package ▲ security
    • CVE-2026-67320 no longer affects this package ▲ security
    • CVE-2026-67317 no longer affects this package ▲ security
    • CVE-2026-67318 no longer affects this package ▲ security
    • CVE-2026-67319 no longer affects this package ▲ security
    • CVE-2026-67314 no longer affects this package ▲ security
  • 15 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

  • 13 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 24 Sept 2026 · Analysed npm/verity-mcp@1.0.2

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Vulnerabilities 17 findings
ID CVE Severity Vector Fix available
GHSA-2g4f-4pwh-qvx6 CVE-2025-69873 medium yes
GHSA-g7r4-m6w7-qqqr low CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:N yes
GHSA-9wv6-86v2-598j CVE-2024-45296 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-2mjp-6q6p-2qxm CVE-2026-1525 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L yes
GHSA-35p6-xmwp-9g52 CVE-2026-6733 low CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N yes
GHSA-4992-7rv2-5pvq CVE-2026-1527 medium CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:N yes
GHSA-8xcm-r25x-g524 CVE-2026-16728 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N yes
GHSA-c76h-2ccp-4975 CVE-2025-22150 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N yes
GHSA-cxrh-j4jr-qwg3 CVE-2025-47279 low CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:L yes
GHSA-g8m3-5g58-fq7m CVE-2026-11525 low CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N yes
GHSA-g9mf-h72j-4rw9 CVE-2026-22036 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-m8rv-5g2x-5cg5 CVE-2026-15157 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:N yes
GHSA-p88m-4jfj-68fv CVE-2026-9679 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N yes
GHSA-v3r7-h72x-cjcm CVE-2026-16729 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N yes
GHSA-v9p9-hfj2-hcw8 CVE-2026-2229 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-vrm6-8vpv-qv8q CVE-2026-1526 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-vxpw-j846-p89q CVE-2026-12151 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 299 packages
Packages resolved 299
Deprecated 1
Stale 60
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 4 exposed · ~301 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
verity_agent ~76

Natural language fact-checking. 'Is this still true?', 'Check this URL', 'When was this last updated?' — VERITY picks the right strategy. 0.10 USDC per call.

NameTypeReqDescription
caller_idstring–Optional stable ID for persistent memory.
querystringyesNatural language fact-check request.

No output schema declared.

No examples provided.

verity_batch ~65

Verify up to 10 claims in one call. Returns array of verdicts. 0.75 USDC for the batch.

NameTypeReqDescription
caller_idstring–Optional stable ID for persistent memory.
claimsarrayyesArray of claims to verify. Max 10.

No output schema declared.

No examples provided.

verity_deep_check ~70

Thorough multi-angle verification. Uses advanced search depth and cross-references authoritative sources. For high-stakes fact-checks. 0.50 USDC per call.

NameTypeReqDescription
caller_idstring–Optional stable ID for persistent memory.
claimstringyesThe claim to deeply verify.

No output schema declared.

No examples provided.

verity_verify ~90

Verify a claim, URL, or statement against live web sources. Returns CURRENT/OUTDATED/DISPUTED/UNVERIFIABLE verdict, confidence 0–100, sources, and what has changed. 0.10 USDC per call.

NameTypeReqDescription
caller_idstring–Optional stable ID for persistent memory.
claimstringyesThe claim, URL, or content to verify.

No output schema declared.

No examples provided.

Common questions

What is the io.github.Clawdio777/verity MCP server?

io.github.Clawdio777/verity is an MCP server listed in the public MCP registry as io.github.Clawdio777/verity. Real-time fact-checking MCP. Verifies claims against live sources with structured verdicts. This page covers its npm package (verity-mcp).

Is the io.github.Clawdio777/verity MCP server safe to use?

io.github.Clawdio777/verity scores 79 out of 100 on VerifyMCP. We recorded 17 known advisories against it as of 24 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the io.github.Clawdio777/verity MCP server expose?

io.github.Clawdio777/verity exposes 4 tools: verity_verify, verity_deep_check, verity_batch, verity_agent. Their descriptions and schemas cost roughly 301 tokens of context every time the server is loaded.

Is the io.github.Clawdio777/verity MCP server still maintained?

io.github.Clawdio777/verity is still listed as active in the MCP registry. We last reached this channel on 24 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the io.github.Clawdio777/verity MCP server under?

io.github.Clawdio777/verity declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.