Remote MCP · Endpoint
RegimeShift MCP server
No. RegimeShift answered an MCP handshake 55 minutes ago.
UpLast checked 55 minutes 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
- 1.23 s
- Tools exposed
- 4 tools
- Uptime, last 30 days
- 100% from 17 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 |
|---|---|---|
| 55 minutes ago | Handshake completed | 1.23 s |
| 2 days ago | Handshake completed | 781 ms |
| 4 days ago | Handshake completed | 559 ms |
| 5 days ago | Handshake completed | 346 ms |
| 7 days ago | Handshake completed | 677 ms |
| 8 days ago | Handshake completed | 638 ms |
| 9 days ago | Handshake completed | 807 ms |
| 12 days ago | Handshake completed | 620 ms |
| 13 days ago | Handshake completed | 694 ms |
| 15 days ago | Handshake completed | 581 ms |
| 17 days ago | Handshake completed | 664 ms |
| 18 days ago | Handshake completed | 458 ms |
| 19 days ago | Handshake completed | 598 ms |
| 20 days ago | Handshake completed | 608 ms |
| 21 days ago | Handshake completed | 548 ms |
| 21 days ago | Handshake completed | 684 ms |
| 23 days ago | Handshake completed | 564 ms |
The last 17 checks. Full history is kept for 30 days; the all-time counter stands at 17 responding of 17.
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.