Remote MCP · Endpoint

io.github.sly13/cryptoetf MCP server

No. io.github.sly13/cryptoetf answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mcp.cryptoetf.today/api/mcp

The last check completed an MCP handshake.

Registry name
io.github.sly13/cryptoetf
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
384 ms
Tools exposed
12 tools
Uptime, last 30 days
100% from 18 checks
Described by its publisher as
Live spot crypto ETF flows for 16 assets and their funds, CEFI index and prices.
Listing
From the official MCP registry (active).
Recent checks of io.github.sly13/cryptoetf
CheckedResultHandshake
1 hour agoHandshake completed384 ms
1 day agoHandshake completed341 ms
2 days agoHandshake completed158 ms
3 days agoHandshake completed335 ms
4 days agoHandshake completed206 ms
5 days agoHandshake completed153 ms
6 days agoHandshake completed346 ms
9 days agoHandshake completed339 ms
11 days agoHandshake completed207 ms
14 days agoHandshake completed350 ms
16 days agoHandshake completed215 ms
18 days agoHandshake completed341 ms
20 days agoHandshake completed146 ms
22 days agoHandshake completed320 ms
24 days agoHandshake completed449 ms
26 days agoHandshake completed129 ms
27 days agoHandshake completed431 ms
29 days agoHandshake completed340 ms

The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 29 responding of 29.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with io.github.sly13/cryptoetf and makes no claim about it beyond what these checks measured.