# @one-source/mcp Unified MCP server for [OneSource](https://docs.onesource.io) — 31 tools for blockchain data, live chain queries, and API documentation in a single server. Combines [`@one-source/api-mcp`](https://www.npmjs.com/package/@one-source/api-mcp) (22 tools) and [`@one-source/docs-mcp`](https://www.npmjs.com/package/@one-source/docs-mcp) (9 tools) so your AI assistant gets full access to OneSource with one MCP connection. > **What is MCP?** The [Model Context Protocol](https://modelcontextprotocol.io) 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 ```bash claude mcp add onesource -- npx @one-source/mcp ``` ### Claude Desktop / Cursor Add to your MCP config: ```json { "mcpServers": { "onesource": { "command": "npx", "args": ["-y", "@one-source/mcp"] } } } ``` ### Any MCP Client (stdio) ```bash npx @one-source/mcp ``` ### HTTP Server (self-hosted) ```bash npx @one-source/mcp --http npx @one-source/mcp --http --port=8080 ``` Then connect your MCP client to `http://localhost:3000/`. ## Tools (31) ### Blockchain API — Live Chain (12 tools) | Tool | Description | |------|-------------| | `1s_allowance_live` | ERC20 allowance check | | `1s_contract_info_live` | Contract type detection via ERC165 | | `1s_erc1155_balance_live` | ERC1155 balance via RPC | | `1s_erc20_balance_live` | ERC20 balance via balanceOf | | `1s_erc20_transfers_live` | ERC20 Transfer logs via eth_getLogs | | `1s_erc721_tokens_live` | ERC721 token enumeration | | `1s_events_live` | Event logs via eth_getLogs | | `1s_multi_balance_live` | ETH + multiple ERC20 balances | | `1s_nft_metadata_live` | NFT metadata via tokenURI | | `1s_nft_owner_live` | NFT owner via ownerOf | | `1s_total_supply_live` | Token total supply | | `1s_tx_details_live` | Transaction + receipt via RPC | ### Blockchain API — Chain Utilities (10 tools) | Tool | Description | |------|-------------| | `1s_contract_code` | Contract bytecode | | `1s_ens_resolve` | ENS name/address resolution | | `1s_estimate_gas` | Gas estimation | | `1s_network_info` | Chain ID, block number, gas price | | `1s_nonce` | Transaction count | | `1s_pending_block` | Pending block from mempool | | `1s_proxy_detect` | Proxy contract detection | | `1s_simulate_call` | Simulate eth_call | | `1s_storage_read` | Read storage slot | | `1s_tx_receipt` | Transaction receipt | ### Documentation (9 tools) Read-only, no API key required. | Tool | Purpose | When to use | |------|---------|-------------| | `search_docs` | Keyword search across all documentation | Finding guides, concepts, or API patterns | | `get_query_reference` | Full reference for a root GraphQL query | Building a specific query with correct args/filters | | `get_type_definition` | Schema definition for any type/enum/input | Understanding field shapes and return types | | `list_examples` | Browse or search working GraphQL examples | Finding ready-to-use query patterns | | `list_supported_chains` | All supported blockchain networks + endpoints | First question: "What chains are supported?" | | `get_filter_reference` | Filter fields and operators for a list query | Building filtered queries with correct syntax | | `get_pagination_guide` | Cursor-based pagination pattern with examples | Implementing pagination for list queries | | `get_schema_overview` | High-level summary of the entire schema | Exploring the API surface before diving in | | `get_authentication_guide` | API key format, headers, and endpoints | Setting up authentication for the first time | ## Networks All blockchain API tools accept an optional `network` parameter: | Network | Description | |---------|-------------| | `ethereum` | Ethereum mainnet (default) | | `sepolia` | Ethereum Sepolia testnet | | `avax` | Avalanche C-Chain | ## Payment (x402) Blockchain API endpoints are priced in USDC on Base via [x402](https://github.com/coinbase/x402). When the backend has payments enabled, tool calls return a 402 with payment details. Agents using [`@x402/fetch`](https://www.npmjs.com/package/@x402/fetch) handle this automatically. Documentation tools are always free — no API key or authentication needed. ## License Apache 2.0

MCP readiness

B · 88/100

Readiness is how fully this listing follows its protocol and how it behaved in our probes over 30 days. It is shown for reference and does not move it in search. Search order and leaderboards use the separate quality grade (here C+, 71.8/100), which weighs availability, conformance, p95 speed and descriptor. How the two differ

Valid MCP handshake	10/10	initialize and tools/list both answered.
Live MCP endpoint	25/25	Endpoint answers the MCP initialize handshake (1883 ms).
Protocol revision	8/10	Speaks MCP 2025-11-25, 1 revision(s) behind 2026-07-28.
Signed descriptor	n/a	No MCP standard defines a signed server descriptor.
Uptime (30 days)	15/15	31/31 probes succeeded over 30 days (100%).
Tool declaration	10/10	Lists 60 tool(s) with descriptions.
Verified identity	5/10	Publisher declared (repository, package or homepage); claim this listing to verify domain control.
Freshness + modern flags	4/5	seen in a source within 7 days.
Auth declaration	2/5	Declares credential scheme: smithery_api_key.

Applicable criteria total 90 points, scaled to 100.

Responsiveness: Responsive (1883 ms; bands ≤2.5 s, ≤5 s, ≤8 s, slower; penalty only).

Measured 2026-11-11.

Nine criteria, the same as the A2A readiness score, read from our daily MCP probe (initialize + tools/list) and 30-day probe history. No MCP standard defines a signed server descriptor, so that criterion is n/a and the other 90 points are scaled to 100. Grades: A>=90, B>=75, C>=60, D>=40, F<40. Display only: search order uses the quality grade.

Compared with peers

Against 53,021 reachable MCP servers in our daily snapshot (2026-11-12 01:39 UTC). Display only; it does not change search order.

Readiness: Higher than 95% of peers; This listing 88 · peer median 81
Latency: Faster than 22% of peers; This listing 601 ms · peer median 326 ms

Where it loses the most points, and how to win them back

Verified identity −5 — Claim the listing and prove control of its domain.
Now: Publisher declared (repository, package or homepage); claim this listing to verify domain control.
Auth declaration −3 — State how to authenticate (an auth scheme, or that none is needed).
Now: Declares credential scheme: smithery_api_key.
Protocol revision −2 — Support the current protocol revision.
Now: Speaks MCP 2025-11-25, 1 revision(s) behind 2026-07-28.

How many agent tools actually work · All statistics

Listed in

Directories this entry was found in.

smithery since 2026-06-04 ↗

How to connect

MCP endpoint (streamable-http)

https://server.smithery.ai/one-source/mcp-1s/mcp

JSON-RPC initialize probe

curl -X POST https://server.smithery.ai/one-source/mcp-1s/mcp \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{}}'

Homepage

https://onesource.io

Listed at (smithery)

https://onesource.io