LABSCO SUMMARY

The docs tools work before you have paid for anything.

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.

What it is

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.

What you get

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

Requirements

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.

Setup effort

One command — npx -y @one-source/mcp@latest

See installation options

USE CASES

01

Answering a question about a wallet or contract

Read balances, holdings and transfer history straight from the chain instead of through a block explorer.

1s_erc20_balance_live1s_multi_balance_live1s_erc20_transfers_live

02

Finding the right REST endpoint for a task

Describe the task in plain language and get the endpoint, its parameters, its price and a runnable curl.

1s_search_use_cases1s_get_endpoint_reference

03

Debugging a contract call that reverts

Simulate the call, read the storage slot behind it, and check whether the address is a proxy.

1s_simulate_call1s_storage_read1s_proxy_detect

04

Setting up pay-per-call without editing config files

Run the setup check, pick a rail, and reclaim the deposit later if you stop using it.

1s_setup_check1s_payment_mode1s_refund

38 tools

Listed in project docs. Your client may show a different list.

1s_allowance_live

1s_contract_info_live

1s_erc1155_balance_live

1s_erc20_balance_live

1s_erc20_transfers_live

1s_erc721_tokens_live

1s_events_live

1s_multi_balance_live

1s_nft_metadata_live

1s_nft_owner_live

1s_total_supply_live

1s_tx_details_live

1s_block_by_number

1s_block_number

1s_chain_id

BEFORE YOU INSTALL

What to know first

Tools you get

38 tools named in the project's documentation.

Requires

npx on PATH

Optional

ONESOURCE_API_KEY in your environment
X402_PRIVATE_KEY in your environment
MPP_PRIVATE_KEY in your environment

INSTALLATION

Connect your client

Server setup

TERMINAL

npx -y @one-source/mcp@latest

MCP Clients

Claude Code

CLAUDE CODE · TERMINAL

claude mcp add onesource -- npx -y @one-source/mcp@latest

Claude Desktop, Cursor

JSON

{
  "mcpServers": {
    "onesource": {
      "command": "npx",
      "args": [
        "-y",
        "@one-source/mcp@latest"
      ],
      "env": {
        "ONESOURCE_API_KEY": "<YOUR_ONESOURCE_API_KEY>"
      }
    }
  }
}

The configuration on this page does not set X402_PRIVATE_KEY and MPP_PRIVATE_KEY; the project's instructions put them in a .env file. To supply them without depending on where the server looks for that file, use the block's "env" section.

Any MCP client

ANY MCP CLIENT · TERMINAL

ONESOURCE_API_KEY=<YOUR_ONESOURCE_API_KEY> npx -y @one-source/mcp@latest

OneSource MCP