Remote MCP · Endpoint

Regime MCP server

No. Regime answered an MCP handshake 40 minutes ago.

UpLast checked 40 minutes ago

Server URL

https://feed.regimetoken.xyz/mcp

The last check completed an MCP handshake.

Registry name
xyz.regimetoken/regime
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
980 ms
Tools exposed
12 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Checks crypto trading claims on real data: leverage, drawdown, stop-loss, seasonality, luck.
Listing
From the official MCP registry (active).
Recent checks of Regime
CheckedResultHandshake
40 minutes agoHandshake completed980 ms
3 days agoHandshake completed693 ms
12 days agoHandshake completed198 ms
12 days agoHandshake completed379 ms
14 days agoHandshake completed370 ms
15 days agoHandshake completed416 ms
16 days agoHandshake completed352 ms
17 days agoHandshake completed465 ms
18 days agoHandshake completed369 ms
19 days agoHandshake completed374 ms
22 days agoHandshake completed508 ms
25 days agoHandshake completed466 ms
27 days agoHandshake completed666 ms
29 days agoHandshake completed439 ms

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

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