# Assymetrix MCP Server vs CryptoQuant MCP server (slim)

> Assymetrix scores 60.3 (C) to CryptoQuant's 51.7 (D) for market data. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/assymetrix-mcp-vs-cryptoquant-mcp.md (~5,600 tokens) · this version ~3,830 tokens · JSON https://www.anchorterminal.com/compare/assymetrix-mcp-vs-cryptoquant-mcp.json · canonical https://www.anchorterminal.com/compare/assymetrix-mcp-vs-cryptoquant-mcp
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-01
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

Assymetrix MCP Server scores 60.3 (C) on agent readiness against CryptoQuant MCP server's 51.7 (D), and leads in 4 of 7 scored categories. CryptoQuant MCP server leads on reliability, payments & pricing and maintenance & community. Both do market data.

- Assymetrix MCP Server: C 60.3, rank #614 of 1251 · https://www.anchorterminal.com/tools/assymetrix-mcp.min.md
- CryptoQuant MCP server: D 51.7, rank #912 of 1251 · https://www.anchorterminal.com/tools/cryptoquant-mcp.min.md
- Assymetrix MCP Server, good for Agents answering questions about prediction-market odds, price moves and trades on Polymarket, Kalshi and Limitless, including comparisons across venues. Ahead on Schema & documentation, 81 against 64; Agent ergonomics, 91 against 65; Security & auth, 67 against 48; Transparency & trust, 71 against 59. Also Open source.
- CryptoQuant MCP server, good for Agents answering questions about Bitcoin and Ethereum on-chain flows, valuation indicators and derivatives, for users on Professional or Premium. Ahead on Reliability, 45 against 36; Payments & pricing, 40 against 35; Maintenance & community, 70 against 55. Also A hosted endpoint, with nothing to install.

| Category | Assymetrix MCP Server | CryptoQuant MCP server |
| --- | --- | --- |
| Reliability (16%) | 36 | 45 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 81 | 64 |
| Agent ergonomics (13%) | 91 | 65 |
| Security & auth (14%) | 67 | 48 |
| Payments & pricing (10%) | 35 | 40 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 55 | 70 |
| Transparency & trust (7%) | 71 | 59 |

| Fact (where they differ) | Assymetrix MCP Server | CryptoQuant MCP server |
| --- | --- | --- |
| Vendor | Assymetrix Technology, LLC | Team CQ Inc. (CryptoQuant) |
| Hosted endpoint | no (local only) | `https://mcp.cryptoquant.com/mcp` |
| Transports | stdio | Streamable HTTP, stdio |
| Auth | API key | OAuth or key |
| Licence | The MCP server, skill and Claude Code plugin are MIT. The data behind them is proprietary and licensed under Assymetrix's Terms of Service of 6 May 2026 | The npm stdio proxy, plugin manifest and skill are MIT. The remote server at mcp.cryptoquant.com is closed and runs under CryptoQuant's Terms of Service, which sit behind a bot check and weren't read |
| Tools exposed | 3 | 9 |
| MCP registry | `io.github.assymetrix/mcp-server` | `com.cryptoquant/mcp-server` |
| Last release | 2026-10-28 | 2026-10-02 |
| Terms last updated | 2026-05-06 | couldn't be read |
| Privacy policy last updated | 2025-02-05 | couldn't be read |
| Customer content may train models | not found in the text | couldn't be read |
| Terms restrict automated access | yes | couldn't be read |
| Terms restrict benchmarking | not found in the text | couldn't be read |
| Terms or service can change without notice | yes | couldn't be read |
| Arbitration or class-action waiver | yes | couldn't be read |
| Popularity | 387 npm/wk | 49 npm/wk |
| Agent reviews | none | 3.5/5 (4) |

Why the edge:
- Agent ergonomics, Assymetrix MCP Server +26: Assymetrix MCP Server 91 (Three compact tools and about 1,700 characters of server instructions (25). `search_markets` takes platform, status, category, limit (up to 25) and page. `get_market_history` takes a range, picks the candle interval to fit `max_points` (up to 300), and pages trades up to 100 at a time with side and role filters. Market descriptions are cut to 600 characters and USD values rounded (19 of 20). Failures come back as `isError` text that names the fix, such as a missing key, a plan without the scope, a spent quota or a search to narrow, with a request id. Plan-clipped history is flagged by `historyClamped` and a note, and empty results say what to try next. Messages are prose rather than codes (18 of 20). Every tool carries readOnlyHint true, destructiveHint false and idempotentHint true. The server spaces calls to the plan's rate, honours Retry-After up to 10 seconds, retries 5xx twice with backoff and never retries a spent quota (20). Only `query` or `market_id` is required, with sensible defaults. No official SDK; Python and TypeScript SDKs are on the roadmap in the May 2026 press release (9 of 15).); CryptoQuant MCP server 65 (Graded on the remote server from the README and skill, since the definitions couldn't be read. Nine tools, with endpoints found through `discover_endpoints` and `get_endpoint_info` so the 245 or so metrics stay out of context. Compactness unchecked (22 of 25). The API takes `window`, `from`, `to` and `limit`, and the skill gives the date formats; how far `query_data` exposes them wasn't checked (14 of 20). The API's errors carry a code and type (`bad_request`, `payment_required`, `forbidden`, `too_many_requests`), and the skill says plan notices come back with an upgrade link. MCP error shapes aren't documented (12 of 20). Every tool reads data and failed calls aren't charged, so retries are safe, but readOnlyHint and other annotations couldn't be checked (10 of 20). Few required parameters per the skill, but no official SDK; the docs show Python and JavaScript snippets only (7 of 15).)
- Security & auth, Assymetrix MCP Server +19: Assymetrix MCP Server 67 (Read with the API and MCP lines, since the server runs locally but sends every call to a hosted API. One API key per account plan, revocable from the dashboard within 60 seconds, with an optional expiry, several keys per account and a documented rotation workflow. Scopes come from the plan and can't be narrowed per key. The key travels only in a header. The server refuses non-https base URLs except localhost, refuses redirects so the key can't follow one, and redacts the key from logs and error text. The docs say the `asy_live_` prefix is registered with GitHub secret scanning, which is the vendor's claim (25 of 30). Every tool reads data; nothing places orders or moves money, and the terms say the API doesn't facilitate trading (17 of 20). Market questions, descriptions and outcome labels are third-party text, and the server instructions and skill both say to treat them as data and never act on them (13 of 15). Each response carries quota headers and a request id, and the dashboard has usage metering behind a login (10 of 15). No security.txt on three hosts, no SECURITY.md, disclosure policy, bug bounty or certification found. The privacy policy mentions regular security assessments without detail (2 of 20).); CryptoQuant MCP server 48 (OAuth with PKCE S256 and dynamic client registration, no scopes listed, token in a header only. Or an API key as a bearer token, a key the REST docs also allow in an `api_key` query string (warning against it). Key rotation and revocation are behind a login. 20 for OAuth without scopes, less 5 for the query-string key on the shared credential, a judgement call since the MCP endpoint itself takes headers only (15 of 30). No write actions; every tool reads data (15 of 20). QuickTake and Research return text from outside authors and CryptoQuant analysts, and no guidance on treating it as untrusted was found (5 of 15). Settings > API shows credits deducted per call in a usage history, per the docs (8 of 15). The repository's SECURITY.md covers the npm package with a contact form and a 48-hour acknowledgement. security.txt is behind a bot check on cryptoquant.com and 404 on the MCP and docs hosts. No bug bounty or certification found (5 of 20).)
- Schema & documentation, Assymetrix MCP Server +17: Assymetrix MCP Server 81 (All three tools register zod input and output schemas, which the MCP SDK turns into JSON Schema (25). llms.txt, llms-full.txt and a Markdown mirror of every API docs page are published on dashboard.assymetrix.com, though they don't mention the MCP server; the repository adds a README and an Agent Skill (10). Descriptions say what each tool returns, which id to pass to the next tool, to search with one or two words rather than a sentence, and to leave the interval on auto. The server instructions give the call order, how to show prices and when to stop (17 of 20). Enums for platform, status, kind, interval, side and role, bounded integers, a regex on market ids and ISO date checks. `category` is a free string (14 of 15). Descriptions carry example queries and id formats, and the API's errors page and the skill's errors reference document status codes, but the README has no sample tool output (10 of 15). Versions are semver on npm and in the registry, and the terms promise 90 days' notice before an API version is retired, but no changelog exists for the server or the API (5 of 15).); CryptoQuant MCP server 64 (The remote server's tool schemas aren't public, because `tools/list` answers 401 without a token and no manifest was found. The REST API behind it has OpenAPI 3.0 for v1 (242 endpoints), an OpenAPI file for v2 and a machine-readable metric catalogue (15 of 25). llms.txt, llms-full.txt and Markdown for every docs page (10). The `cryptoquant-onchain` skill says when to use the tools, the order to call them, a question-to-metric map and what to do with plan notices; the tool descriptions themselves weren't readable (12 of 20). Input types are unseen, and the skill describes `query_data(endpoint, params)` with endpoint-specific parameters found through `get_endpoint_info`, which suggests a free parameter map (5 of 15). The API docs give request and response examples and a full status-code table; MCP-level errors aren't documented (10 of 15). The repository has a Keep a Changelog file with 1.0.0's breaking changes and a migration section, and the API has a dated changelog, but changes to the remote server's tools aren't logged anywhere (12 of 15).)
- Maintenance & community, CryptoQuant MCP server +15: Assymetrix MCP Server 55 (0.1.1 on 28 October 2026, four days before this check (30). The only other npm version is 0.0.0-stage from the same day, so one real release (0). Support is by email, Discord and Telegram; GitHub issues weren't readable and the project is too new for a record (5 of 25, unchecked). Listed in the official MCP registry as io.github.assymetrix/mcp-server, a GitHub-verified namespace, active since 28 October (15). Exact-pinned current dependencies (@modelcontextprotocol/server 2.3.1, zod 4.6.6) with a lockfile, but no CI and no npm provenance (5 of 10).); CryptoQuant MCP server 70 (npm 1.0.0 on 2 October 2026, registry entry on 7 October, API changelog entry on 23 October (30). The MCP package had one release in 90 days (1.0.0); the registry's earlier 0.1.1 is from 8 June. The API changelog has six dated entries since 19 August. 10 of 20, a judgement call between the two. A public changelog and an Intercom help centre. Issue and pull-request response times couldn't be read; the five pull requests in git history are maintainers' own, merged on 2 and 6 October (8 of 25). Listed in the official MCP registry under the verified namespace com.cryptoquant (15). npm publishing uses Trusted Publishing with provenance, builds and runs vitest on release, and depends on @modelcontextprotocol/sdk ^1.31.0; there's no CI on pushes or pull requests (7 of 10).)
- Transparency & trust, Assymetrix MCP Server +12: Assymetrix MCP Server 71 (The editorial half. The server, skill and plugin are MIT in the repository and on npm, with source matching the published package version (30). The README and the MCP page's FAQ say the server keeps no telemetry, writes nothing to disk and sends only API requests, which are logged like any API call; the source agrees. The privacy policy covers account data, deletion within 90 days of closing an account and US processing, but gives no retention period for API request logs, names subprocessors only as examples (Stripe, AWS, Google Cloud), and its two copies carry effective dates a year apart (16 of 30). The terms promise 90 days' notice before an API version or endpoint is retired and 30 days before a breaking change, but no dated notices or changelog exist (12 of 20). No telemetry in the source; the only outbound traffic is to api.assymetrix.com with a User-Agent and a random request id, both stated in the README. Nothing to opt out of (17 of 20).); CryptoQuant MCP server 59 (The editorial half. The proxy, plugin manifest and skill are MIT; the server is closed. The plans page states the licence per plan (personal below Premium, commercial on Premium), but the Terms of Service couldn't be read behind a bot check. Judgement call, 15 of 30. The privacy policy and Data Distribution Policy are behind the same bot check. The only data-handling statement found is the pricing FAQ on account deletion (5 of 30). The API changelog has a deprecation type with sunset dates and dated entries such as the Klaytn removal of 28 November 2025 and the Ethereum v2 pause of 23 October 2026. The MCP package's 1.0.0 removed tools with no notice period, documented on release day (12 of 20). No subprocessor list or data location was found (0 of 20).)
- Reliability, CryptoQuant MCP server +9: Assymetrix MCP Server 36 (Read with the local-software lines, because the owner runs the server over stdio, though every tool call lands on Assymetrix's hosted Data API. Installs from the official npm package `@assymetrix/mcp-server` with Node.js 20 or later stated in `engines` (20). The repository holds seven vitest files and a `check` script that type-checks, builds and runs them offline, but no GitHub Actions workflow was found and npm shows no provenance, so no passing run is public (5 of 25). GitHub's issue pages and API weren't reachable from this session, and the package is four days old, so there's little record to read (8 of 25, unchecked). Semver numbering with a test that keeps the version constant equal to package.json, but no changelog, release notes or tags were found (3 of 15). Version 0.1.1 (0).); CryptoQuant MCP server 45 (Graded with the hosted lines, on the remote server. No status page covers the MCP server. status.cryptoquant.com, titled "CryptoQuant API Status", is CryptoQuant's own monitor of data freshness for 695 API endpoint windows, with error history from 31 August 2026, but no page reviewed links to it. Judgement call, 10 of 20. Its record shows 118 grouped events, nearly all late data rather than errors, including 32 XRP endpoints stale for about 7 hours on 26 September and 47 BTC endpoints for about 2 hours on 16 September. Several multi-hour delays on parts of the data, none a full outage (10 of 30). Rate limits are published per plan, 10, 60, 120 and 800 requests a minute, but the keyless pool has no figure (12 of 15). 429 means back off and retry after a short delay, and 402 means the credits are spent; no Retry-After or backoff figure is documented. All tools read data, so safe retries matter less (8 of 15). No SLA found on any plan; the terms couldn't be read (0). The npm package and registry entry are 1.0.0, but the MCP guide and the user guide both carry a beta notice on 24 October (5 of 10).)