47620 Solana Data
REMOTE · 47620.XYZ · SCANNED SEP 20
Pay-per-call Solana data for AI agents over x402: token, account, tx, trending. No signup, no key.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability78
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 222 tokens (~44/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
How do I install the 47620 Solana Data MCP server?
47620 Solana Data is a hosted endpoint at https://47620.xyz/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · 47620.xyz
claude mcp add --transport http 47620-xyz-solana-data 'https://47620.xyz/mcp'
{
"mcpServers": {
"47620-xyz-solana-data": {
"url": "https://47620.xyz/mcp"
}
}
} {
"servers": {
"47620-xyz-solana-data": {
"type": "http",
"url": "https://47620.xyz/mcp"
}
}
} [mcp_servers.47620-xyz-solana-data] url = "https://47620.xyz/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"47620-xyz-solana-data": {
"type": "remote",
"url": "https://47620.xyz/mcp",
"enabled": true
}
}
} openclaw mcp add 47620-xyz-solana-data --url 'https://47620.xyz/mcp' --transport streamable-http
mcp_servers:
47620-xyz-solana-data:
url: "https://47620.xyz/mcp" {
"McpServers": {
"47620-xyz-solana-data": {
"Transport": "http",
"Url": "https://47620.xyz/mcp"
}
}
} assistant mcp add 47620-xyz-solana-data -t streamable-http -u 'https://47620.xyz/mcp'
{
"mcpServers": {
"47620-xyz-solana-data": {
"type": "http",
"url": "https://47620.xyz/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Sept 26 65
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Probed https://47620.xyz/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=47620.xyz | CN=YE2,O=Let's Encrypt,C=US | 30 Aug 2026 | 28 Nov 2026 | ECDSA 256 | ECDSA-SHA384 | 6cc23e4e4e432d09e874d63ae8aeec1293c |
| SANs: 47620.xyz | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of 47620.xyz. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| xyz. | present | 3599, 18130 | 8, 8 | Verified |
| 47620.xyz. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://47620.xyz/mcp | Verified | 200 | |
| http (plaintext) | http://47620.xyz/mcp | HTTPS enforced | 308 | https://47620.xyz/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
solana_account ~50
Native SOL balance plus every SPL token balance (incl. USDC) for a Solana address. Pay-per-call ($0.002 USDC).
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Solana wallet address |
No output schema declared.
No examples provided.
solana_health ~34
Solana network health: current slot, epoch, and SOL/USD price. Pay-per-call ($0.001 USDC).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
solana_token ~51
Live price, liquidity, 24h volume and DEX pairs for any Solana SPL token mint. Pay-per-call ($0.002 USDC).
| Name | Type | Req | Description |
|---|---|---|---|
| mint | string | yes | SPL token mint address |
No output schema declared.
No examples provided.
solana_trending ~41
Live trending / new Solana DEX pairs by 24h volume. A fresh feed for agents. Pay-per-call ($0.005 USDC).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
solana_tx ~46
Status, slot, fee, block time and transfer summary for a Solana transaction signature. Pay-per-call ($0.003 USDC).
| Name | Type | Req | Description |
|---|---|---|---|
| signature | string | yes | Transaction signature |
No output schema declared.
No examples provided.
What is the 47620 Solana Data MCP server?
47620 Solana Data is an MCP server listed in the public MCP registry as io.github.47620-xyz/solana-data. Pay-per-call Solana data for AI agents over x402: token, account, tx, trending. No signup, no key. This page covers its hosted endpoint (https://47620.xyz/mcp).
Is the 47620 Solana Data MCP server safe to use?
47620 Solana Data scores 65 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the 47620 Solana Data MCP server expose?
47620 Solana Data exposes 5 tools: solana_health, solana_token, solana_account, solana_tx, solana_trending. Their descriptions and schemas cost roughly 222 tokens of context every time the server is loaded.
Does the 47620 Solana Data MCP server require authentication?
No. We connected to 47620 Solana Data without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the 47620 Solana Data MCP server still maintained?
47620 Solana Data is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.