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 分