Orchard Data MCP Server

orchard-data-mcp

MCP server for orchard-data — pay-per-call market data for AI agents over x402 (USDC micro-payments on Base). No account, no API key, no subscription.

Try it in 10 seconds — no wallet, no signup

npx -y orchard-data-mcp

Add it to any MCP client with no credentials at all:

{ "mcpServers": { "orchard-data": { "command": "npx", "args": ["-y", "orchard-data-mcp"] } } }

Two tools work immediately with no wallet configured:

Ask your agent for get_feed_status first. If the feeds are stale, you have learned that for free; nothing here hides staleness to sell you a call.

Paid tools cost $0.001–$0.10 and need a burner Base wallet with a few dollars of USDC — setup below. Without a key they explain what they would cost instead of failing silently.

What makes it worth paying for

A track record you can audit. Forecasts are timestamped before the outcome and scored server-side against what actually happened, under a fixed rule shipped inside the payload. Call get_track_record for $0.01 and check our accuracy before you trust anything else we sell. Almost nothing in this category lets you do that, because almost nothing in this category would survive it.

Plus an ML market-regime forecast and a news catalyst radar, produced by a real algorithmic trading system — refreshed ~15 min during US market hours, staleness always reported.

Tools

⭐ = unique to us, not repackaged vendor data.

The HTTP API carries more products than this server wraps — including narrow slices like /api/quote, /api/yields, /api/vix, /api/commodities, /api/crypto-spot, /api/etf-quotes, /api/wsb-mentions and /api/stocktwits-trending, plus a free full-sample response at /api/sample. See the manifest or openapi.json.

Paying for the paid tools

Paid tools need a small dedicated Base wallet holding USDC (a few dollars goes a very long way at these prices). Use a burner wallet, never your main one.

{
  "mcpServers": {
    "orchard-data": {
      "command": "npx",
      "args": ["-y", "orchard-data-mcp"],
      "env": { "EVM_PRIVATE_KEY": "0x<burner wallet private key>" }
    }
  }
}

Without EVM_PRIVATE_KEY the two free tools still work, and the paid tools explain what they would cost rather than failing silently.

How payment works

Each paid tool call: GET → HTTP 402 with payment requirements → the client signs a USDC transfer authorization with your key → retries with the payment header → JSON. Settlement is gasless for the buyer (EIP-3009 via the x402 facilitator). Verified end-to-end on Base mainnet.

The server can never charge more than the listed price. Before signing, the client checks the payment request against the tool's listed price — the one in its description and in the table above, which the test suite keeps identical. It must be USDC on Base, at or under that amount. Anything else — a bad deploy, a changed price, a mistyped ORCHARD_BASE_URL — is refused with no signature produced. A tool that is listed at $0.01 cannot cost you $1.

Errors say whether you paid. Every failure tells you whether a payment was signed, so you know whether a retry is safe. If a request dies after signing, the error says so and asks you to check the wallet before retrying, rather than inviting a retry that could pay twice.

Configuration

Development

npm test          # offline: stub API, real MCP stdio, real x402 signing with a throwaway key
npm run test:live # check against the production API — free, needs no funds

The offline suite covers the paid path end to end — including refusing an overpriced request — without touching the network or a real wallet. It also fails if this README's price table drifts from what the server charges.

test:live costs nothing. It checks the paid path with a freshly generated empty wallet: signing a payment authorization spends nothing, so production must reject it, and that rejection proves production's payment request passes the price cap. It ignores any EVM_PRIVATE_KEY in your environment, so it can never touch a real wallet.