arbitova-mcp-server
Arbitova
Escrow de USDC sin custodia + arbitraje mediante IA para pagos de agente a agente en Base.
Dos agentes bloquean USDC en un contrato, uno entrega, el otro confirma o disputa, y un árbitro de IA neutral resuelve. Arbitova nunca retiene el dinero; lo hace el contrato.
Sin claves API. Sin registro. Sin custodia. Tu dirección de Ethereum es tu identidad.
Contrato:
EscrowV1en0xA8a031bcaD2f840b451c19db8e43CEAF86a088fCen Base Sepolia — verificado en Basescan, mainnet se lanzará tras la auditoríaEspecificación:
A2A-ESCROW-RFC-v0.1Descriptor legible por máquina:
/.well-known/arbitova.jsonPanel de veredictos por caso: arbitova.com/verdicts
Rutas de integración: arbitova.com/integrate (contrato sin procesar / SDK de referencia / nativo para agentes)
Interfaz de usuario de referencia (no canónica, para humanos): arbitova.com/pay
Tutorial de 15 minutos:
docs/tutorials/15-min-paid-agent.md
Por qué existe esto
Cada especificación de A2A / comercio de agentes en el mercado — MCP, A2A de Google, ERC-7683, Agent Commerce de Coinbase — define cómo hablan los agentes. Ninguna define cómo se mueve el dinero cuando los agentes no confían entre sí.
Arbitova es la primitiva de liquidación que faltaba:
Máquina de estados determinista.
createEscrow → markDelivered → {confirmDelivery | dispute → resolve | cancel}. Sin ramas ocultas, sin anulación de administrador.Sin liberación automática tras tiempo de espera. Las ventanas de revisión expiran en
DISPUTED, no en el pago al vendedor. El silencio es más seguro que una confirmación incorrecta.Hash de contenido fijado en la cadena. Los vendedores no pueden cambiar el archivo de entrega después de que el comprador lo inspeccione.
Transparencia de veredictos por caso. Cada decisión del árbitro es un blob JSON firmado; su
keccak256se almacena en la cadena. El historial completo de veredictos se puede consultar en/verdicts— sin agregación, sin retraso.
Esto no es un mercado. No hay cuenta de Arbitova, ni tarifa de listado, ni nivel Pro. El protocolo es el producto completo.
Related MCP server: idios
Inicio rápido — SDK de Node.js
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)}`);Lado del vendedor, lado del árbitro, integración de billetera de navegador: ver packages/sdk-js/README.md.
Inicio rápido — SDK de Python
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)Inicio rápido — Claude / cualquier cliente MCP
{
"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..."
}
}
}
}Seis herramientas: arbitova_create_escrow, arbitova_mark_delivered, arbitova_confirm_delivery, arbitova_dispute, arbitova_cancel_if_not_delivered, arbitova_get_escrow. Todas firman localmente mediante ethers v6. Tu clave privada nunca abandona el proceso.
Omite ARBITOVA_AGENT_PRIVATE_KEY para el modo de introspección de solo lectura (útil para observabilidad).
Ciclo de vida
┌──────────────────┐
│ 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 │
└──────────┘Dos estados terminales no dibujados: CANCELLED (el comprador llama a cancelIfNotDelivered después de la ventana de entrega) y auto-escalada a DISPUTED si la ventana de revisión expira sin confirmación.
Agentes de referencia del framework
Tres demos de A2A de extremo a extremo en Base Sepolia con un árbitro de IA en vivo:
Claude Agent SDK — herramientas MCP en proceso
LangGraph — agente ReAct, comprador + vendedor + árbitro
CrewAI — Agente + Tarea + Equipo
Cada demo ejecuta el flujo completo CREATED → DELIVERED → CONFIRMED (o DISPUTED → RESOLVED) con transacciones reales en la cadena.
Paquetes
Paquete | Propósito |
SDK de Node.js / navegador ( | |
SDK de Python, instalar con el extra | |
Servidor MCP (6 herramientas en cadena) para Claude Desktop, Claude Code, cualquier cliente MCP |
Cada uno ofrece la misma superficie de seis puntos de entrada para que un agente que usa el SDK de Python pueda liquidar con un agente que usa el servidor MCP: ambos acceden al mismo contrato.
Tarifas
Cuándo | Tarifa | Pagado por |
| 0.5% | deducido del pago al vendedor |
El árbitro resuelve una disputa | 2% | dividido según el veredicto del árbitro |
Las tarifas se acumulan en el contrato. El protocolo funciona con ellas; no hay suscripción.
Redes
Red | Estado | Contrato |
Base Sepolia | en vivo, Circle USDC real |
|
Base mainnet | auditoría pendiente + árbitro multisig | TBA |
Consulta el Registro de desarrollo para el lanzamiento en mainnet.
Legado (Ruta A)
La v2.x de los SDK y la v3.4.0 del servidor MCP eran un cliente HTTP de custodia contra api.arbitova.com. Esa arquitectura tenía cuatro problemas estructurales (desviación entre BD y cadena, gas de billetera de custodia, ADMIN_KEY única, punto único de fallo WALLET_ENCRYPTION_KEY) y fue obsoleta en favor de la Ruta B: el diseño en cadena sin custodia descrito anteriormente.
Migración para usuarios de SDK:
sdk/MIGRATION_PATH_A_TO_B.mdMigración para usuarios de MCP:
mcp-server/MIGRATION.md
Los paquetes antiguos permanecen en npm/PyPI pero están obsoletos.
Licencia
MIT
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