CryptoQuant MCP server vs Yield.xyz MCP server

CryptoQuant MCP server 40

No x402, MPP or L402 (0). Plan prices and the top-up price, $5 per 100,000 credits, are public without a login, but credits per call vary with rows and data type and no per-call figure is published (10 of 20). Keyless MCP use needs no account and no card, and Basic is free with 10,000 credits a month (20). An MCP client can register itself by dynamic client registration and use keyless, but someone still clicks "Continue with Keyless" on a sign-in page that loads Cloudflare Turnstile; there's no programmatic key API (10 of 20).

Yield.xyz MCP server 100

x402 on its own MCP endpoint for metered tools over quota (40). $0.001 a call published, with machine-readable pricing at /.well-known/x402 (20). 1,000 free read calls a tool a day with no sign-up (20). Keyless use and x402 let an agent start with no person (20). 40 + 20 + 20 + 20 = 100.

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).

Yield.xyz MCP server 95

22 tools read from tools/list with JSON Schema inputs and 14 enums (25). llms.txt (10). Descriptions with order of use, such as yields_get before actions_enter (18 of 20). Typed inputs with enums, ranges and defaults (15). A tool reference with inputs and returns for every tool (12 of 15). Weekly dated product changelog (15). 25 + 10 + 18 + 15 + 12 + 15 = 95.

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).

Yield.xyz MCP server 65

Status page at status.yield.xyz, all services online, with a notice on protocol-level Aave pauses (20). History not read (5). Plan rate limits with headers documented, and the MCP free quotas published with numbers (15). 429 with retry-after and a retry strategy documented; transactions are built unsigned and never broadcast (15). No SLA read (0). Not labelled beta (10). 20 + 5 + 15 + 15 + 0 + 10 = 65.

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).

Yield.xyz MCP server 82

22 tools, about 61 KB (15). limit and offset with documented ranges (20). 429 and the x402 gate documented (15 of 20). All 22 annotated, 18 read-only; transactions unsigned (20). Optional inputs default sensibly; SDKs listed in the docs (12 of 15). 15 + 20 + 15 + 20 + 12 = 82.

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).

Yield.xyz MCP server 60

Weekly changelog entries into November 2026 (30). More than three dated entries in 90 days (20). Docs, a trust page and support; issues not public (10 of 15). Not found in our import of the official registry (0). No package health read (0). 30 + 20 + 10 + 0 + 0 = 60. Registry presence read from Anchor Terminal's own daily import of the official MCP registry (/api/v1/registry.json, 6 November 2026), not the registry's API.

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).

Yield.xyz MCP server 56

Keyless shared access, x402, or your own key in a header; the key can also go in a query string, a documented option (10 of 30, a plain key less 10 for the query string). Mostly reads, and wallet tools build unsigned transactions the user signs elsewhere (18 of 20). Returns protocol data, no third-party prose (10). No audit log of MCP calls (0). SOC 2 Type II, penetration tests by Spearbit/Cantina and Trail of Bits, audited contracts (18 of 20). 10 + 18 + 10 + 0 + 18 = 56.