OneSource MCP
https://mcp.onesource.io/mcp ↗
Description
# @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 ``` #
What our measurements say
OneSource MCP is a remote MCP server published at mcp.onesource.io. It has been probed 6 times since 9/10/2026. It answered in 6 of them (100.0%), a near-uninterrupted record. Median response time is 716 ms, a delay an agent will notice. It exposes a broad tool surface of 44 tools. On the protocol side it still runs 2025-11-25 and has not moved to the newer spec.
Agent readability score
Can an LLM agent pick the right tool here — names, descriptions and parameter clarity are assessed.
Agent readability score
Strengths
- Clear naming convention with '1s_' prefix for tool identification
- Comprehensive coverage of blockchain data queries (ERC20/721, NFTs, transactions, etc.)
Weaknesses
- Some tool descriptions are overly technical without clear use cases
- Parameter documentation lacks explicit required/optional field indicators
- Tool names like '1s_ds_book' are cryptic without context
1s_contract_info_live— Description lacks specific use cases for detected standards1s_erc20_balance_live— Optional fields explanation is incomplete and ambiguous1s_ds_book— Name does not clearly indicate Deepstate order book functionality1s_tx_details_live— No explicit error handling documentation for invalid transaction queries
Verdict
Event narrative
Risk: medium
- 2026-09-10T21:16:35.016Z — era changed from 'auth-gated' to 'legacy' · indicates a shift in operational mode, possibly affecting access controls
- 2026-09-11T05:44:28.819Z — compliance score set to 100 (previously null) · signals full compliance, but 'smokeOk' remains unverified, requiring further checks
Advice
Schema compliance
tools/list structure, inputSchema validity, and a functional smoke test — the components of the 0-100 score.
- tools/list schema valid
- inputSchema is valid JSON Schema
- Smoke test not run this round
- Cold-start: cold 131ms → warm 127ms (penalty 4ms)
Availability history
Event log
Derived by comparing consecutive probes — changes in era, protocol version, build and reachability.
- Server build: — → 5.12.0
- Supported versions: — → 2025-11-25
- Era changed: Auth-gated → Legacy
- Added to watch — era: Auth-gated
Get your badge
Add this badge to your README — it updates automatically as measurements change.
[](https://mcpmetrics.io/servers/one-source-mcp-1s)<a href="https://mcpmetrics.io/servers/one-source-mcp-1s"><img src="https://mcpmetrics.io/badge/one-source/mcp-1s/era.svg" alt="mcpmetrics"></a>You are seeing the last 7 days. Sign up for the full history. Which check failed and why is in the dashboard.
Sign up free to see