io.github.sly13/cryptoetf
REMOTE · MCP.CRYPTOETF.TODAY · 2 COMPONENTS · SCANNED SEP 20
Live spot crypto ETF flows for 13 assets, CEFI sentiment index and prices.
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 Usability80
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 535 tokens (~107/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 Management73
- Stability observed for 22 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
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 6 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
How do I install the io.github.sly13/cryptoetf MCP server?
io.github.sly13/cryptoetf is a hosted endpoint at https://mcp.cryptoetf.today/api/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 · mcp.cryptoetf.today
claude mcp add --transport http sly13-cryptoetf 'https://mcp.cryptoetf.today/api/mcp'
{
"mcpServers": {
"sly13-cryptoetf": {
"url": "https://mcp.cryptoetf.today/api/mcp"
}
}
} {
"servers": {
"sly13-cryptoetf": {
"type": "http",
"url": "https://mcp.cryptoetf.today/api/mcp"
}
}
} [mcp_servers.sly13-cryptoetf] url = "https://mcp.cryptoetf.today/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"sly13-cryptoetf": {
"type": "remote",
"url": "https://mcp.cryptoetf.today/api/mcp",
"enabled": true
}
}
} openclaw mcp add sly13-cryptoetf --url 'https://mcp.cryptoetf.today/api/mcp' --transport streamable-http
mcp_servers:
sly13-cryptoetf:
url: "https://mcp.cryptoetf.today/api/mcp" {
"McpServers": {
"sly13-cryptoetf": {
"Transport": "http",
"Url": "https://mcp.cryptoetf.today/api/mcp"
}
}
} assistant mcp add sly13-cryptoetf -t streamable-http -u 'https://mcp.cryptoetf.today/api/mcp'
{
"mcpServers": {
"sly13-cryptoetf": {
"type": "http",
"url": "https://mcp.cryptoetf.today/api/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.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 8 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 6 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 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 20 Sept 2026 · Probed https://mcp.cryptoetf.today/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=cryptoetf.today | CN=WE1,O=Google Trust Services,C=US | 23 Jul 2026 | 21 Oct 2026 | ECDSA 256 | ECDSA-SHA256 | 9d5d2052732bc73130db0889ebc0563 |
| SANs: cryptoetf.today, *.cryptoetf.today | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.cryptoetf.today. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| today. | present | 8164 | 8 | Verified |
| cryptoetf.today. | 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://mcp.cryptoetf.today/api/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.cryptoetf.today/api/mcp | HTTPS enforced | 301 | https://mcp.cryptoetf.today/api/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 →
get_asset_flows Crypto ETF Flow History ~91
Get daily net ETF flow history for a single crypto asset over the last 30 days. Returns a time series of net USD millions per day (positive = inflow, negative = outflow).
| Name | Type | Req | Description |
|---|---|---|---|
| asset | string | yes | Asset to fetch: btc, eth, sol, xrp, hyp, doge, link, avax, hbar, ltc, bnb, dot, sui |
No output schema declared.
No examples provided.
get_cefi_index CEFI Sentiment Index ~57
Get the composite CEFI (Crypto ETF Flow Index) sentiment score across all tracked assets. Baseline = 100. Above 100 means net inflow bias (bullish), below 100 means outflow bias (bearish).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_flows_summary Latest Crypto ETF Flows ~177
Get the latest-day net ETF inflow/outflow (USD millions) for every tracked crypto asset: BTC (Bitcoin), ETH (Ethereum), SOL (Solana), XRP, HYP (Hyperliquid), DOGE (Dogecoin), LINK (Chainlink), AVAX (Avalanche), HBAR (Hedera), LTC (Litecoin), BNB, DOT (Polkadot) and SUI. Positive = inflow, negative = outflow. Use this for a quick dashboard snapshot. Flows are published one business day in arrears, so `referenceIsToday` is normally false: the figures belong to `referenceDate` — the last trading day published — and must not be described as today's. On Mondays the freshest data is Friday's. `totalUsdM` is already summed across all assets.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_prices Crypto Spot Prices ~71
Get current spot prices (USD) and 24-hour percentage change for all 13 tracked crypto assets: BTC, ETH, SOL, XRP, HYP, DOGE, LINK, AVAX, HBAR, LTC, BNB, DOT, SUI. Prices are sourced from major exchanges and refreshed frequently.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_weekly_analytics Weekly ETF Flow Analytics ~56
Get 7-day aggregated ETF flow analytics for all tracked assets. Returns total net flow, average daily flow, and count of positive vs negative days per asset. Useful for a quick momentum read without pulling the full time series.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
What is the io.github.sly13/cryptoetf MCP server?
io.github.sly13/cryptoetf is an MCP server listed in the public MCP registry as io.github.sly13/cryptoetf. Live spot crypto ETF flows for 13 assets, CEFI sentiment index and prices. This page covers its hosted endpoint (https://mcp.cryptoetf.today/api/mcp).
Is the io.github.sly13/cryptoetf MCP server safe to use?
io.github.sly13/cryptoetf scores 75 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 io.github.sly13/cryptoetf MCP server expose?
io.github.sly13/cryptoetf exposes 5 tools: get_flows_summary, get_asset_flows, get_cefi_index, get_prices, get_weekly_analytics. Their descriptions and schemas cost roughly 452 tokens of context every time the server is loaded.
Does the io.github.sly13/cryptoetf MCP server require authentication?
No. We connected to io.github.sly13/cryptoetf without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.sly13/cryptoetf MCP server still maintained?
io.github.sly13/cryptoetf 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.