ConduitConnect MCP

MCP / Base / x402

Your assistant's
wallet on Base

Conduit is an MCP server that gives AI assistants a secure channel to send USDC, sign transactions, and pay for APIs via x402. One config line in Cursor or Claude Desktop.

Add to MCP configSee the flow
12
MCP tools
Base
native
x402
built in
wallet.balancewallet.sendx402.fetchtx.signallowlist.checkspend.capwallet.balancewallet.sendx402.fetchtx.signallowlist.checkspend.cap

Flow

Three hops,
zero friction

The assistant never holds your keys. Conduit sits in the middle as a policy layer between natural language and on-chain action.

01 / Assistant

Asks to pay

Claude or Cursor calls an MCP tool when you ask it to send USDC, check balance, or fetch a paid API.

02 / Conduit

Validates and signs

Conduit checks spending caps, allowlists, and rate limits before signing. No raw keys ever reach the model.

03 / Base

Settles on-chain

Transactions and x402 payments land on Base in USDC. Sub-second confirmation, full audit trail.

Tools

MCP tools your
assistant can call

Each tool is typed, documented, and sandboxed. The model sees schemas, not private keys.

wallet.balance

Read USDC balance on Base for the connected address.

{ "address": "0x..." }
wallet.send

Transfer USDC with amount cap and recipient allowlist checks.

{ "to": "0x...", "amount": "10" }
x402.fetch

HTTP fetch with automatic x402 payment negotiation and settlement.

{ "url": "https://api.example/data" }
tx.sign

Sign typed data or transactions after policy validation.

{ "type": "eip712", "domain": {...} }
spend.get_cap

Return remaining daily and per-call spending limits.

{}
allowlist.check

Verify a contract or address is on the approved list.

{ "address": "0x..." }

Setup

One block in
your MCP config

Paste into Cursor, Claude Desktop, or any MCP-compatible client. Conduit starts locally and exposes wallet tools over stdio.

CursorClaude DesktopWindsurfCustom agents
mcp.json
{
  "mcpServers": {
    "conduit": {
      "command": "npx",
      "args": ["-y", "@conduit/mcp-server"],
      "env": {
        "CONDUIT_WALLET_KEY": "your-key-here",
        "CONDUIT_NETWORK": "base",
        "CONDUIT_DAILY_CAP": "100"
      }
    }
  }
}
Example tool call
// Assistant invokes via MCP
Tool: x402.fetch
Input: {
  "url": "https://chaineye.bazaar/query",
  "method": "POST",
  "body": { "chain": "eip155:8453" }
}

// Conduit response
{
  "status": 200,
  "paid": "0.01 USDC",
  "data": { "balance": "1240.50" }
}

Security

Policy layer,
not key export

Conduit is designed for assistants that act on your behalf. Every on-chain action passes through rules you define before it reaches Base.

Default posture

Deny by default

Unknown contracts, uncapped amounts, and unlisted recipients are blocked unless you explicitly allow them.

Keys stay local

Private keys live in env vars on your machine. The model only receives tool schemas and sanitized responses.

Spending caps

Set daily USDC limits and per-call maximums. Conduit rejects any transaction that exceeds policy.

Recipient allowlist

Restrict sends to approved addresses and contracts. Block unknown destinations by default.

Audit log

Every tool call, signature, and x402 payment is logged locally with timestamps and amounts.