arbitova-mcp-server
Arbitova
Nicht-verwahrter USDC-Treuhandservice + KI-Schiedsverfahren für Agent-zu-Agent-Zahlungen auf Base.
Zwei Agenten sperren USDC in einen Vertrag, einer liefert, der andere bestätigt oder ficht an, und ein neutraler KI-Schiedsrichter entscheidet. Arbitova hält niemals das Geld — das tut der Vertrag.
Keine API-Schlüssel. Keine Registrierung. Keine Verwahrung. Ihre Ethereum-Adresse ist Ihre Identität.
Vertrag:
EscrowV1unter0xA8a031bcaD2f840b451c19db8e43CEAF86a088fCauf Base Sepolia — verifiziert auf Basescan, Mainnet-Start nach AuditSpezifikation:
A2A-ESCROW-RFC-v0.1Maschinenlesbarer Deskriptor:
/.well-known/arbitova.jsonDashboard für Urteile pro Fall: arbitova.com/verdicts
Integrationspfade: arbitova.com/integrate (Rohvertrag / Referenz-SDKs / Agent-nativ)
Referenz-UI (nicht kanonisch, für Menschen): arbitova.com/pay
15-minütiges Tutorial:
docs/tutorials/15-min-paid-agent.md
Warum existiert dies?
Jede A2A / Agent-Commerce-Spezifikation, die es gibt — MCP, Googles A2A, ERC-7683, Coinbases Agent Commerce — definiert, wie Agenten kommunizieren. Keine davon definiert, wie Geld fließt, wenn die Agenten einander nicht vertrauen.
Arbitova ist das fehlende Abwicklungs-Primitiv:
Deterministische Zustandsmaschine.
createEscrow → markDelivered → {confirmDelivery | dispute → resolve | cancel}. Keine versteckten Verzweigungen, keine Admin-Überschreibung.Keine automatische Freigabe nach Zeitablauf. Prüffenster laufen in
DISPUTEDaus, nicht in eine Verkäuferauszahlung. Schweigen ist sicherer als eine falsche Bestätigung.Content-Hash on-chain fixiert. Verkäufer können die Lieferdatei nicht austauschen, nachdem der Käufer sie geprüft hat.
Transparenz der Urteile pro Fall. Jede Entscheidung des Schiedsrichters ist ein signierter JSON-Blob; dessen
keccak256ist on-chain gespeichert. Die vollständige Urteilshistorie ist unter/verdictsabfragbar — keine Aggregation, keine Verzögerung.
Dies ist kein Marktplatz. Es gibt kein Arbitova-Konto, keine Einstellgebühr, keine Pro-Stufe. Das Protokoll ist das gesamte Produkt.
Related MCP server: idios
Schnellstart — Node.js SDK
npm install @arbitova/sdk ethersimport { Arbitova } from '@arbitova/sdk';
const buyer = await Arbitova.fromPrivateKey({ privateKey: process.env.BUYER_PK });
const { escrowId, txHash } = await buyer.createEscrow({
seller: process.env.SELLER_ADDRESS,
amount: '5.00',
deliveryHours: 24,
reviewHours: 24,
verificationURI: 'https://example.com/spec.json',
});
console.log(`Escrow #${escrowId} locked — ${buyer.explorerTx(txHash)}`);Verkäuferseite, Schiedsrichterseite, Browser-Wallet-Integration: siehe packages/sdk-js/README.md.
Schnellstart — Python SDK
pip install "arbitova[path_b]"from arbitova import path_b
result = path_b.arbitova_create_escrow(
seller="0x...",
amount=5.00,
verification_uri="https://example.com/spec.json",
)
print(result)Schnellstart — Claude / beliebiger MCP-Client
{
"mcpServers": {
"arbitova": {
"command": "npx",
"args": ["-y", "@arbitova/mcp-server"],
"env": {
"ARBITOVA_RPC_URL": "https://sepolia.base.org",
"ARBITOVA_ESCROW_ADDRESS": "0xA8a031bcaD2f840b451c19db8e43CEAF86a088fC",
"ARBITOVA_USDC_ADDRESS": "0x036CbD53842c5426634e7929541eC2318f3dCF7e",
"ARBITOVA_AGENT_PRIVATE_KEY": "0x..."
}
}
}
}Sechs Tools: arbitova_create_escrow, arbitova_mark_delivered, arbitova_confirm_delivery, arbitova_dispute, arbitova_cancel_if_not_delivered, arbitova_get_escrow. Alle signieren lokal via ethers v6. Ihr privater Schlüssel verlässt niemals den Prozess.
Lassen Sie ARBITOVA_AGENT_PRIVATE_KEY für den schreibgeschützten Introspektionsmodus weg (nützlich für Beobachtbarkeit).
Lebenszyklus
┌──────────────────┐
│ CREATED │ buyer locked USDC
└────────┬─────────┘
│
▼ seller.markDelivered()
┌──────────────────┐
│ DELIVERED │ deliveryHash on-chain
└────────┬─────────┘
│
buyer.confirmDelivery()│ │ buyer.dispute()
│ │ or seller.dispute()
▼ ▼
┌─────────────┐ ┌──────────┐
│ RELEASED │ │ DISPUTED │ waiting for arbiter
└─────────────┘ └────┬─────┘
│ arbiter.resolve(bps split + verdictHash)
▼
┌──────────┐
│ RESOLVED │
└──────────┘Zwei Endzustände sind nicht gezeichnet: CANCELLED (Käufer ruft cancelIfNotDelivered nach Lieferfenster auf) und automatische Eskalation in DISPUTED, wenn das Prüffenster ohne Bestätigung abläuft.
Framework-Referenzagenten
Drei End-to-End A2A-Demos auf Base Sepolia mit einem Live-KI-Schiedsrichter:
Claude Agent SDK — In-Process MCP-Tools
LangGraph — ReAct-Agent, Käufer + Verkäufer + Schiedsrichter
CrewAI — Agent + Aufgabe + Crew
Jede Demo führt den vollständigen CREATED → DELIVERED → CONFIRMED (oder DISPUTED → RESOLVED) Ablauf mit echten On-Chain-Transaktionen aus.
Pakete
Paket | Zweck |
Node.js / Browser SDK ( | |
Python SDK, Installation mit | |
MCP-Server (6 On-Chain-Tools) für Claude Desktop, Claude Code, jeden MCP-Client |
Jedes liefert dieselbe Oberfläche mit sechs Einstiegspunkten, sodass ein Agent, der das Python-SDK verwendet, mit einem Agenten abrechnen kann, der den MCP-Server verwendet — sie greifen auf denselben Vertrag zu.
Gebühren
| Wann | Gebühr | Gezahlt von | |
Available Tools
7 toolsarbitova_cancel_if_not_deliveredA
Buyer cancels an escrow after the delivery deadline has passed and the seller has not marked delivery. Full USDC refund to buyer. Only callable by the buyer, only after deliveryDeadline has elapsed, and only when escrow is still in CREATED state. Call arbitova_get_escrow first to verify the deadline has passed and status is CREATED before calling this.
Inputs: escrowId (required).
arbitova_confirm_deliveryA
Confirm that the seller has delivered and the output meets ALL criteria in the escrow's verificationURI. ONLY call after you have: (1) fetched the delivery payload, (2) fetched and parsed the verificationURI criteria document, (3) compared the payload against EVERY criterion, (4) are fully confident every criterion is satisfied. If anything is missing, wrong, ambiguous, incomplete, or the seller did not deliver the agreed output — DO NOT call this. Call arbitova_dispute instead with a specific reason citing the failed criterion. Silence is safer than a wrong confirmation: if you do not confirm within the review window, funds auto-escalate to AI arbitration, which protects the buyer by independently evaluating delivery.
Inputs: escrowId (required).
arbitova_create_escrowA
Buyer locks USDC into the Arbitova EscrowV1 smart contract. Calls USDC.approve() then createEscrow() on-chain. Requires USDC balance >= amount. deliveryWindowHours = how long the seller has to deliver (default 24). reviewWindowHours = how long the buyer has to verify after delivery is marked (default 24). verificationURI must point to a publicly fetchable JSON document listing every criterion the delivery will be checked against. If the review window expires without confirmation or dispute, funds auto-escalate to arbitration. Silence protects the buyer — you do NOT need to confirm promptly.
Inputs: seller (required), amount (required), verificationURI (required), deliveryWindowHours, +1 more.
arbitova_disputeA
Open a dispute when delivery is missing, incorrect, incomplete, or violates the verification criteria. Disputes trigger AI arbitration which independently evaluates the delivery and can split funds fairly. Call this whenever arbitova_confirm_delivery feels uncertain — when in doubt, dispute. The reason field MUST cite specific criteria from verificationURI that were not met, e.g. "Delivery at [URI] is missing criterion 3: word count is 400 but spec requires >= 1000." Either the buyer OR the seller can open a dispute.
Inputs: escrowId (required), reason (required).
arbitova_escalate_if_expiredA
Permissionlessly escalate a DELIVERED escrow to DISPUTED after the review window has expired. Any address can call this — buyer, seller, or an independent watcher. Use when the buyer went silent past reviewDeadline: this unblocks the seller and routes the escrow into arbitration instead of leaving funds stuck. Only valid when status is DELIVERED and block.timestamp > reviewDeadline. Call arbitova_get_escrow first to verify status and deadline before calling this.
Inputs: escrowId (required).
arbitova_get_escrowA
Fetch the current on-chain state of an escrow: buyer, seller, amount, deadlines, status, verificationURI, and deliveryHash. Use this to check whether delivery has been marked before fetching the payload, and to verify the reviewDeadline before deciding to confirm or dispute. Status values: CREATED (awaiting delivery), DELIVERED (seller marked done, review window open), RELEASED (funds released to seller), DISPUTED (in arbitration), RESOLVED (arbiter resolved), CANCELLED.
Inputs: escrowId (required).
arbitova_mark_deliveredA
Called by the SELLER after completing the work and uploading the deliverable to a stable URL. deliveryPayloadURI must point to the completed, publicly fetchable deliverable — the contract hashes this URI on-chain. Do NOT call before work is actually done. Do NOT use a temporary or expiring URL. The arbiter will fetch this URI during dispute resolution — a broken or mismatched URL counts as non-delivery. Before calling: complete all work to spec, upload to a stable URL (IPFS or persistent storage), and verify the content matches every criterion in verificationURI.
Inputs: escrowId (required), deliveryPayloadURI (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 7 tools
Each tool targets a unique action in the escrow lifecycle (create, get, mark delivered, confirm, cancel, dispute, escalate). No two tools have overlapping purposes, and descriptions clarify exactly when each should be used.
All tools follow the pattern 'arbitova_<verb>_<condition>', using snake_case consistently. The names are descriptive and predictable, making it easy to infer the tool's action from its name.
7 tools is an ideal size for an escrow management server. Each tool serves a necessary function in the lifecycle without unnecessary redundancy or bloat.
The tool set covers the full escrow lifecycle: creation, status retrieval, delivery marking, confirmation/cancellation, dispute opening, and escalation. There are no obvious gaps that would hinder an agent from managing an escrow end-to-end.
Related MCP Connectors
Agent-to-agent escrow on Base. Post quests with ETH/USDC bounties and settle on-chain.
Escrow middleman for any deal between people or AI agents: USDC held in an audited contract.
Escrow protection for agent payments on Base — USDC held in smart contract until job completion.
Escrow protection for agent payments on Base — USDC held in smart contract until job completion.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceSettlement rails for AI labor — USDC escrow on Base Mainnet, 1% protocol fee, designed for autonomous agents. 10 MCP tools covering the full escrow lifecycle: * Quoting calldata for create-intent, submit-proof, release-funds (broadcast gated) * Single-call x402 payment binding (replaces the 5-step x402 dance with one HMAC-signed POST) * Server-side reputation from on-chain event scan * LiMIT
- AlicenseAqualityCmaintenancePrivate escrow for AI agent work on Beam mainnet an agent locks payment, the worker locks collateral, and delivery settles on hash match or review, with M of N arbitrator voting and slashable worker bonds as the dispute backstop. 22 tools cover the full contract lifecycle, and dispute voting is deliberately not an agent tool, so an agent can never rule in its own favour.26MIT
- AlicenseNot gradedqualityDmaintenanceMulti-party escrow and settlement for autonomous agent transactions with x402 micropayments and dispute resolution on Base, Ethereum, or Solana.MIT
- AlicenseAqualityBmaintenanceZero-key on-chain intelligence for Base, Ethereum, and Solana. Instant bytecode decompilation, honeypot detection, EIP-1967 proxy resolution, calldata/revert decoding, and pre-flight transaction simulation. No API keys or wallet connection required.7132MIT