47620 Solana Data
REMOTE · 47620.XYZ
Pay-per-call Solana data for AI agents over x402: token, account, tx, trending. No signup, no key.
Available components
Last scanned (21 hours ago)
Scores higher than 66% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Crypto and Web3
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 52 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 Usability75
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 4163 tokens (~80/item across 52 items; 52 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage92
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 76% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "should_pay" implies "pay" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 52 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
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 Oct 26 0
- Stability: 0.97 → pass security
- 19 Oct 26 +1
- Tool “wallet_balances_multichain” rewrote its description, which is the text the model reads security
- New tool “wallet_reliability_json” functional
- 17 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Oct 26 0
- A breaking change shipped without a version bump: still 1.1.0 ▼ security
- Tool “dex_spread” was removed ▼ security
- New tool “defi_arbitrage” functional
- New tool “opportunity_feed” functional
- New tool “payment_verify” functional
- 10 Oct 26 0
- Tool coverage: 100% → 79% ▼ functional
- Schema quality: 2867 → 3956 ▼ functional
- Schema quality: excellent → good functional
- New tool “crypto_analytics” functional
- New tool “crypto_prices” functional
- New tool “defi_yields” functional
- New tool “dex_spread” functional
- New tool “gas_multichain” functional
- New tool “nft_holdings” functional
- New tool “payment_evidence” functional
- New tool “portfolio_multichain” functional
- New tool “stablecoin_peg” functional
- New tool “token_research” functional
- New tool “token_risk_evm” functional
- New tool “tx_history” functional
- New tool “tx_receipt” functional
- New tool “wallet_balances_multichain” functional
- New tool “wallet_security” functional
- 7 Oct 26 +2
No change was recorded against any check on this day. Stability & Change Management went from 47 to 57. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
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 4 Nov 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 | 18 Oct 2026 | 16 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 6b228b0e2152c41c03962bb97ba51e760be |
| 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 →
x402_ecosystem_networks ~78
Network and payment-asset histogram of the live x402 ecosystem: which chains (CAIP-2 ids) and which USDC/other assets the indexed pay-per-call services accept, with counts. Sourced live from public indexes. -> /x/x402/networks. Pay-per-call ($0.005 USDC).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
x402_ecosystem_stats ~94
LIVE, sourced snapshot of x402 adoption across the public ecosystem: indexed pay-per-call service count, networks, payment assets, categories and USD price stats (min/median/mean/max), each with its source URL and fetchedAt. Aggregated from 402index.io + Coinbase CDP Bazaar + PayAI Bazaar. -> /x/x402/stats. Pay-per-call ($0.01 USDC).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
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'
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 76 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 52 tools: snapshot, risk_check, should_pay, token_report, health, and 47 more. Their descriptions and schemas cost roughly 4,163 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 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.