mcp-registry/io.github.elevasyncsolutions-jpg/cryptodata-api · v3.0.0
Also listed as glama/elevasyncsolutions-jpg/cryptoboss-mcp-server, mcp-registry/io.github.elevasyncsolutions-jpg/cryptoboss-mcp
As of 2026-10-22 02:12 UTC, the Elevasyncsolutions Jpg Cryptodata Api MCP server is up with a Glimind reliability score of 97/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 25.6 hours.
Crypto MCP with 21 tools for market data, DeFi, analytics, and sentiment. Post-paid USDC billing.
Claude Code
claude mcp add --transport http elevasyncsolutions-jpg-cryptodata-api-mc https://cryptodata-api.datachain.workers.dev/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"elevasyncsolutions-jpg-cryptodata-api-mc": {
"type": "http",
"url": "https://cryptodata-api.datachain.workers.dev/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
48 of 48 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
48 tools on one server. Tool-selection accuracy drops as the menu grows, and some clients (e.g. Cursor) cap the number of active tools.
Group tools by task into smaller servers or toolsets, and merge near-duplicates behind one tool with a mode parameter. How to fix →
86 parameter(s) across 43 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →
3 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.
Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →
Negotiates MCP 2025-03-26. Structured output, tool output schemas and elicitation arrived in 2025-06-18.
Upgrade the MCP SDK and negotiate 2025-06-18 or newer. How to fix →
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 43 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.elevasyncsolutions-jpg%2Fcryptodata-api/fixes
{
"name": "analyze_contract",
"description": "Deep contract audit: liquidity, holder risk, bundled supply, honeypot, price manipulation. $0.05.",
"inputSchema": {
"type": "object",
"required": [
"api_key",
"address"
],
"properties": {
"chain": {
"type": "string",
"default": "ethereum"
},
"address": {
"type": "string"
},
"api_key": {
"type": "string"
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "analyze_solana_token",
"description": "Deep Solana token analysis: mint authority, freeze authority, supply, decimals, metadata. $0.05.",
"inputSchema": {
"type": "object",
"required": [
"api_key",
"mint"
],
"properties": {
"mint": {
"type": "string",
"description": "SPL token mint address"
},
"api_key": {
"type": "string"
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "check_agent_balance",
"description": "Check an agent's CryptoBoss API balance. $0.005.",
"inputSchema": {
"type": "object",
"required": [
"api_key"
],
"properties": {
"api_key": {
"type": "string"
}
}
},
"annotations": {
"readOnlyHint": true
}
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.github.elevasyncsolutions-jpg/cryptodata-api"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/io.github.elevasyncsolutions-jpg/cryptodata-api"}) over MCP.
get_jupiter_quote ~214 tokenspay_agent ~114 tokensset_price_alert ~95 tokenscompare_coins ~93 tokensget_price_summary ~93 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fio.github.elevasyncsolutions-jpg%2Fcryptodata-api?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fio.github.elevasyncsolutions-jpg%2Fcryptodata-api?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.elevasyncsolutions-jpg%2Fcryptodata-api.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.elevasyncsolutions-jpg%2Fcryptodata-api.svg :target: https://glimind.com/server/mcp-registry%2Fio.github.elevasyncsolutions-jpg%2Fcryptodata-api?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:681df525171f6df9…, first seen 2026-10-17, included at leaf 4233 of 42,872. Version history · verify what your client received.
Compare: most reliable security servers · most reliable data servers · most reliable finance servers · most reliable other servers · most reliable alerts servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-22 02:12 UTC, the Elevasyncsolutions Jpg Cryptodata Api MCP server is up with a Glimind reliability score of 97/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 25.6 hours.
Elevasyncsolutions Jpg Cryptodata Api MCP server advertises 48 tools, including analyze_contract, analyze_solana_token, check_agent_balance, check_approvals, check_usage.
Point your MCP client at this streamable-http endpoint: https://cryptodata-api.datachain.workers.dev/mcp
Glimind scanned all 48 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.