@one-source/mcp

Unified MCP server for OneSource — 38 tools for blockchain data, live chain queries, and REST API documentation in a single server.

> What is MCP? The Model Context Protocol lets AI assistants call tools and access data sources. This server exposes both the OneSource blockchain API and its documentation as tools.

Quick Start

Claude Code

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

Claude Desktop / Cursor

Add to your MCP config:

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

Any MCP Client (stdio)

npx -y @one-source/mcp@latest

HTTP Server (self-hosted)

npx -y @one-source/mcp@latest --http
npx -y @one-source/mcp@latest --http --port=8080

Then connect your MCP client to `http://localhost:3000/` (or your `--port` value, e.g. `8080` in the second example above).

Health check: `GET http://localhost:3000/health` (substitute your port).

Tools (38)

Blockchain API — Live Chain (12 tools)

Blockchain API — Chain Utilities (13 tools)

RPC only.

Payments (2 tools)

Documentation (8 tools)

No authentication required. These answer from a documentation corpus bundled with the server, so they cost nothing and work even before a payment method is configured. They share their names with the standalone `@one-source/docs-mcp` server, which serves the same corpus.

Setup & Ops (3 tools)

No authentication required.

Networks

All blockchain API tools accept an optional `network` parameter:

Authentication

Blockchain API tools require authentication. Three options are available — if an API key is set alongside a wallet key, the API key takes priority and the wallet is ignored.

> Tip: the fastest way to configure any of these is the `1s_setup_check` tool — it walks you through every option interactively and hands you a ready-to-run command, so you never have to hand-edit env vars or config files. The manual instructions below are the reference.

Option 1: API Key

1. Go to app.onesource.io and create an account.

2. Complete the API key subscription through Stripe checkout.

3. Navigate to API Keys and generate a key.

4. Copy the key — it starts with `sk_`.

Claude Code

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

Claude Desktop / Cursor

Add the `env` block to your MCP config:

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

Any MCP Client (stdio)

ONESOURCE_API_KEY= npx -y @one-source/mcp@latest

After adding, reload the MCP server and call `1s_setup_check` — under Current configuration it should report Active auth method: API key (with the first 6 characters of your key).

Option 2: x402 Micropayments

Blockchain API endpoints are priced in USDC on Base via x402. When you set `X402_PRIVATE_KEY`, the server automatically handles payments — tool calls are paid and retried transparently without any extra work from the agent.

1. Get an EVM private key — export one from MetaMask, Coinbase Wallet, or any EVM wallet, or generate a fresh one. The key is a 64-character hex string. The `0x` prefix is optional — both formats are accepted.

2. Pass the key to the server using one of the methods below.

3. Reload and find your wallet address — reload the MCP server, then call `1s_setup_check`. Under Current configuration it lists your x402 (Base) wallet — the address derived from your key.

4. Fund that address with USDC on Base — send USDC to the address shown in `1s_setup_check`, on the Base network. A few dollars ($1–5 USDC) is enough for hundreds of calls. If your USDC is on Ethereum mainnet, bridge it using the Base Bridge.

5. Verify — call `1s_network_info` for ethereum. If it returns chain data (block number, gas price), x402 payments are working end-to-end.

Claude Code

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

Claude Desktop / Cursor

Add the `env` block to your MCP config:

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

Any MCP Client (stdio)

X402_PRIVATE_KEY= npx -y @one-source/mcp@latest

Option 3: MPP Micropayments (Tempo)

Blockchain API endpoints can also be paid on the Tempo network via MPP — an alternative to x402 on Base. When you set `MPP_PRIVATE_KEY`, the server handles payments automatically; tool calls are paid and retried transparently.

1. Get an EVM private key — same format as x402 (64-char hex, `0x` optional). Export one or generate a fresh key.

2. Pass the key to the server using one of the methods below.

3. Reload and find your wallet address — reload the MCP server, then call `1s_setup_check`. Under Current configuration it lists your MPP (Tempo) wallet — the address derived from your key.

4. Fund that address with USDC.e or pathUSD on Tempo — a few dollars covers hundreds of calls.

5. Verify — call `1s_network_info`. If it returns chain data, MPP payments are working end-to-end.

Claude Code

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

Claude Desktop / Cursor

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

Any MCP Client (stdio)

MPP_PRIVATE_KEY= npx -y @one-source/mcp@latest

By default MPP pays per call (`mpp-charge`). For a burst of calls, switch to a Tempo voucher channel with `1s_payment_mode { "mode": "mpp-session" }` (or set `MPP_PAYMENT_MODE=session`) — one deposit funds many off-chain calls; reclaim the unspent balance any time with `1s_refund`, or it settles automatically on clean shutdown.

Config File Locations

If you prefer editing the config file directly instead of using CLI commands:

Add the `onesource` entry inside `"mcpServers"` using the JSON block shown above.

Alternative: Set as an Environment Variable

Instead of the `env` config block, you can set any of these variables as a shell or system environment variable: `export ONESOURCE_API_KEY=` (bash/zsh) or `$env:ONESOURCE_API_KEY = ""` (PowerShell). Set it at the OS level for persistence across sessions.

Payment channels (optional)

By default each paid call signs one payment per call (`x402-exact` on Base, `mpp-charge` on Tempo). For a burst of calls, open a payment channel — one on-chain deposit funds many off-chain calls, settled together — which is cheaper than paying per call:

• x402 (Base): switch to `x402-batch` with `1s_payment_mode { "mode": "x402-batch" }` (or `X402_PAYMENT_MODE=batch`). The first call deposits `price × X402_DEPOSIT_MULTIPLIER` (default 10).
• MPP (Tempo): switch to `mpp-session` with `1s_payment_mode { "mode": "mpp-session" }` (or `MPP_PAYMENT_MODE=session`). The first call deposits up to `MPP_MAX_DEPOSIT` (default 1).

Reclaim the unused balance any time with the `1s_refund` tool (works for both rails); the residual is always recoverable on-chain. An idle x402 channel also auto-refunds after a few hours, and an MPP session settles automatically on clean shutdown.

When paying via a wallet, the agent receives channel guidance in its system prompt at startup, so it can manage this for you rather than leaving it as a manual step: when it anticipates a burst of calls it offers to switch to the channel mode for the active rail and reminds you to `1s_refund` when finished. Control how proactive it is with `X402_BATCH_PROMPT` (`ask` / `auto` / `off`) and `X402_BATCH_THRESHOLD` (how many anticipated calls count as a burst — shared across both rails) — see Environment Variables. `1s_setup_check` reports your current mode, whether the channel is available, and all settings.

Security

Never commit keys to source control. Use environment variables, a `.env` file (excluded from git), or a secrets manager.

> After any config change: Run `/reload-plugins` in Claude Code, or restart Claude Desktop / Cursor. The MCP server must be reloaded to pick up new environment variables.

Environment Variables

Required

Set one to access the blockchain API tools. Without any, only the no-auth Setup & Ops tools work. The API key takes priority when set alongside a wallet key.

Optional / Advanced

All have sensible defaults — channel modes run out of the box. Set these only to override an endpoint, tune how channel modes behave, or adjust analytics. Payment modes can also be switched at runtime with the `1s_payment_mode` tool. The channel knobs below (`X402_PAYMENT_MODE`, `X402_DEPOSIT_MULTIPLIER`, `MPP_PAYMENT_MODE`, `MPP_MAX_DEPOSIT`, `X402_BATCH_PROMPT`, `X402_BATCH_THRESHOLD`) can be set and persisted from a session with the `1s_batch_config` tool — no config editing or restart required; a saved config takes priority over these env vars.

Troubleshooting

`1s_setup_check` shows "Active auth method: none" (blockchain tools locked)

Under Current configuration, "Active auth method: *none*" means no authentication is set. Set one of `ONESOURCE_API_KEY` (API key), `X402_PRIVATE_KEY` (x402 on Base), or `MPP_PRIVATE_KEY` (MPP on Tempo) — or just run `1s_setup_check` and let it walk you through it. Reload the MCP server after setting any variable (see note above). If the key still isn't reaching the server, set it as a shell environment variable directly.

Getting 403 / wrong key active despite correct setup

A key set in your shell profile (e.g. `~/.zshrc`, `~/.bash_profile`) is picked up by the MCP server process even if it isn't in your Claude MCP config. Run `echo $ONESOURCE_API_KEY` in your terminal to check. If it prints a value you didn't intend, unset it (`unset ONESOURCE_API_KEY`) or explicitly clear it when adding the server: `claude mcp add onesource -e ONESOURCE_API_KEY= -e X402_PRIVATE_KEY= -- npx -y @one-source/mcp@latest`. `1s_setup_check` shows the first 6 characters of whichever key is active so you can confirm which one the server is using.

Instructions show wrong auth method after reinstall

`/reload-plugins` in Claude Code reconnects tools but may not refresh the system prompt the LLM sees. If you switch auth method (e.g. API key → x402), do a full Claude Code restart to ensure the instructions reflect the new auth.

"MCP server onesource already exists" error

Run `claude mcp remove onesource` first, then re-add with your updated config.

Windows: `npx` requires `cmd /c` wrapper

Claude Code's `/doctor` command may warn about this. Update your MCP config to use `"command": "cmd"` with `"args": ["/c", "npx", "-y", "@one-source/mcp@latest"]`.

`npx` hangs with no output

That's normal — stdio mode waits for JSON-RPC input on stdin. Use `--http` if you want an HTTP server you can curl.

Port already in use

Specify a different port: `npx -y @one-source/mcp@latest --http --port=8080`

Registry Publishing

This package is listed on the official MCP Registry under the verified namespace `io.onesource/mcp` and on Glama. When releasing a new version, update both registries.

MCP Registry

First-Time Setup

1. Install Go

Download the installer for your platform from go.dev/dl and run it. Verify:

go version

2. Install mcp-publisher

go install github.com/modelcontextprotocol/registry/cmd/mcp-publisher@latest

If the Go module path has changed and the command fails, download the binary directly from the mcp-publisher GitHub releases page instead.

On Windows, add Go's bin directory to your PATH if the command isn't recognized:

$env:PATH += ";$env:USERPROFILE\go\bin"

Verify:

mcp-publisher --help

3. DNS Authentication (already done)

The `onesource.io` domain has a DNS TXT record that proves ownership of the `io.onesource` namespace. This is already configured — you don't need to redo it.

The record is on the root domain (`onesource.io`, not `_mcp-registry.onesource.io`):

v=MCPv1; k=ed25519; p=7D3U5rufgNXb/lH2MthTRZdDzEGeE7/Jvg8YkiArQc8=

You can verify it resolves:

nslookup -type=TXT onesource.io 8.8.8.8

4. Get the Private Key

Authentication requires the ed25519 private key in hex format that corresponds to the public key in the DNS record. Ask the team lead for this key — it's stored in the team's password manager / vault.

If you need to regenerate the keypair (this invalidates the current DNS record and requires updating it):

1. Generate a new ed25519 keypair (e.g., `openssl genpkey -algorithm Ed25519 -out key.pem`)

2. Extract the raw 32-byte private key seed and convert to hex:

openssl pkey -in key.pem -outform DER | tail -c 32 | xxd -p -c 32

3. Extract the public key in base64 for the DNS TXT record:

openssl pkey -in key.pem -pubout -outform DER | tail -c 32 | base64

4. Update the DNS TXT record on `onesource.io` with the new public key:

v=MCPv1; k=ed25519; p=

5. Wait for DNS propagation before attempting to log in.

Publishing a New Version

> Use the release script. Releases are normally run via the coordinated release

> script in the sre-services repo (`scripts/release-mcp.mjs` — see `sre-services/RELEASING.md`),

> which performs all of the steps below across both `@one-source/api-mcp` and

> `@one-source/mcp` in the correct order, including the `server.json` bump and

> `mcp-publisher publish`. The First-Time Setup above is still the prerequisite for

> the registry step. The manual steps below are the fallback for registry-only fixes

> or when the script can't run.

Every time you release a new npm version, update the MCP Registry:

1. Publish to npm (the registry validates the package exists, so this must happen first):

npm run build
   npm publish --access public

2. Update `server.json` — set both `version` fields to match the new npm version:

{
     "version": "x.y.z",
     ...
     "packages": [{ "version": "x.y.z", ... }]
   }

The `mcpName` field in `package.json` must be `"io.onesource/mcp"` and must match the `name` field in `server.json`. This is already set — don't remove it.

3. Authenticate (tokens expire, so do this each time):

mcp-publisher login dns --domain onesource.io --private-key

4. Publish to the registry:

mcp-publisher publish

5. Verify:

curl "https://registry.modelcontextprotocol.io/v0.1/servers?search=onesource"

Glama

Glama auto-syncs from the GitHub repo daily. No manual steps needed after a release — just make sure changes are pushed to `develop` (the default branch). The `glama.json` file in the repo root controls ownership. Manual re-sync is available from the Glama admin panel after claiming the server.

Privacy Policy

Use of this extension connects to the OneSource API. See the OneSource Privacy Policy for details on how data is handled.

License

Apache 2.0 — see LICENSE for details.