Official description7 sourcesMCP servers8d ago
@arbitova/mcp-server
Arbitova Non-custodial USDC escrow + AI arbitration for agent-to-agent payments on Base.** Two agents lock USDC into a contract, one delivers, the other confirms or disputes, and a neutral AI arbiter resolves.
View on GitHub ↗Direct link · no redirect page
Config template (adjust for your client)
claude mcp add arbitova -- npx -y arbitova
A pasteable skeleton generated from the repository name. Check the project README for the exact package and arguments.
- Star count
- 2 ★ · jiayuanliang0716-max/Arbitova · read from the GitHub search API · (checked 2026-10-16 20:00:20)
- Source
- collected from the punkpeye/awesome-mcp-servers list · type: MCP server
- Harvest history
- first seen 2026-10-09 · last seen 2026-10-16 · seen 32× · listed by 7 sources
- Score
- score 703 · 2 ★ · 7 sources · mcp
FAQ (answers come from our records)
How do I install it?
We did not find an install command for this repository (our install coverage is only about 4%). Check its README or releases page.
Who is it for?
We filed it under these tags: MCP 服务. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository
jiayuanliang0716-max/Arbitova；first catalogued 2026-10-09；last seen 2026-10-16。There is no official certification or quality rating here — we record sources and dates only.Third-party quality signals
Arbitova
以下摘录自该仓库的 README（片段） · 在 GitHub 读完整 README →
**Non-custodial USDC escrow + AI arbitration for agent-to-agent payments on Base.**
Two agents lock USDC into a contract, one delivers, the other confirms or disputes, and a neutral AI arbiter resolves. Arbitova never holds the money — the contract does.
No API keys. No registration. No custody. Your Ethereum address is your identity.
- Contract: EscrowV1 at 0xA8a031bcaD2f840b451c19db8e43CEAF86a088fC on Base Sepolia — verified on Basescan, mainnet launching after audit
- Spec: A2A-ESCROW-RFC-v0.1
- Machine-readable descriptor: /.well-known/arbitova.json
- Per-case verdict dashboard: arbitova.com/verdicts
- Integration paths: arbitova.com/integrate (raw contract / reference SDKs / agent-native)
- Reference UI (non-canonical, for humans): arbitova.com/pay
- 15-minute tutorial: docs/tutorials/15-min-paid-agent.md
---
Why this exists
Every A2A / agent-commerce spec in the wild — MCP, Google's A2A, ERC-7683, Coinbase's Agent Commerce — defines *how agents talk*. None of them define *how money moves when the agents don't trust each other*.
Arbitova is the missing settlement primitive:
- **Deterministic state machine.** createEscrow → markDelivered → {confirmDelivery | dispute → resolve | cancel}. No hidden branches, no admin override.
- **No auto-release after timeout.** Review windows expire into DISPUTED, not into seller payout. Silence is safer than a wrong confirmation.
- **Content-hash pinned on-chain.** Sellers can't swap the delivery file after the buyer inspects.
- **Per-case verdict transparency.** Every arbiter decision is a signed JSON blob; its keccak256 is stored on-chain. The full verdict history is queryable at /verdicts — no aggregation, no delay.
This is not a marketplace. There is no Arbitova account, no listing fee, no Pro tier. The protocol is the whole product.
---
Quick start — Node.js SDK
Seller-side, arbiter-side, browser wallet integration: see packages/sdk-js/README.md.
Quick start — Python SDK
Quick start — Claude / any MCP client
Six tools: arbitova_create_escrow, arbitova_mark_delivered, arbitova_confirm_delivery, arbitova_dispute, arbitova_cancel_if_not_delivered, arbitova_get_escrow. All sign locally via ethers v6. Your private key never leaves the process.
Omit ARBITOVA_AGENT_PRIVATE_KEY for read-only introspection mode (useful for observability).
---
Lifecycle
Two terminal states not drawn: CANCELLED (buyer calls cancelIfNotDelivered after delivery window) and auto-escalation into DISPUTED if the review window expires without confirmation.
---
Framework reference agents
Three end-to-end A2A demos on Base Sepolia with a live AI arbiter:
- **Claude Agent SDK** — in-process MCP tools
- **LangGraph** — ReAct agent, buyer + seller + arbiter
- **CrewAI** — Agent + Task + Crew
Each demo runs the full CREATED → DELIVERED → CONFIRMED (or DISPUTED → RESOLVED) flow with real on-chain transactions.
---
Packages
| Package | Purpose |
|---|---|
| @arbitova/sdk | Node.js / browser SDK (ethers v6) |
Two agents lock USDC into a contract, one delivers, the other confirms or disputes, and a neutral AI arbiter resolves. Arbitova never holds the money — the contract does.
No API keys. No registration. No custody. Your Ethereum address is your identity.
- Contract: EscrowV1 at 0xA8a031bcaD2f840b451c19db8e43CEAF86a088fC on Base Sepolia — verified on Basescan, mainnet launching after audit
- Spec: A2A-ESCROW-RFC-v0.1
- Machine-readable descriptor: /.well-known/arbitova.json
- Per-case verdict dashboard: arbitova.com/verdicts
- Integration paths: arbitova.com/integrate (raw contract / reference SDKs / agent-native)
- Reference UI (non-canonical, for humans): arbitova.com/pay
- 15-minute tutorial: docs/tutorials/15-min-paid-agent.md
---
Why this exists
Every A2A / agent-commerce spec in the wild — MCP, Google's A2A, ERC-7683, Coinbase's Agent Commerce — defines *how agents talk*. None of them define *how money moves when the agents don't trust each other*.
Arbitova is the missing settlement primitive:
- **Deterministic state machine.** createEscrow → markDelivered → {confirmDelivery | dispute → resolve | cancel}. No hidden branches, no admin override.
- **No auto-release after timeout.** Review windows expire into DISPUTED, not into seller payout. Silence is safer than a wrong confirmation.
- **Content-hash pinned on-chain.** Sellers can't swap the delivery file after the buyer inspects.
- **Per-case verdict transparency.** Every arbiter decision is a signed JSON blob; its keccak256 is stored on-chain. The full verdict history is queryable at /verdicts — no aggregation, no delay.
This is not a marketplace. There is no Arbitova account, no listing fee, no Pro tier. The protocol is the whole product.
---
Quick start — Node.js SDK
Seller-side, arbiter-side, browser wallet integration: see packages/sdk-js/README.md.
Quick start — Python SDK
Quick start — Claude / any MCP client
Six tools: arbitova_create_escrow, arbitova_mark_delivered, arbitova_confirm_delivery, arbitova_dispute, arbitova_cancel_if_not_delivered, arbitova_get_escrow. All sign locally via ethers v6. Your private key never leaves the process.
Omit ARBITOVA_AGENT_PRIVATE_KEY for read-only introspection mode (useful for observability).
---
Lifecycle
Two terminal states not drawn: CANCELLED (buyer calls cancelIfNotDelivered after delivery window) and auto-escalation into DISPUTED if the review window expires without confirmation.
---
Framework reference agents
Three end-to-end A2A demos on Base Sepolia with a live AI arbiter:
- **Claude Agent SDK** — in-process MCP tools
- **LangGraph** — ReAct agent, buyer + seller + arbiter
- **CrewAI** — Agent + Task + Crew
Each demo runs the full CREATED → DELIVERED → CONFIRMED (or DISPUTED → RESOLVED) flow with real on-chain transactions.
---
Packages
| Package | Purpose |
|---|---|
| @arbitova/sdk | Node.js / browser SDK (ethers v6) |
- Source
- awesome · https://github.com/jiayuanliang0716-max/Arbitova
- Browse by field
- MCP servers
- Traction
- 2 ★
- added
- yesterday
More in MCP servers
Filed under
Every tag opens the full list for that filter. Counts are the live catalogue figures.