Remote MCP · Endpoint
RegimeShift MCP server
No. RegimeShift answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://mcp.regimeshift.xyz/mcp
The last check completed an MCP handshake.
- Registry name
- xyz.regimeshift/mcp
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 729 ms
- Tools exposed
- 4 tools
- Uptime, last 30 days
- 100% from 19 checks
- Described by its publisher as
- Paid MCP for AI agents: vol risk premium, Agent-SOFR, max-LTV. $0.001 USDC on Base via x402.
- Website
- https://regimeshift.xyz/
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 729 ms |
| 1 day ago | Handshake completed | 764 ms |
| 2 days ago | Handshake completed | 767 ms |
| 3 days ago | Handshake completed | 1.02 s |
| 4 days ago | Handshake completed | 541 ms |
| 5 days ago | Handshake completed | 567 ms |
| 6 days ago | Handshake completed | 681 ms |
| 8 days ago | Handshake completed | 704 ms |
| 11 days ago | Handshake completed | 820 ms |
| 13 days ago | Handshake completed | 442 ms |
| 15 days ago | Handshake completed | 689 ms |
| 18 days ago | Handshake completed | 746 ms |
| 20 days ago | Handshake completed | 1.23 s |
| 22 days ago | Handshake completed | 781 ms |
| 24 days ago | Handshake completed | 559 ms |
| 26 days ago | Handshake completed | 346 ms |
| 27 days ago | Handshake completed | 677 ms |
| 29 days ago | Handshake completed | 638 ms |
| 29 days ago | Handshake completed | 807 ms |
The last 19 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 RegimeShift and makes no claim about it beyond what these checks measured.