Chain Data for Agents (x402)
REMOTE · CHAIN-DATA-AGENT.WANGZUO305.WORKERS.DEV
Solana validator stats and the SOL stake unlock calendar for agents. Pay per call via x402.
Available components
Last scanned (15 hours ago)
Scores higher than 54% of remote servers
Reachable. Last reached 21 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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 406, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- 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 Usability77
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1835 tokens (~183/item across 10 items; 7 tools + 3 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
- Structured output schemas are declared (86% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 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
Checks we ran (12)
- TLS certificate
- Authorization
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 406, which proves neither a plaintext path nor enforcement.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Nov 26 +1
- Schema quality: 1036 → 1835 ▼ functional
- Tool coverage: 75% → 86% ▲ functional
- New prompt “solana_unlock_outlook” functional
- New resource “solana_unlocks_docs” functional
- Server version: 0.1.0 → 0.2.0 functional
- New tool “solana_unlocks_get_unlock_calendar” functional
- New tool “solana_unlocks_get_unlock_summary” functional
- New tool “solana_unlocks_list_unlocks” functional
- “request_data” reworded the description of “request” cosmetic
- 15 Nov 26 0
- Stability: unverified → 0.03 ▲ functional
- 14 Nov 26 67
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 21 Nov 2026 · Probed https://chain-data-agent.wangzuo305.workers.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=wangzuo305.workers.dev | CN=YE1,O=Let's Encrypt,C=US | 14 Nov 2026 | 12 Feb 2027 | ECDSA 256 | ECDSA-SHA384 | 6da90c20159169dd14a4b13555c517bce6d |
| SANs: *.wangzuo305.workers.dev, wangzuo305.workers.dev | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| 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 chain-data-agent.wangzuo305.workers.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | DS published | 60074 | 8 | Verified |
| workers.dev. | No DS | 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://chain-data-agent.wangzuo305.workers.dev/mcp | Verified | 200 | |
| http (plaintext) | http://chain-data-agent.wangzuo305.workers.dev/mcp | Inconclusive | 406 |
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 →
request_data Request data that is not covered yet ~124
Request data that these tools do not provide yet (another chain, a dataset, a field or a filter), so the maintainers can consider it for a future release. Free. Describe the data and, optionally, the task it is for. Do not include personal information. Requests are stored anonymously and read by the maintainers; the result is only a confirmation.
| Name | Type | Req | Description |
|---|---|---|---|
| request | string | yes | The data you need, e.g. 'unlock schedule for token X' or 'Ethereum validator stats' |
| use_case | string | – | Optional: the task you need it for |
No output schema declared.
No examples provided.
solana_unlocks_get_unlock_calendar Get the SOL unlock schedule by day, week or month for a date range. ~289
Get the SOL unlock schedule by day, week or month for a date range. Dates from and to are YYYY-MM-DD, inclusive (default today and 90 days on, span up to 1,500 days). The group parameter is day (default), week (starting Monday) or month. Each period gives the SOL whose stake lockup ends then, the number of stake accounts, the delegated part (needs about one epoch to deactivate before withdrawal) and the largest single account. Periods with nothing unlocking are left out. Costs $0.002 per call, paid via x402 in USDC on Base; the first 3 paid-tool calls per day are free for MCP clients while a shared daily allowance lasts. Without x402 support, later calls return the payment requirements as an error result. Failed calls are not charged. Source: Solana mainnet-beta (stake account lockups via JSON-RPC), Public on-chain data.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string|number | – | First date, YYYY-MM-DD (default today) (e.g. 2026-12-01) |
| group | string|number | – | day, week or month (default day) (e.g. month) |
| to | string|number | – | Last date, YYYY-MM-DD (default from + 89 days) (e.g. 2027-05-31) |
| Name | Type | Req | Description |
|---|---|---|---|
| attribution | object | yes | Source attribution; keep it when presenting the data |
| data | – | – | Result: a list of applications for search and nearby tools, one record or summary object otherwise |
| meta | object | yes | Paging and query details, e.g. limit, offset, has_more, count |
No examples provided.
solana_unlocks_get_unlock_summary Get how much SOL is still locked in stake account lockups and how much unlocks soon. ~113
Get how much SOL is still locked in stake account lockups and how much unlocks soon. Returns the locked SOL total (and the delegated part), the next unlock day, the SOL unlocking in the next 7, 30, 90 and 365 days, and the last unlock date. Use solana_unlocks_get_unlock_calendar for the schedule. Free, no payment needed. Source: Solana mainnet-beta (stake account lockups via JSON-RPC), Public on-chain data.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| attribution | object | yes | Source attribution; keep it when presenting the data |
| data | – | – | Result: a list of applications for search and nearby tools, one record or summary object otherwise |
| meta | object | yes | Paging and query details, e.g. limit, offset, has_more, count |
No examples provided.
solana_unlocks_list_unlocks List individual SOL stake account unlocks in a date range, largest first within each time. ~370
List individual SOL stake account unlocks in a date range, largest first within each time. Dates from and to are YYYY-MM-DD, inclusive (default today and 30 days on). Filters: min_sol, withdraw_authority (whose SOL it is) and custodian (who can lift the lockup). Each row gives the stake account, SOL, unlock time, withdraw authority, custodian and the vote account it is delegated to (null if not delegated). Returns up to limit rows (default 50, max 200) and the matched count and SOL. Costs $0.002 per call, paid via x402 in USDC on Base; the first 3 paid-tool calls per day are free for MCP clients while a shared daily allowance lasts. Without x402 support, later calls return the payment requirements as an error result. Failed calls are not charged. Source: Solana mainnet-beta (stake account lockups via JSON-RPC), Public on-chain data.
| Name | Type | Req | Description |
|---|---|---|---|
| custodian | string|number | – | Only lockups with this custodian (base58) |
| from | string|number | – | First date, YYYY-MM-DD (default today) (e.g. 2026-12-01) |
| limit | string|number | – | Rows to return, 1 to 200 (default 50) (e.g. 20) |
| min_sol | string|number | – | Only unlocks of at least this many SOL (e.g. 10000) |
| to | string|number | – | Last date, YYYY-MM-DD (default from + 29 days) (e.g. 2026-12-31) |
| withdraw_authority | string|number | – | Only stake accounts with this withdraw authority (base58) |
| Name | Type | Req | Description |
|---|---|---|---|
| attribution | object | yes | Source attribution; keep it when presenting the data |
| data | – | – | Result: a list of applications for search and nearby tools, one record or summary object otherwise |
| meta | object | yes | Paging and query details, e.g. limit, offset, has_more, count |
No examples provided.
solana_validators_get_network_summary Get live Solana network health: epoch progress, validator counts, stake concentration and skip rate. ~142
Get live Solana network health: epoch progress, validator counts, stake concentration and skip rate. Returns the current epoch and its progress, active and delinquent validator counts, total active stake in SOL, the delinquent stake share, the Nakamoto coefficient (fewest validators holding over a third of stake), median commission, cluster block production and skip rate so far this epoch, and median and best vote credits per SOL staked in the last complete epoch. Use it as the baseline when judging a single validator. Free, no payment needed. Source: Solana mainnet-beta (public chain state via JSON-RPC), Public on-chain data.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| attribution | object | yes | Source attribution; keep it when presenting the data |
| data | – | – | Result: a list of applications for search and nearby tools, one record or summary object otherwise |
| meta | object | yes | Paging and query details, e.g. limit, offset, has_more, count |
No examples provided.
solana_validators_get_validator Get live stats for one Solana validator by vote account or identity pubkey. ~285
Get live stats for one Solana validator by vote account or identity pubkey. Pass vote (vote account pubkey) or identity (node identity pubkey). Returns stake in SOL with share and rank, commission, delinquency, how many slots its last vote is behind the cluster, vote credits for each of the last 5 epochs per SOL staked, as a percentage of the cluster median (100 = median; approximate, as it uses today's stake), and current-epoch leader slots, blocks produced and skip rate next to the cluster's. Unknown keys return 404. Costs $0.001 per call, paid via x402 in USDC on Base; the first 3 paid-tool calls per day are free for MCP clients while a shared daily allowance lasts. Without x402 support, later calls return the payment requirements as an error result. Failed calls are not charged. Source: Solana mainnet-beta (public chain state via JSON-RPC), Public on-chain data.
| Name | Type | Req | Description |
|---|---|---|---|
| identity | string|number | – | Validator identity (node) pubkey (base58); use instead of vote |
| vote | string|number | – | Vote account pubkey (base58) (e.g. JDMq8hxZnad2smKLGkFbfg8zVMZHKQcMugD4tMR9u2da) |
| Name | Type | Req | Description |
|---|---|---|---|
| attribution | object | yes | Source attribution; keep it when presenting the data |
| data | – | – | Result: a list of applications for search and nearby tools, one record or summary object otherwise |
| meta | object | yes | Paging and query details, e.g. limit, offset, has_more, count |
No examples provided.
solana_validators_list_validators List Solana validators ranked by stake, vote credits, skip rate or commission, with filters. ~345
List Solana validators ranked by stake, vote credits, skip rate or commission, with filters. For choosing where to stake or comparing validators. sort is stake (default), credits (vote credits per SOL in the last complete epoch, as % of the cluster median), skip_rate (current epoch, lowest first; validators with no leader slots yet come last) or commission (lowest first). Filters: max_commission (percent), min_stake_sol, include_delinquent (default false). Returns up to limit rows (default 20, max 50) and the number matched. Costs $0.002 per call, paid via x402 in USDC on Base; the first 3 paid-tool calls per day are free for MCP clients while a shared daily allowance lasts. Without x402 support, later calls return the payment requirements as an error result. Failed calls are not charged. Source: Solana mainnet-beta (public chain state via JSON-RPC), Public on-chain data.
| Name | Type | Req | Description |
|---|---|---|---|
| include_delinquent | string|number | – | true to include delinquent validators (default false) |
| limit | string|number | – | Rows to return, 1 to 50 (default 20) (e.g. 10) |
| max_commission | string|number | – | Only validators with commission at most this percent (e.g. 5) |
| min_stake_sol | string|number | – | Only validators with at least this much active stake in SOL (e.g. 100000) |
| sort | string|number | – | One of stake, credits, skip_rate, commission (default stake) (e.g. credits) |
| Name | Type | Req | Description |
|---|---|---|---|
| attribution | object | yes | Source attribution; keep it when presenting the data |
| data | – | – | Result: a list of applications for search and nearby tools, one record or summary object otherwise |
| meta | object | yes | Paging and query details, e.g. limit, offset, has_more, count |
No examples provided.
How do I install the Chain Data for Agents (x402) MCP server?
Chain Data for Agents (x402) is a hosted endpoint at https://chain-data-agent.wangzuo305.workers.dev/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 · chain-data-agent.wangzuo305.workers.dev
claude mcp add --transport http zuo305-chain-data-agent 'https://chain-data-agent.wangzuo305.workers.dev/mcp'
What is the Chain Data for Agents (x402) MCP server?
Chain Data for Agents (x402) is an MCP server listed in the public MCP registry as io.github.zuo305/chain-data-agent. Solana validator stats and the SOL stake unlock calendar for agents. Pay per call via x402. This page covers its hosted endpoint (https://chain-data-agent.wangzuo305.workers.dev/mcp).
Is the Chain Data for Agents (x402) MCP server safe to use?
Chain Data for Agents (x402) scores 70 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 Chain Data for Agents (x402) MCP server expose?
Chain Data for Agents (x402) exposes 7 tools: solana_validators_get_network_summary, solana_validators_get_validator, solana_validators_list_validators, solana_unlocks_get_unlock_summary, solana_unlocks_get_unlock_calendar, and 2 more. Their descriptions and schemas cost roughly 1,668 tokens of context every time the server is loaded.
Does the Chain Data for Agents (x402) MCP server require authentication?
No. We connected to Chain Data for Agents (x402) without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Chain Data for Agents (x402) MCP server still maintained?
Chain Data for Agents (x402) is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Chain Data for Agents (x402) MCP server?
VerifyMCP ran 12 checks on Chain Data for Agents (x402), covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Chain Data for Agents (x402): HTTPS. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.