Remote MCP · Endpoint
MCPify MCP server
No. MCPify answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://mcp.mcpify.trade/mcp
The last check completed an MCP handshake.
- Registry name
- trade.mcpify/mcpify
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 673 ms
- Tools exposed
- 17 tools
- Uptime, last 30 days
- 100% from 19 checks
- Described by its publisher as
- Non-custodial Hyperliquid perp trading: live markets, account state, user-armed order execution
- Website
- https://mcpify.trade/mcp
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 673 ms |
| 1 day ago | Handshake completed | 215 ms |
| 2 days ago | Handshake completed | 215 ms |
| 3 days ago | Handshake completed | 220 ms |
| 4 days ago | Handshake completed | 213 ms |
| 5 days ago | Handshake completed | 220 ms |
| 6 days ago | Handshake completed | 410 ms |
| 8 days ago | Handshake completed | 233 ms |
| 11 days ago | Handshake completed | 248 ms |
| 13 days ago | Handshake completed | 201 ms |
| 15 days ago | Handshake completed | 312 ms |
| 18 days ago | Handshake completed | 209 ms |
| 20 days ago | Handshake completed | 278 ms |
| 22 days ago | Handshake completed | 210 ms |
| 24 days ago | Handshake completed | 254 ms |
| 26 days ago | Handshake completed | 201 ms |
| 27 days ago | Handshake completed | 216 ms |
| 29 days ago | Handshake completed | 227 ms |
| 29 days ago | Handshake completed | 204 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 MCPify and makes no claim about it beyond what these checks measured.