原型 · 预览版:收录官方注册中心里的全部服务器,每 30 分钟同步一次。评价和账户功能将在后续阶段推出。
PopNx MCP为使用 AI 的人准备的 MCP 服务器 · 用大白话讲清楚

Veris

作者:jakeyoung1版本 0.3.1i★ –i在你的电脑上运行
注册名称io.github.jakeyoung1/veris

安装

概览

作者提供的说明(英文原文)

Provenance-first web + SEC EDGAR data for AI agents: every fact carries its verifiable source.

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

  • 连接方式: 在你的电脑上运行
  • 传输方式: stdio
  • 分类: 其他
  • 你需要填写:BRAVE_API_KEY

安装

选择你使用的 AI 应用,然后复制设置。

安装之前

  • 基础检查:1 项中通过 1 项
  • 在你的电脑上运行,拥有你的用户账户的权限(文件、网络、应用)。
  • 需要你自己填写: BRAVE_API_KEY, SEC_USER_AGENT

标为机密的值是你账户的钥匙。千万不要分享给别人,也不要粘贴到聊天里。

你需要

  • npm已安装 Node.js(用于 npx 命令)

你用的是哪个应用?

在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。

打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json

{
  "mcpServers": {
    "veris": {
      "command": "npx",
      "args": [
        "-y",
        "veris-mcp"
      ],
      "env": {
        "BRAVE_API_KEY": "your-value",
        "SEC_USER_AGENT": "your-value"
      }
    }
  }
}

在终端中运行这条命令

claude mcp add veris --env BRAVE_API_KEY=your-value --env SEC_USER_AGENT=your-value -- npx -y veris-mcp

运行前请先填写空着的值。

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json

{
  "mcpServers": {
    "veris": {
      "command": "npx",
      "args": [
        "-y",
        "veris-mcp"
      ],
      "env": {
        "BRAVE_API_KEY": "your-value",
        "SEC_USER_AGENT": "your-value"
      }
    }
  }
}

浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

{
  "servers": {
    "veris": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "veris-mcp"
      ],
      "env": {
        "BRAVE_API_KEY": "your-value",
        "SEC_USER_AGENT": "your-value"
      }
    }
  }
}

浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。

这个服务器在你的电脑上运行,而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。

你的选择通过 Cookie 保存在这台设备上,无需账户。

需要你填写的值

  • BRAVE_API_KEY 机密 env
    Optional Brave Search API key; falls back to keyless DuckDuckGo if unset.
  • SEC_USER_AGENT env
    SEC fair-access User-Agent ('Name email@domain') for EDGAR; a default ships.

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。

它能做什么

它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。

基础检查i

我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日

  • ✓ 通过

    作者与仓库一致

    注册名称已通过 GitHub 账户 jakeyoung1 验证,该账户拥有此仓库

  • … 尚未检查

    仍在维护

    我们还没有从 GitHub 读取这个仓库

  • … 尚未检查

    有许可证

    我们还没有从 GitHub 读取这个仓库

  • – 不适用

    端点有响应

    它在你的电脑上运行,没有互联网端点

  • – 不适用

    使用 OAuth 登录

    在你的电脑上运行,改用本地设置

  • … 尚未检查

    工具描述中没有隐藏指令

    它在你的电脑上运行;我们只能读取互联网端点的工具列表

与“其他”中的其他服务器比较i

  • 星标数多于此分类中其他 32680 个服务器的 0%
  • 发布到注册中心的时间比此分类中其他 32680 个服务器的 58% 更新
  • 基础检查结果等于或优于此分类中其他 32680 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。

常见问题

Veris 安全吗?

它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。

它需要哪些密钥或代码?

你需要填写:BRAVE_API_KEY

它在我的电脑上运行还是在云端?

它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。

它还在维护吗?

GitHub 仓库最后更新于–,最新版本(0.3.1)于28天前进入注册中心。

哪些应用可以使用它?

支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Node.js。

有什么可以替代它?

同一分类中有:Spec Driven Development, Remote Desktop Commander, EmbeddedCI BenchPod

替代选择

同一分类中其他作者的服务器,按星标数排序。

如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

Spec Driven Development

作者:formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

在你的电脑上运行★ 440MIT14个月前更新
安装

Remote Desktop Commander

作者:desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

在云端运行★ 211前天更新
安装

EmbeddedCI BenchPod

作者:embeddedci-com

Drive a BenchPod hardware-in-the-loop bench: power, flash, UART, I2C, CAN, analog and logic.

在你的电脑上运行今天更新
安装

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

veris

· npx -y veris-mcp

Provenance-first web access for AI agents. Clean content *plus* verifiable source metadata, in one call.

Today an AI agent reading the web gets a wall of text. It does not get: when the page was published, whether the content changed since last time, who wrote it, the canonical source, or the license terms. veris attaches all of that to every read.

web_read("https://example.com/article")

→ clean markdown

  • { publishedAt, modifiedAt, author, canonicalUrl, contentHash, license, fetchedAt }

That metadata is not a nice-to-have. It is the foundation the rest of the AI-web economy needs: freshness, change-detection, citation, and — eventually — paying the people who wrote the content.


Why this exists

The web is being scraped by AI with no attribution and no payment. Publishers are responding by blocking bots and locking content. AI gets worse; publishers lose. The fix is a layer between agents and publishers that reads cleanly, tracks provenance, and (later) settles payment.

veris is the agent-side of that layer — the SDK every agent imports to consume the web responsibly. Think "Plaid for the AI web": you don't own the publishers, you own the integration developers reach for.

Roadmap (one codebase, three stages)

StageWhatStatus
1. Clean + provenancesearch / read / research with verifiable source metadata✅
2. Finance verticalSEC EDGAR filings with authoritative, official provenance✅
3. Settlementlicense-aware access + attribution ledger + payment intents✅ v0.3.0 (payments stubbed, no money moves)
3b. Live paymentsplug a provider (RSL license server / x402 / Stripe) into settlement.ts🔜
Stage 3: what v0.3.0 does

Every content read passes a policy gate first: web_read, web_research, finance_filing_read, URL watches (watch_manage refuses to add a URL it may not read; watch_check reports it as withheld and keeps the old baseline), and filing reads in veris-mcp digest. EDGAR index lookups use the SEC JSON API and are not page reads.

  1. robots.txt. Fetched per origin and matched for the VerisBot token (falls back to *), per RFC 9309: longest match wins, * and $ wildcards, missing file = allow, 5xx = disallow. A disallowed URL returns status: "blocked" with the exact rule (e.g. Disallow: /cgi-bin) and the page is never requested.
  2. RSL licenses. Discovered from robots.txt License: lines, , or inline . The gate picks the scope covering the URL and the license that permits ai-input use.
  3. Price. If the license charges (purchase, subscription, crawl, use), the tool returns status: "payment_required" with the terms, price, and the RSL document URL instead of content. When the license is declared in robots.txt, the page is not fetched at all. priceHint is filled only from a declared , copied verbatim. A paid license with no amount reports price: null; veris never estimates one.
  4. Ledger. Every read, block, and payment requirement is appended to ~/.veris/ledger.jsonl (override VERIS_LEDGER_FILE) with URL, content hash, timestamp, tool, and the full license record. Entries are hash-chained, so edits or deletions are detectable: veris-mcp ledger --verify. List with veris-mcp ledger [--kind read|blocked|payment_required|payment_intent] [--url U] [--since ISO] [--limit N].
  5. Settlement stub. A paid license also records a payment_intent entry (declared price, terms, license server). The default provider is none: status recorded, nothing charged, content withheld. A real provider implements PaymentProvider.authorize() in src/settlement.ts and registers with setPaymentProvider().

Every license field names its source (robotsUrl + robotsRule, rslUrl, price.source), so any verdict can be re-fetched and checked. Tool input schemas are unchanged from v0.2.

Tools

Web

ToolDoes
web_search(query, n?)Ranked results as structured JSON. Brave (with key) or keyless DuckDuckGo.
web_read(url, fresh?)URL → clean markdown + provenance block. 24h cache.
web_research(query, n?)Search + read top N + bundle with per-source citations.

Finance — SEC EDGAR (free, official, no API key)

ToolDoes
finance_filings(query, formType?, limit?)Ticker / name / CIK → recent SEC filings: form, official filing & report dates, accession, direct document URL.
finance_filing_read(url or query, formType?)Read a filing by URL, or auto-read the latest matching form for a company. Clean text + provenance.
finance_financials(query)Revenue, net income, total assets, cash, diluted EPS from SEC XBRL — each figure stamped with the exact filing it came from.

Why EDGAR first? Filings carry *authoritative* dates and identifiers straight from the SEC — provenance isn't guessed, it's official. Free, structured, no auth. One call gets an agent the latest 10-K with a verifiable source:

`

finance_filing_read({ query: "NVDA", formType: "10-K" })

→ NVIDIA CORP — 10-K (filed 2026-02-25)

clean text + { source, filed date, contentHash, wordCount }

`

Watch — change detection & alerts

ToolDoes
watch_manage(action, target?, formType?)Add/remove/list watches: a company's SEC filings (ticker + optional form like 8-K) or any URL (content-hash watch).
watch_check()Check all watches; returns only what's NEW (new filings / changed pages) and rolls baselines forward. Run it on a schedule → alert feed.

Filings watches default to material forms only — 8-K, 10-K, 10-Q, 20-F, SC 13D/G, merger proxies, offerings, late-filing notices. Routine Form 4 / 13F-HR traffic is suppressed, because an alert feed nobody reads is worse than none. Pass formType: "ALL" to see everything, or a specific form to watch just that one.

Alerts by email (veris-mcp digest)

watch_check returns JSON to an MCP client. digest turns the same data into an email a human actually reads: it checks every watch, reads each new material filing, summarizes what changed, and delivers it.

veris-mcp digest --dry-run          # print the digest, send nothing

veris-mcp digest # check, summarize, email veris-mcp digest --to a@co.com # override recipients veris-mcp mailtest # verify SMTP without sending

Every summary carries verbatim quotes from the filing, and each quote is checked against the source text before sending — quotes that can't be matched are flagged in the email rather than presented as fact. Filings longer than the character budget are marked as partially read; they are never silently truncated.

EnvDoes
ANTHROPIC_API_KEYEnables filing summaries. Without it, digests still send as raw filing notices.
VERIS_SUMMARY_MODELModel for summaries (default claude-opus-5).
VERIS_SUMMARY_CHAR_BUDGETChars of filing text summarized (default 250,000).
VERIS_SMTP_URLe.g. smtps://user:pass@smtp.gmail.com:465
VERIS_MAIL_FROMe.g. "Veris Alerts "
VERIS_MAIL_TOComma-separated default recipients.

Run it on a schedule for a live alert feed:

*/15 * * * * ANTHROPIC_API_KEY=... VERIS_SMTP_URL=... veris-mcp digest

Install

npx -y veris-mcp        # zero-install, always latest

Or from source:

git clone https://github.com/jakeyoung1/veris && cd veris

npm install && npm run build

Optional env:

export BRAVE_API_KEY=your_key                      # better search; https://search.brave.com/app/keys

export SEC_USER_AGENT="Your Name you@email.com" # SEC fair-access policy (recommended)

Without a Brave key, search falls back to keyless DuckDuckGo automatically. SEC requires a Name email@domain style User-Agent — veris ships a default, but set your own contact.

Use in Claude Code

Add to your MCP config (.mcp.json):

{

"mcpServers": { "veris": { "command": "npx", "args": ["-y", "veris-mcp"], "env": { "BRAVE_API_KEY": "optional", "SEC_USER_AGENT": "Your Name you@email.com" } } } }

Restart Claude Code, then ask it to web_research something.

Remote server (HTTP)

Run veris as a remote MCP server (Streamable HTTP) and connect from any MCP client by URL:

npx -y veris-mcp http                            # http://127.0.0.1:8787/mcp

VERIS_HTTP_HOST=0.0.0.0 npx -y veris-mcp http # expose it (put TLS in front)

EnvDoes
VERIS_PORT / PORTPort (default 8787)
VERIS_HTTP_HOSTBind host (default 127.0.0.1)
VERIS_API_KEYSComma-separated keys. If set, /mcp requires Authorization: Bearer (or x-api-key). Unset = open.
VERIS_RATE_LIMITRequests/min/IP (default 60)

Self-hosting is free, forever. VERIS_API_KEYS exists so a hosted instance can be metered.

Docker
docker build -t veris .

docker run -p 8787:8787 veris

Works as-is on Fly.io / Render / Railway — anything that runs a Dockerfile.

Design notes

  • Provenance from raw HTML. We fetch the page ourselves and pull dates/author/canonical from , JSON-LD, and Open Graph *before* readability strips them.
  • Content hash. sha256 of extracted text — detects whether a page changed and enables dedupe across agents (the basis for a shared web index).
  • Provider interface. Swap search backends without touching tool code.
  • Cache + ledger. cache.ts keeps the keyed read cache and the append-only, hash-chained attribution ledger side by side.

License

MIT

问 PopNx