Eight documentation tools answer from a corpus bundled with the server, so an agent can find the right endpoint and read its price before a payment method exists. That makes the first session useful rather than a configuration exercise, and `1s_setup_check` handles the rest of it interactively.
A single MCP server that exposes both the OneSource blockchain API and the documentation for it. It runs over stdio via `npx`, or as an HTTP server with `--http` when you would rather host it.
- Live chain (12 tools) — ERC20 balances and allowances, ERC721 and ERC1155 holdings, NFT metadata and owner, transfer and event logs, transaction details, total supply, contract type detection
- Chain utilities (13 tools) — block by number, latest block, chain ID, contract bytecode, ENS resolution, gas estimation, nonce, pending block, proxy detection, `eth_call` simulation, storage reads, receipts
- Documentation (8 tools) — search the docs, list every REST endpoint with its price, pull one endpoint in full with a curl example, find the endpoint for a plain-language task, and read the authentication guide
- Payments (2 tools) — `1s_payment_mode` switches between the x402 and MPP rails; `1s_refund` reclaims an open channel's unspent deposit
- Setup and ops (3 tools) — `1s_setup_check` walks the whole configuration interactively, `1s_batch_config` persists channel preferences, `1s_report_bug` files an issue
Node, via `npx -y @one-source/mcp@latest`. The documentation and setup tools need no credentials at all. Blockchain tools need one of three: `ONESOURCE_API_KEY` for unlimited calls with no per-call cost, `X402_PRIVATE_KEY` to pay per call in USDC on Base, or `MPP_PRIVATE_KEY` to pay per call on Tempo. If an API key and a wallet key are both set, the API key wins and the wallet is ignored. Chain tools take an optional `network` parameter: `ethereum`, `sepolia` or `robinhood`.
One command plus a key — npx -y @one-source/mcp@latest, then supply credentials