Log inSubmit server
MCP Server logo

MCP Server

by @arbitova

Non-custodial MCP tools for managing USDC escrow payments on Base Sepolia.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install MCP Server

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "arbitova-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "@arbitova/mcp-server"
      ],
      "env": {
        "ARBITOVA_RPC_URL": "YOUR_VALUE_HERE",
        "ARBITOVA_ESCROW_ADDRESS": "YOUR_VALUE_HERE",
        "ARBITOVA_USDC_ADDRESS": "YOUR_VALUE_HERE",
        "ARBITOVA_AGENT_PRIVATE_KEY": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

We couldn’t confirm it starts correctly

We ran the install command but it didn't respond within our test window — this can mean a slow first-time install rather than a real problem.

npx -y @arbitova/mcp-server

No response to initialize.

This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked 1mo ago.

Overview

@arbitova/mcp-server MCP server exposes six on-chain escrow tools for agent-to-agent USDC payments on Base Sepolia. It uses ethers v6 to sign transactions locally and interact directly with the EscrowV1 contract, without an API key or custodial service. Configure the RPC endpoint, contract addresses, and optionally a private key for write operations. Use it when agents need to create, deliver, confirm, dispute, cancel, or inspect escrowed payments.

Use cases

  • Create USDC escrows between autonomous agents
  • Record delivery with an on-chain content hash
  • Confirm or dispute agent payments
  • Inspect escrow state without transaction signing

Key features

  • Six on-chain escrow tools
  • Local ethers v6 transaction signing
  • Base Sepolia and USDC support
  • Read-only mode without a private key
  • Non-custodial contract-based settlement

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked Today

Recent health check succeeded.

96/96 checks healthy over the last 58d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 15d ago via OSV.dev · @arbitova/mcp-server (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars2Stargazers on the source repository.
npm downloads147Package downloads in the last 30 days.
Last commit6mo agoMost recent push to the default branch.
Install checkInconclusiveDidn't respond in our test window — often a slow first install.
Directory activity11 viewsConfig copies, upvotes, and views on AllMCPs.

How MCP Server works

What @arbitova/mcp-server MCP server does

The @arbitova/mcp-server MCP server gives MCP-compatible agents access to a non-custodial USDC escrow contract on Base Sepolia. It supports the main buyer and seller actions in the escrow lifecycle: creating an escrow, recording delivery, confirming delivery, opening a dispute, cancelling an undelivered escrow after the delivery window, and reading escrow state.

Funds remain in the EscrowV1 smart contract rather than in an Arbitova-operated wallet. The contract address documented for Base Sepolia is 0xA8a031bcaD2f840b451c19db8e43CEAF86a088fC, and the deployment uses Circle USDC on that network. Base mainnet is listed as pending audit and multisig arbiter support.

How it works

The agent connects to a configured Ethereum RPC endpoint and calls the deployed contract directly. Write requests are signed in the local process with ethers v6. The private key is not sent outside the process; omitting it starts read-only introspection mode for observing escrow data.

The supported flow begins when a buyer locks USDC for a seller. The seller can attach delivery information, including an on-chain content hash. The buyer can then confirm the delivery or either party can dispute it. A buyer can cancel when delivery has not occurred within the configured delivery window. Review-window expiry can move an escrow into a disputed state rather than automatically releasing funds.

The MCP package is one integration path for the same contract used by the project’s Node.js and Python SDKs. Arbiter resolution is described in the protocol documentation, but the README’s MCP tool list does not include a resolution tool.

Setup and configuration

Install and run the @arbitova/mcp-server MCP server with the package manager command shown in the project documentation:

Terminal
npx -y @arbitova/mcp-server

Configure these environment variables in the MCP client:

  • ARBITOVA_RPC_URL: RPC endpoint for the target network, shown with https://sepolia.base.org for Base Sepolia.
  • ARBITOVA_ESCROW_ADDRESS: deployed EscrowV1 contract address.
  • ARBITOVA_USDC_ADDRESS: USDC token contract address.
  • ARBITOVA_AGENT_PRIVATE_KEY: optional signing key for transactions.

The documented example uses Claude Desktop configuration, but the package is described as usable with any MCP client. A private key is needed for actions that submit transactions; read-only inspection works without it.

Tools and capabilities

The documented MCP entry points are:

  • arbitova_create_escrow to lock USDC for a seller with delivery and review periods.
  • arbitova_mark_delivered to record seller delivery and its content hash.
  • arbitova_confirm_delivery to confirm delivery and complete the normal release path.
  • arbitova_dispute to place an escrow into the dispute flow.
  • arbitova_cancel_if_not_delivered to cancel after the delivery window when delivery has not been recorded.
  • arbitova_get_escrow to inspect escrow state without a signing key.

Limitations and notes

The documented live deployment is Base Sepolia, not Base mainnet. Transactions require the relevant network assets and can incur the protocol fees described in the repository: 0.5% for confirmation or review-window expiry settlement, and 2% for arbiter dispute resolution. The project says its earlier custodial HTTP-based MCP architecture is deprecated; current integrations should use the non-custodial on-chain design.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about MCP Server

Run `npx -y @arbitova/mcp-server`.

Yes. The README provides a Claude Desktop configuration and states that the server also works with any MCP client.

Configure `ARBITOVA_RPC_URL`, `ARBITOVA_ESCROW_ADDRESS`, and `ARBITOVA_USDC_ADDRESS`. Add `ARBITOVA_AGENT_PRIVATE_KEY` for transaction signing; it is optional for read-only introspection.

No.

The documented live contract is on Base Sepolia. Base mainnet is listed as pending audit and multisig arbiter support.

Related MCP servers

All in Finance & Fintech All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewMCP Server AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/-arbitova-mcp-server?style=directory)](https://allmcps.com/mcp/-arbitova-mcp-server)
HTML Embed
<a href="https://allmcps.com/mcp/-arbitova-mcp-server"><img src="https://allmcps.com/api/badge/-arbitova-mcp-server?style=directory" alt="MCP Server on AllMCPs" /></a>