Verity

io.github.Clawdio777由 GitHub 账号 Clawdio777 发布v1.0.2更新于 Oct 25, 2026

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

已验证STDIO仅桌面网页搜索与抓取金融

概览

AI 生成的概览

Verity 是一个本地 MCP 服务器，可对照实时网络来源核查陈述与链接，返回带置信度和来源的结构化结论。

可以做什么
核查单条陈述或链接，返回结构化结论（最新、过时、有争议、无法核实）及置信度和来源。对某条陈述进行多角度深入核查。一次批量核查最多十条陈述。用自然语言提出事实核查请求。查询预付密钥的剩余余额。使用固定调用方 ID，以便记住此前的核查记录和关注的领域。
适用场景
适合在助手依赖某条陈述或链接之前确认其是否仍然准确，或需要一次核查多条陈述、并希望得到带日期的来源和明确结论而非普通搜索结果时使用。
运行要求
通过 npx（Node.js）在本地运行。需要在 VERITY_PRIVATE_KEY 环境变量中提供 Base 钱包私钥以签署付款，并需要 Base 上的 USDC 按次付费。需要能访问 Verity API 的网络连接。
安装前请注意
该服务器要求提供 Base 钱包私钥，该私钥可控制资金，建议使用专用的低余额钱包。每次核查都会花费 USDC（每次 0.10、0.50 或 0.75），费用会累积。陈述、链接和调用方 ID 会发送给第三方 API，调用方 ID 会将你的多次核查关联起来。

安装

在 SourceWeft 中

  1. 打开 控制台中的 Verity，将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Desktop only，通过 STDIO。 STDIO 服务会启动本地进程，因此需要 SourceWeft 桌面宿主。

其他 MCP 客户端

参照 仓库 中的启动说明。

README

VERITY — Real-Time Fact-Checking Agent

Real-time fact-checking and data freshness agent. Verifies claims, URLs, and content against live web sources. Returns structured verdicts with confidence scores, what has changed, and supporting sources.

Verdicts

VerdictMeaning
CURRENTClaim is accurate and up to date
OUTDATEDClaim was true but has since been superseded
DISPUTEDSources disagree — no clear consensus
UNVERIFIABLENo usable sources found

MCP Setup (Claude Desktop / Cursor)

json
{  "mcpServers": {    "verity": {      "command": "npx",      "args": ["verity-mcp"],      "env": {        "VERITY_PRIVATE_KEY": "0x..."      }    }  }}

Get USDC on Base at coinbase.com/wallet.

Tools

ToolDescriptionPrice
verity_verifyVerify a claim or URL against live sources0.10 USDC
verity_deep_checkMulti-angle thorough verification0.50 USDC
verity_batchVerify up to 10 claims at once0.75 USDC
verity_agentNatural language fact-checking0.10 USDC
check_creditsRemaining balance for a PayGated pg_ keyfree

API

POST https://verity.basechainlabs.com/api/verifyAuthorization: x402 (USDC on Base)
json
{  "claim": "Is GPT-4 still the most capable OpenAI model?",  "caller_id": "my-agent-id"}

Response:

json
{  "verdict": "OUTDATED",  "confidence": 91,  "summary": "GPT-4 has been superseded by GPT-4o and o3.",  "what_changed": "OpenAI released GPT-4o (May 2024) and o3 (late 2024).",  "sources": [{ "url": "...", "title": "...", "published_date": "2025-01", "supports": "CONTRADICTS" }],  "checked_at": "2026-05-11T09:00:00Z",  "recommendation": "Update any content referencing GPT-4 as the most capable model."}

Persistent Memory

Pass a consistent caller_id on every call. VERITY remembers topics you've checked, domains you monitor, and previous results — no re-sending context.

A2A Agent Card

GET https://verity.basechainlabs.com/api/agent?agent-card=true

Built by BaseChain Labs

Making changes (maintainer guide)

Where things live

ThingWhere
The agent's brainsrc/agent.ts (system prompt, orchestration), src/tools.ts (fact-checking: Tavily search + Claude verdicts)
API endpointsone file per route under api/: agent (paid A2A entry), verify, deep-check, batch-verify, mcp, checkout, stripe-webhook, recover-key, plus the cron-check-deps and daily-summary crons
Payment gateapi/_x402-gate.ts: unpaid POSTs get HTTP 402 with the price and the Bazaar listing; GET returns the agent card
Public pagepublic/index.html (plain HTML). Agent card: public/.well-known/agent.json
Marketplace sellerseller-v2.mjs + Dockerfile + railway.json, the Virtuals ACP seller on Railway. Its keyring lives on a Railway volume; keyring.json and keyring.key are runtime files and gitignored
Secretshosting environment variables only. Never in a file, never in a commit

How a change goes live

There is no test suite and no CI on this repo. A push to main is the deploy.

  1. Edit, then type-check: npx tsc --noEmit -p .
  2. Commit and push to main. Vercel builds and deploys production from the GitHub integration.
  3. Confirm the newest production deployment carries your commit SHA and the endpoint answers: curl -s https://verity.basechainlabs.com/.well-known/agent.json | head -c 300
  4. A push also redeploys the Railway seller. Confirm its log shows it connected afterwards.

Because there are no tests, prove a change on the live endpoint with a read-only call before calling it done. Never make a paid call (x402 or Stripe) just to test.

Things that bite

  • Prices live in four places that must stay in sync: public/index.html, the 402 body in api/_x402-gate.ts, the Virtuals ACP offerings, and the npm package README.
  • Agentic.market's "Validate endpoint" tool: use POST. GET returns the agent card (200) by design and the validator then says "no x402 setup".
  • Tavily is the search backend. If verifications start failing, check the Tavily credit first.
  • Removing the Railway volume wipes the seller's keyring on the next redeploy and takes it offline.

来源：README.md，提交 301f9b7

工具

0
SourceWeft 尚未在沙箱中启动过该软件包，因此其工具未知。

版本历史

1
  1. v1.0.2最新Sep 16, 2026

评分

已满足适用检查项的 50%

该评分衡量此收录条目的完整程度，依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价，也不表示服务器安全或当前可用：可连通性是带日期的检查结果，评分也不包含安装量或用户评价。

  • 近 30 天内可连通25 分

    请保持端点能够响应 MCP 握手；SourceWeft 每 30 天探测一次。

  • 已声明认证方式10 分

    请在注册中心条目中声明凭据请求头，或保持端点能够响应探测，以便判定其认证方式。

  • 已列出工具15 分

    请让服务器在无凭据时响应 tools/list，或发布可在沙箱中无凭据启动的软件包。

  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分