mcp-registry/xyz.47620/solana-data · v1.1.0
As of 2026-10-19 12:14 UTC, the 47620 Solana Data MCP server is up with a Glimind reliability score of 81/100 (grade B). Over the last 30 days it answered 99.7% of Glimind's liveness checks. It had 5 outages in 90 days, with a median recovery of 7 minutes.
Pay-per-call Solana data over x402 for AI agents: balances, tokens, txs, risk and MCP trust checks.
Claude Code
claude mcp add --transport http 47620-solana-data-mcp-server https://47620.xyz/mcp/solana
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"47620-solana-data-mcp-server": {
"type": "http",
"url": "https://47620.xyz/mcp/solana"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
52 of 52 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 →
52 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 →
16 parameter(s) across 16 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 →
4 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 →
Handshake + tools/list takes ~2,269 ms.
Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.
In the last 30 days: 1 tool(s) removed and 16 schema change(s).
Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts. 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. 16 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fxyz.47620%2Fsolana-data/fixes
{
"name": "crypto_orderbook",
"description": "Order-book top-of-book for a crypto coin: best bid/ask, mid price, spread (abs + bps), bid/ask depth and book imbalance (>0 = more bids). -> /x/crypto/orderbook/:symbol. Pay-per-call ($0.005 USDC).",
"inputSchema": {
"type": "object",
"required": [
"symbol"
],
"properties": {
"limit": {
"type": "integer",
"description": "Order-book levels (5-100, default 20)"
},
"symbol": {
"type": "string",
"description": "Coin ticker or name, e.g. btc, eth, sol"
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
}
}{
"name": "health",
"description": "Network health for a chosen chain. Paths: solana -> /x/solana/health, base -> /x/base-fac/health, polygon -> /x/polygon-fac/health. Pay-per-call from $0.001 USDC.",
"inputSchema": {
"type": "object",
"required": [
"chain"
],
"properties": {
"chain": {
"enum": [
"solana",
"base",
"polygon"
],
"type": "string",
"description": "Chain to query"
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "payment_evidence",
"description": "payment evidence (multichain) — Given a transaction hash (EVM 0x 64-hex or Solana base58 signature), returns on-chain payment evidence: status, confirmations, sender, receiver, val From $0.010 USDC.",
"inputSchema": {
"type": "object",
"required": [
"hash"
],
"properties": {
"hash": {
"type": "string"
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
}
}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/xyz.47620/solana-data"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/xyz.47620/solana-data"}) over MCP.
crypto_analytics ~191 tokenscrypto_ohlcv ~176 tokensrisk_check ~165 tokensunit_convert ~162 tokenstoken_report ~160 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%2Fxyz.47620%2Fsolana-data?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fxyz.47620%2Fsolana-data?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fxyz.47620%2Fsolana-data.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fxyz.47620%2Fsolana-data.svg :target: https://glimind.com/server/mcp-registry%2Fxyz.47620%2Fsolana-data?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:87149f37a8df5dd2…, first seen 2026-10-18, included at leaf 21802 of 26,615. Version history · verify what your client received.
Compare: most reliable data servers · most reliable finance servers · most reliable security servers · most reliable knowledge servers · most reliable other 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-19 12:14 UTC, the 47620 Solana Data MCP server is up with a Glimind reliability score of 81/100 (grade B). Over the last 30 days it answered 99.7% of Glimind's liveness checks. It had 5 outages in 90 days, with a median recovery of 7 minutes.
47620 Solana Data MCP server advertises 52 tools, including account, balance, contract, crypto_analytics, crypto_deep.
Point your MCP client at this streamable-http endpoint: https://47620.xyz/mcp/solana
Glimind scanned all 52 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.