Remote MCP · Endpoint

Crypto Regime MCP MCP server

No. Crypto Regime MCP answered an MCP handshake 3 hours ago.

UpLast checked 3 hours ago

Server URL

https://signal-api.shicoars.workers.dev/mcp

The last check completed an MCP handshake.

Registry name
io.github.Shicodiez/crypto-regime-mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
298 ms
Tools exposed
11 tools
Uptime, last 30 days
3 checks from 3 checks
Described by its publisher as
Crypto trend, regime, indicators, stats, scan and perps; 12 tools; credits or x402.
Listing
From the official MCP registry (active).
Recent checks of Crypto Regime MCP
CheckedResultHandshake
3 hours agoHandshake completed298 ms
4 days agoHandshake completed660 ms
7 days agoHandshake completed278 ms

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

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 Crypto Regime MCP and makes no claim about it beyond what these checks measured.