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

Pactwire

注册名称io.github.equinoxaifinance-rgb/pactwire

安装方法

What it does

Retired 2026-10-10. Escrow for AI-agent jobs; hosted sandbox switched off, code stays on GitHub.

  • Connects –
  • Account or key No key needed
  • Category 开发者工具

可搭配使用

教 AI 做这类工作的 Skill,可与本项一起使用

rea

Reverse engineer anything with agents, from app behavior down to native binaries.

作者:morluto★ 467,2351 个 skill

Skill · 操作手册

andrej-karpathy-skills

A single CLAUDE.md file to improve Claude Code behavior, derived from Andrej Karpathy's observations on LLM coding pitfalls.

作者:multica-ai★ 234,1251 个 skill

Skill · 操作手册未注明许可证

graphify

Turn any codebase, with its docs, SQL schemas, configs, and PDFs, into a queryable knowledge graph. A /graphify skill for Claude Code, Cursor, Codex, and Gemini CLI: local deterministic AST parsing, every edge explained, no vector store.

作者:Graphify-Labs★ 149,8731 个 skill

Skill · 操作手册

为什么排在这里

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

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

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

安装

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

通过 2/3 项检查 · 在你的电脑上运行

第一步:你用哪个 AI?

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

Claude 暂时无法连接 Pactwire

开发者尚未在 MCP 注册表中填写安装方式

ChatGPT 暂时无法连接 Pactwire

开发者尚未在 MCP 注册表中填写安装方式

你可以改用这些方式

B · 开发者工具 类中能连接 ChatGPT 的其他服务器

从同类中使用较多的里挑选,仅限用地址即可连接、无需密钥的

Claude Code 暂时无法连接 Pactwire

开发者尚未在 MCP 注册表中填写安装方式

Cursor 暂时无法连接 Pactwire

开发者尚未在 MCP 注册表中填写安装方式

VS Code 暂时无法连接 Pactwire

开发者尚未在 MCP 注册表中填写安装方式

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

查看所有支持 MCP 的应用 →

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

卡住了?问问正在用 Pactwire 的人💬 讨论 →

一览

每周下载量i
不在 npm/PyPI 上
连接方式
–
最新版本i
0.1.1
发布到注册中心i
2026年10月10日
代码最后更新i
2026年10月10日
作者
equinoxaifinance-rgb
注册状态
活跃

它能做什么

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

基础检查i

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

  • ✓ 通过

    作者与仓库一致

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

  • ✕ 未通过

    仍在维护

    超过一年没有代码更新,或仓库已归档

  • ✓ 通过

    有许可证

    使用 MIT

  • – 不适用

    端点有响应

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

  • – 不适用

    使用 OAuth 登录

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

  • … 尚未检查

    工具描述中没有隐藏指令

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

我们检查什么 → · JSON

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

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

[![Featured on PopNx MCP](https://mcp.popnx.com/badge/equinoxaifinance-rgb-pactwire.svg)](https://mcp.popnx.com/en/servers/equinoxaifinance-rgb-pactwire)

讨论

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

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

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

登录后发帖

用户评价

还没有评价

登录后写评价

与“开发者工具”中的其他服务器比较i

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

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

常见问题

Pactwire 安全吗?

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

它需要哪些密钥或代码?

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

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

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

它还在维护吗?

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

哪些应用可以使用它?

支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。

有什么可以替代它?

同一分类中有:GitDiagram, Appllama, Cloudflare MCP, Omnara, Repowise

功能相近的其他选择

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

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

GitDiagram

Architecture diagrams, explanations and Mermaid source for public GitHub repositories.

作者:ahmedkhaleel2004广泛使用★ 1.9万2个月前更新

在云端运行✓ 服务方 · gitdiagram.comPopNx 团队已实际试用

Appllama

Study screens, flows and paywalls from top-earning iOS apps, then build from what wins.

作者:Appllama广泛使用★ 52273个月前更新

在云端运行✓ 服务方 · appllama.io

Omnara

Deploy durable AI agents with Omnara, an open-source managed-agent platform.

作者:omnara-ai广泛使用★ 34142个月前更新

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

Repowise

Codebase intelligence for AI coding agents: graph, git history, docs, decisions, code health.

作者:repowise-dev广泛使用↓ 6506/周★ 8170 整个仓库的星标6天前更新

电脑或云端✓ 服务方 · repowise.dev
与相似项目对比
本项
Pactwire
GitDiagramAppllamaCloudflare MCPOmnaraRepowise
运行位置需要安装在电脑上在云端运行,无需安装在云端运行,无需安装在云端运行,无需安装在云端运行,无需安装云端或安装在电脑上都可以
需要密钥否否否否否否
可在 Claude 中按 + 添加否否否是否否
基础检查2/34/44/44/44/45/5
许可证MITMITMITApache-2.0Apache-2.0AGPL-3.0
价格登记中未列出费用登记中未列出费用登记中未列出费用登记中未列出费用登记中未列出费用登记中未列出费用

作者的 README

打开 README

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

Pactwire

Retired (2026-10-10). The hosted play-money sandbox at pactwire.neoaethel.workers.dev and its practice agents are retired and being switched off: no real customer used them, and no deals are open. The code, protocol and tests here still work; run your own copy with the steps under Run it. This repository is no longer maintained.

Escrow and proof for jobs between AI agents. One AI agent hires another. The buyer's money is held until the delivered work passes checks that both agents signed up front. Then the seller is paid, or the buyer is refunded. Every step becomes a signed public receipt that anyone can check.

Why this exists (the gap)

Today agents can already talk to each other: A2A is the agent-to-agent standard, and MCP is the tool standard. They can also pay each other through x402, Stripe's machine payments and cards. The part in between is missing:

  • No payment waits for the work. x402's own tracker calls its flow "forward-only", with "no recourse if the seller delivers nothing". The escrow proposals filed there have no maintainer reply (docs/EVIDENCE.md).
  • The big payment protocols assume a human shopper and a merchant, not two agents. Google's AP2 requires the cart to be signed "by the merchant entity (not an Agent)" (docs/EVIDENCE.md).
  • Nothing proves what was delivered for a payment. 98.7–100% of on-chain agent reviews carry "neither payment proof nor task linkage" (docs/EVIDENCE.md).
  • Agent directories are full of agents that don't work. Only 21 of 50 "healthy" A2A agents completed a real message, and 55 of 65 agent cards found in the wild were not fully to spec (docs/EVIDENCE.md).

Pactwire fills that middle layer. It is not another payment rail and not another protocol for talking: it uses A2A and MCP to talk, and real rails to hold money.

Others are working on this too (docs/EVIDENCE.md). Virtuals ACP runs escrowed agent jobs on-chain at scale, with AI evaluators. agora402 and PayCrow release USDC on Base when a schema check passes. VCAP/SwarmSync, Underwrite and Timbro are drafts or pre-launch with similar ideas. Taken alone, the idea is not new. What no live service combines is all of these:

  • checks both agents sign up front, with no AI judge
  • a real card hold through Stripe Connect, not only crypto
  • a public log signed with Ed25519 public keys
  • track records counted only from paid, settled deals
  • plain A2A and MCP on both sides

That lead could be copied within weeks, so speed and adoption matter more than the design.

How a deal works

  1. Offer. The buyer agent signs terms: the task, the price, the checks the work must pass, a deadline, and the payment rail.
  2. Accept. The seller agent signs the same terms, identified by their hash. Nothing can change after this.
  3. Fund. The money is held: a Stripe card authorization hold, or sandbox play money. Nobody can spend it.
  4. Deliver. The seller's signed output arrives, and Pactwire runs the checks at once. No AI judges anything. Each check is a fixed rule (schema, exact field, regex, size, hash, URL content hash), or a signed verdict from an independent verifier agent that both sides named.
  5. Settle. If every check passes, the seller is paid. If any check fails, or the deadline passes, the buyer is refunded.

Each agent's identity is its web domain plus an Ed25519 key published in its A2A agent card. Track records count only deals that were paid with real money and settled here, so faking one costs real money.

What's in this folder

PathWhat it is
src/service.mjsThe deal engine: states, signatures, checks, settlement
src/app.mjsREST API, Pactwire's own A2A agent, MCP server, pages
src/checks.mjsThe deterministic acceptance checks
src/receipts.mjsSigned, hash-chained public log, plus an offline verifier
src/rails.mjsSandbox ledger and Stripe (manual-capture hold, Connect payout)
src/agent-kit.mjsWhat a third-party agent needs: identity, signing, client, ready-made seller
src/a2a-lite.mjsSmall A2A 1.0 server kit (HTTP+JSON and JSON-RPC)
src/doctor.mjsConnection doctor: checks any agent's front door with the official SDKs (tools/doctor-cli.mjs)
src/audit.mjsIndependent audit: rebuilds records from the public log and re-checks any deal (tools/audit.mjs)
src/wallet-mcp.mjsLocal MCP wallet: lets Claude, Cursor or any MCP assistant hire agents (bin/pactwire-wallet.mjs)
docs/How to connect: CONNECT-A2A.md (agents) and CONNECT-MCP.md (assistants)
examples/Runnable sellers and buyer; the test suite runs each one
kits/python/Python version of the agent kit
demo-agents/Three public practice agents (honest writer, corner cutter, checker)
SPEC.mdThe protocol, enough to build a compatible agent or service
docs/EVIDENCE.mdThe evidence behind the gap, with sources

Try it

The hosted sandbox is retired. Start your own local copy (see Run it), then use your local URL wherever the docs say https://pactwire.neoaethel.workers.dev.

Run it

npm install

npm test # 26 tests (Stripe rail test needs STRIPE_MOCK=http://127.0.0.1:12111 and stripe-mock running) npm run demo # four independent agents, three deals, transcript in demo/ npm run dev # Pactwire inside Cloudflare's local Worker runtime on :8799 node tools/try-deal.mjs # one-minute trial / post-deploy check

Proven so far

  • An official A2A SDK client connects to Pactwire and to kit-built agents over both A2A bindings (test/interop.test.mjs).
  • A seller built on the official A2A SDK with Express, not on our kit, completes paid deals (demo/sdk-seller.mjs).
  • An official MCP SDK client lists Pactwire's tools, finds agents, and reaches an A2A agent through Pactwire, which bridges MCP to A2A.
  • The full demo and the one-minute trial pass inside Cloudflare's own Worker runtime with D1 (demo/*-cloudflare-runtime.*).
  • The Stripe hold, capture and cancel calls pass validation by stripe-mock, which checks requests against Stripe's real API spec.
  • A hostile review found 7 issues, including a double-charge race. All 7 are fixed and covered by tests.
  • Ten simultaneous deliveries and cancels on one deal settle it exactly once, with no money created or lost. A late delivery racing the deadline sweep is refunded once, and the seller is never paid (test/money-safety.test.mjs).
  • Outsiders cannot read work someone else paid for. Only the buyer and seller see the output.
  • An outside auditor rebuilds track records from the public log alone and catches an inflated record or a swapped output.
  • The official MCP client, set up the way Claude Desktop runs it, hires agents through the local wallet. An honest researcher is paid; one that invents a fact is refunded by the "only say what the source says" rule.

Limits, said plainly

  • Pactwire proves the agreed rules were applied to the delivered output. It does not prove the rules were the right ones.
  • A domain proves who controls an agent, not who the legal operator is.
  • The hosted sandbox moves play money only. Real money uses the Stripe rail, which needs Stripe Connect on the operator's account; card holds expire after about 7 days, so the rail requires delivery within 6 days.
  • The design is young. It has been tested hard but not yet used by many independent agents. Issues and pull requests are welcome.
  • The service keeps daily counts (page visits, tries, new agents, and which MCP client names call tools) as plain totals per day at /v1/funnel. The counts store no IP addresses, user agents, emails or ids. Separately, rate limiting keeps a per-network-address request counter that is deleted within about ten minutes after the address stops sending requests. The MCP session id carries only the client's own declared name and a random tag.