原型 · 预览版:收录官方注册中心里的全部服务器,每 30 分钟同步一次。使用 Google 登录即可撰写评价。原型 · 每 30 分钟更新
PopNx MCP为使用 AI 的人准备的 MCP 服务器 · 用大白话讲清楚 登录

Veyra Trust

作者:mioku50版本 1.0.0i★ 1i在云端运行官方网站 ↗
注册名称io.github.mioku50/veyra-trust

安装方法

能做什么

Check x402 payment terms and preview observed endpoint history on Arc mainnet.

作者提供的原文

  • 连接方式 在云端运行
  • 账号或密钥 无需密钥
  • 分类 网店与支付

为什么排在这里

列表按使用分(满分 100)排序,由以下部分组成

热度4/80GitHub 星标或每周下载量:较大的计 60,较小的计 20
新鲜度12/1230 天内有发布或代码更新得满分
仍在响应8/8上次检查时云端端点有响应
使用分24/100

质量: 基础检查通过 5/5 项(仅展示,不用于排序) · 上升势头: 暂无数据 (只用于“上升中”标签)

安装

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

用一句话让 AI 帮你安装

请帮我安装 Veyra Trust。按照 https://mcp.popnx.com/i/mioku50-veyra-trust.md 操作,先把命令给我看,等我同意后再运行。

粘贴到能在你电脑上工作的 AI(如 Claude Code、Cursor)。它会读取我们的步骤,先给你看命令,等你同意。无需密钥,无需注册。 · 查看 AI 会读取的全文

通过 5/5 项检查 · 你的提问会经过开发者的服务器(agent-commerce-six.vercel.app) · ✓ 命令已检查 2026年11月20日

第一步:你用哪个 AI?

选择你用的应用,步骤会显示在下方。

可连接 Claude · 约 2 分钟

不需要密钥,不用安装程序 · 在 claude.ai 或桌面应用设置一次,即可在聊天中使用 · 免费账户可添加 1 个 · Team/Enterprise 方案由所有者(Owner)添加

  1. 打开 Claude 的 Connectors 页面

    CustomizeConnectors

    CustomizeConnectors1Add2https://…3Add4
  2. 点击“Add” → “Custom” → “Web”,填写这 2 项

    把这里的内容复制到 Claude 中同名的输入框,然后点击 Continue

    Name · 名称Veyra Trust
    Remote MCP server URL · 地址https://agent-commerce-six.vercel.app/api/mcp

    在 Claude 检测到的登录设置页点击 Continue · Authentication 按作者说明选择(Sign in now、Sign in when needed 或 No sign in),然后点击 Add

  3. 在聊天中开启

    +ConnectorsVeyra Trust

  4. 试一试

    用 Veyra Trust 告诉我你能帮我做什么,然后做一件给我看

    ✓ 如果 Claude 说正在使用 Veyra Trust,或回答中出现 Veyra Trust 的工具名称,就表示连接成功

菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同

能否连接 ChatGPT 取决于方案

完整 MCP:网页版 ChatGPT Business、Enterprise 或 Edu · Pro:以读取/获取权限连接,修改数据的工具可能用不了 · Plus:官方文档尚未确认,如果在插件页看到添加自定义 MCP 的选项可以试试 · 仅限网页

  1. 在网页版 ChatGPT 打开添加 MCP 的页面

    Plugins+Add custom MCP server

    ChatGPTPlugins1+2https://…3Create4
  2. 填写名称和地址

    输入名称,在 Connection 下粘贴地址,勾选风险提示,然后点击 Create as a plugin

    Name · 名称Veyra Trust
    Connection · 地址https://agent-commerce-six.vercel.app/api/mcp
  3. 在聊天中选择 Veyra Trust

    开启新聊天,输入前先从插件列表中选择 Veyra Trust

  4. 试一试

    用 Veyra Trust 告诉我你能帮我做什么,然后做一件给我看

    ✓ 如果 ChatGPT 说正在使用 Veyra Trust,或回答中出现 Veyra Trust 的工具名称,就表示连接成功

菜单名称已于 2026年11月11日 对照 OpenAI 帮助页面核实 · 你的界面可能因版本略有不同

可连接 Claude Code · 约 2 分钟

不需要密钥,不用安装程序

  1. 打开终端

    Mac:按 Command+空格,输入 Terminal · Windows:打开 PowerShell

  2. 粘贴这条命令并按 Enter

    claude mcp add --transport http --scope user veyra-trust https://agent-commerce-six.vercel.app/api/mcp
  3. 在 Claude Code 中输入 /mcp

    应能看到 Veyra Trust 在列表中并显示已连接

  4. 试一试

    用 Veyra Trust 告诉我你能帮我做什么,然后做一件给我看

    ✓ 如果 Claude Code 说正在使用 Veyra Trust,或回答中出现 Veyra Trust 的工具名称,就表示连接成功

菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同

可连接 Cursor · 约 2 分钟

不需要密钥,不用安装程序

  1. 点击这个按钮打开 Cursor

    在 Cursor 中打开

    Cursor 会请你确认安装,点击 Install

  2. 在 Cursor 中以 Agent 模式打开 AI 聊天

  3. 试一试

    用 Veyra Trust 告诉我你能帮我做什么,然后做一件给我看

    ✓ 如果 Cursor 说正在使用 Veyra Trust,或回答中出现 Veyra Trust 的工具名称,就表示连接成功

菜单名称已于 2026年11月11日 对照 Cursor 帮助页面核实 · 你的界面可能因版本略有不同

可连接 VS Code · 约 2 分钟

不需要密钥,不用安装程序

  1. 点击这个按钮打开 VS Code

    在 VS Code 中打开

    VS Code 会请你确认安装,点击 Install

  2. 在 VS Code 中以 Agent 模式打开 AI 聊天

  3. 试一试

    用 Veyra Trust 告诉我你能帮我做什么,然后做一件给我看

    ✓ 如果 VS Code 说正在使用 Veyra Trust,或回答中出现 Veyra Trust 的工具名称,就表示连接成功

菜单名称已于 2026年11月11日 对照 VS Code 帮助页面核实 · 你的界面可能因版本略有不同

其他支持 MCP 的应用(如 Windsurf、Zed、Gemini CLI)添加方式各不相同,请在应用列表中查看

查看所有支持 MCP 的应用 →

通过网页连接的应用使用的地址

地址https://agent-commerce-six.vercel.app/api/mcp

JSON 设置在下方“开发者专用”中

卡住了?问问正在用 Veyra Trust 的人💬 讨论 →
开发者专用:终端命令和 JSON 设置

通过网页连接

Claude Code

claude mcp add --transport http --scope user veyra-trust https://agent-commerce-six.vercel.app/api/mcp

Cursor (~/.cursor/mcp.json)

{
  "mcpServers": {
    "veyra-trust": {
      "url": "https://agent-commerce-six.vercel.app/api/mcp"
    }
  }
}

VS Code (mcp.json)

{
  "servers": {
    "veyra-trust": {
      "type": "http",
      "url": "https://agent-commerce-six.vercel.app/api/mcp"
    }
  }
}

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

一览

每周下载量i
不在 npm/PyPI 上
许可证i
Apache-2.0
连接方式
在云端运行
传输方式
streamable-http
最新版本i
1.0.0
发布到注册中心i
2026年11月20日
代码最后更新i
2026年11月20日
最近检查
2026年11月20日
作者
mioku50
注册状态
活跃

哪些应用可以使用它

依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。

通过互联网连接,适用于

ClaudeChatGPTGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast

全部应用及其优缺点 →

它能做什么

工具名称和描述与服务器在 2026年11月20日 报告的完全一致。这些内容由作者撰写,不是我们写的;我们以纯文本形式显示。

  • veyra_check_endpoint

    Check the live USDC offer for an x402 endpoint on Arc mainnet before paying. Returns an unsigned verdict and evidence.

  • veyra_endpoint_history

    Preview the recency and coverage of stored Arc USDC observations. Full history and change details are sold separately.

  • veyra_list_resources

    List Veyra's published free and paid x402 API resources and their HTTP methods.

基础检查i

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

  • ✓ 通过

    作者与仓库一致

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

  • ✓ 通过

    仍在维护

    代码最后更新于今天

  • ✓ 通过

    有许可证

    使用 Apache-2.0

  • ✓ 通过

    端点有响应

    在 88 毫秒内响应(HTTP 200)

  • – 不适用

    使用 OAuth 登录

    无需登录

  • ✓ 通过

    工具描述中没有隐藏指令

    已读取 3 个工具描述,未发现针对 AI 的隐藏指令

我们检查什么 → · JSON

作者:申请重新检查或报告信息错误
给作者:在 README 中加徽章

如果你是作者,可把这段代码贴到 README。徽章会链接回本页。

[![Featured on PopNx MCP](https://mcp.popnx.com/badge/mioku50-veyra-trust.svg)](https://mcp.popnx.com/en/servers/mioku50-veyra-trust)

讨论

提问、分享技巧或报告无法使用。按“有帮助”数量排序。

还没有帖子,欢迎第一个提问或分享。

此处内容由用户撰写,不代表 PopNx 团队。

登录后发帖

用户评价

还没有评价

登录后写评价

与“网店与支付”中的其他服务器比较i

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

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

常见问题

Veyra Trust 安全吗?

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

它需要哪些密钥或代码?

注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。

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

它在作者的云端运行。通过互联网连接,无需安装,但你发送的内容会经过作者的服务器。

它还在维护吗?

GitHub 仓库最后更新于今天,最新版本(1.0.0)于今天进入注册中心。

哪些应用可以使用它?

支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,因此也能用于接受远程 MCP 的应用,例如网页版 ChatGPT(Business 及以上为完整 MCP;Pro 为只读)。

有什么可以替代它?

同一分类中有:Stripe MCP, flightclaw, Trade It, Marketplace Ad Pros: Amazon Ads & Seller Central, idealo MCP Server

功能相近的其他选择

同一分类、其他作者、命令已通过检查。官方的排在前面,再按星标排序。

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

Stripe MCP

MCP server integrating with Stripe - tools for customers, products, payments, and more.

作者:stripe广泛使用★ 207513个月前更新

在云端运行✓ 服务方 · stripe.com

flightclaw

Search ~300 airlines and book flights with a checkout link. OAuth sign-in by email code.

作者:flightclaw正在增长★ 872个月前更新

在云端运行✓ 服务方 · flightclaw.com

Trade It

Connect brokerage accounts to AI assistants: holdings, orders, asset lookup, and approved trading.

作者:trade-it-inc起步阶段★ 6235天前更新

在云端运行✓ 服务方 · tradeit.app

idealo MCP Server

Search products, compare prices and discover deals across 6 European markets with your AI assistant.

作者:idealo起步阶段★ 286个月前更新

在云端运行✓ 服务方 · mcp.idealo.com
与相似项目对比
本项
Veyra Trust
Stripe MCPflightclawTrade ItMarketplace Ad Pros: Amazon Ads & Seller Centralidealo MCP Server
运行位置在云端运行,无需安装在云端运行,无需安装在云端运行,无需安装在云端运行,无需安装在云端运行,无需安装在云端运行,无需安装
需要密钥否否否否否否
可在 Claude 中按 + 添加否是否否否否
基础检查5/54/44/45/54/44/4
许可证Apache-2.0MITMITCC0-1.0MITMIT
价格登记中未列出费用登记中未列出费用登记中未列出费用登记中未列出费用登记中未列出费用登记中未列出费用

作者的 README

打开 README

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

Veyra

## Veyra decides. Circle pays.

Before an agent spends USDC, Veyra decides whether it should pay, whom, and how much.

Circle gives an agent a wallet, a marketplace, and a way to pay. Veyra is the independent layer in front of that: it measures the evidence available about a counterparty, ranks the alternatives, enforces budget and risk policy, and issues a signed authorization bound to one endpoint and one amount. After execution, the observed outcome becomes new reputation on Arc.

ERC-8004 · ERC-8183 · x402 · Gateway Nanopayments · USDC · Arc

Live — [agent-commerce-six.vercel.app](https://agent-commerce-six.vercel.app) · Create an agent, the front door — a personal agent, its brief, and what it has earned on Arc · Choose and pay yourself, the same decision driven by hand · Decision log, every trust-routed action, authorization and onchain settlement as it happened

On Arc mainnet Veyra is ERC-8004 agent #298. It sells its Trust API there, paid through Circle Gateway. Its own contracts (the Trust Gate, the evaluator and the proof registry) stay on Arc Testnet until they are audited.

The agent in front of it

The front door creates Nova, a personal agent owned by the person who made it. Nova starts from an owner-stated goal, interests, and a short owner-confirmed account of where the work already is. It reads official publications and release notes, explains significant changes against what has already been built, with source excerpts, and keeps ordinary commit counts and API listings in background history. Nova may propose a change to that project context and can never confirm one itself. Public-source analysis uses the app's model without charging the owner's wallet.

GOAL       a concrete result the owner wants

↓ STATE what is already true about the work, confirmed by the owner ↓ OBSERVE official publications · release notes · payment changes ↓ EXPLAIN what changed · why it matters against work already done · next step · source excerpts ↓ FEEDBACK was this result useful? ↓ only for a specific unanswered question PROPOSE suitable tool · expected result · exact price · Veyra policy ↓ only after owner approval and existing execution checks SIGN → EXECUTE → VERIFY → RECEIPT / ARC ATTESTATION

Ask Nova. The owner can put a question to Nova directly.

  • Nova answers from Arc's and Circle's documentation first, at no charge.
  • Only when that does not answer does it choose a tool on Arc for the question, and price it for the owner to approve.

The brief reads Arc first and Base after, with one card per endpoint. The cards come from Circle's catalogue and from the ERC-8004 registry on Arc.

A missing answer is a research hypothesis, not permission to spend. Financial permission remains Veyra's separate deterministic decision. The owner signs every payment, because autonomous spending is frozen.

Nova never holds money and there is no signing path in its code. It can want to spend and it says so, with a price and a verdict on the item; the payment goes through the same selection, clearance and wallet signature as any other Veyra purchase.

An identity is earned, not granted. The rule is a verified purchase and an attestation somebody else can read — not because Arc re-checks Veyra's verdict (it does not; the verdict stays Veyra's) but because a claim that lives only in Veyra's database is a claim whose only witness is the party making it.

The decision underneath

INTENT     "Research the latest developments in Ambient"

budget 0.10 USDC · optimize for trust ↓ DISCOVER ERC-8004 agents on Arc · Circle x402 marketplace 4 candidates ↓ VERIFY live endpoint probe · catalog drift · latency settlement history · onchain identity evidence coverage caps the tier ↓ DECIDE ALLOW · ALLOW_WITH_LIMITS · REQUIRE_EVALUATOR · REVIEW · DENY fails closed, never silently ↓ EIP-712 clearance, bound to endpoint + amount EXECUTE x402 / Gateway Nanopayments · ERC-8183 escrow on Arc ↓ LEARN observed outcome → reputation on Arc

One decision core. Two ways to spend. Every score traceable to the evidence that produced it.

Autonomy is frozen

Nova proposes, and the owner signs every payment. On 26 September autonomous spending was frozen for every user:

  • AUTONOMY_FROZEN is a constant in lib/execution/autonomy-freeze.ts, not a setting, so no environment variable can undo it.
  • The autopilot route answers 503, and new AUTOPILOT mandates are refused.
  • The scheduled shadow pass stops before it reads a mandate.

Before the freeze, Nova rehearsed spending it could not do:

  • The owner signed an ExecutionMandate (EIP-712, v2, mode: PREVIEW). It named the capabilities, rails, spending ceilings and minimum trust score.
  • Every scheduled pass then ran the whole path for real: a question, discovery, a live price, Veyra's decision and all eleven mandate checks.
  • Each pass stopped one step before the only step that costs anything.

That epoch ended on 22 September, when its mandate expired. It was not renewed.

A PREVIEW mandate can never authorize a live payment. Execution refuses any

mode but AUTOPILOT. The decision table has no column for a signature, a

clearance, a transaction or a settled amount.

The next step keeps the owner in control. Nova will propose hiring a specific ERC-8004 agent for a task at a price, and the owner will confirm every hire.

Deterministic evaluator: lib/nova/autonomy.ts · the one mandate it issues: lib/nova/autonomy-mandate.ts

Why this exists

An autonomous agent with a funded wallet pays whoever answers first. It cannot tell a service that has settled 147 payments from one listed an hour ago, and it does not notice when the catalog price is no longer what the endpoint charges. Veyra answers the question that comes first: should I pay this endpoint at all, and for how much.

A first-contact endpoint never reaches ALLOW — not because it is bad, but because no settlement history exists for a counterparty nobody has paid yet. Veyra reports the absence of evidence instead of scoring around it.

Proof it works

A complete ERC-8183 job — creation, USDC escrow, deliverable, independent evaluation, payout — executed on Arc Testnet, with every step backed by a transaction hash:

Job#186207 on Arc Testnet
Lifecycle cost560,260 gas — 0.0118 USDC, about 1.2 cents
Time to payout19 seconds, createJob → USDC in the provider's wallet
Policy checks11 of 11 passed, deliverable re-fetched and re-hashed by the evaluator

Two rails, one decision core

The same engine, policy tiers, and EIP-712 clearance serve both. What differs is the candidate source and the shape of the evidence.

API purchaseAgent job
DiscoverCircle x402 marketplace · offers declared in the ERC-8004 registry on ArcERC-8004 IdentityRegistry on Arc
Evidencelive 402 probe, catalog drift, latencyonchain settlement history, evaluator verdicts
Executex402 / Gateway NanopaymentsERC-8183 job with USDC escrow
Verifyresponse validity, settlementindependent evaluator verdict, signed EIP-712

An x402 purchase settles wherever the endpoint sells, and Nova reads Arc first. On 23 September Circle's catalogue listed 482 offers on Arc mainnet and 1,009 on Base. Identity, authorization, attestation and escrow stay on Arc. The product says which chain a price is on, rather than letting the Arc heading imply one.

Settlement is a property of the endpoint too:

  • All 482 Arc offers take a batched Gateway accept. It spends a deposit already held in Circle's GatewayWallet, not the wallet's balance.
  • Only two of them also take a plain wallet payment.

A trust score is worth nothing if you cannot see what produced it, so every decision exposes its evidence: the live 402 challenge against the advertised one, settled ERC-8183 jobs and evaluator verdicts on Arc, observed latency and uptime over time, and project and treasury signals. These are inputs to a decision, not separate products.

Primitives

The standards Veyra is built on, in the role each one actually plays:

PrimitiveRole
NovaThe personal agent in front of all of it — watches, proposes, holds no key
ERC-8004Agent identity and reputation registries on Arc
ERC-8183Job lifecycle: escrow, deliverable, evaluation, settlement
Veyra Trust GateEIP-712 clearance, verified and consumed onchain
Veyra EvaluatorIndependent, fail-closed verdicts that authorize ERC-8183 payout
x402 / NanopaymentsGas-free USDC payment for an API call — a direct EIP-3009 authorization, or a batched Gateway accept where the endpoint takes one
MandatesEIP-712 budget and capability limits an agent operates under — PREVIEW rehearses, AUTOPILOT pays
Arc Proof RegistryVerified purchases written onchain: parties, amount, request and response hashes
LLM forms the intent. Veyra makes the financial decision.

The language model turns a request into a structured intent — capability, budget, priority — and decides what is worth asking. It does not choose who gets paid and it cannot reach the evaluator's inputs except by producing a proposal the market priced. Ranking, policy, exposure limits and the signed authorization are deterministic and reproducible from the evidence, so the same inputs always produce the same decision, and it can be audited later.

Veyra is itself an x402 resource

Discoverable and payable by the machinery it verifies, at /.well-known/x402. The verdict is free, with its evidence; the signed clearance costs, because a contract can consume an attestation and cannot consume an opinion. Reporting what happened after a purchase earns a credit toward the next one.

On Arc mainnet Veyra sells two answers of its own:

  • history, what it has observed of an endpoint, at 0.005 USDC;
  • select, a ranked choice of sellers for a task, at 0.02 USDC.

Both are paid only on Arc, through Circle Gateway, to Veyra's own Circle wallet. Credits do not pay there, and no clearance is signed there, because the Trust Gate is on Arc Testnet. See the OpenAPI document and the ERC-8004 registration.

Arc integration

| | Arc mainn

只显示了开头部分;其余内容请在仓库中阅读