Remote MCP · Endpoint

SmartPerps MCP server

No. SmartPerps answered an MCP handshake 19 minutes ago.

UpLast checked 19 minutes ago

Server URL

https://api.youraitools.co/smartperps/mcp

The last check completed an MCP handshake.

Registry name
co.youraitools/smartperps
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
446 ms
Tools exposed
1 tool
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Read-only Hyperliquid smart-money positioning: top-trader bias, flows. Not financial advice.
Listing
From the official MCP registry (active).
Recent checks of SmartPerps
CheckedResultHandshake
19 minutes agoHandshake completed446 ms
3 days agoHandshake completed61 ms
14 days agoHandshake completed107 ms
14 days agoHandshake completed309 ms
15 days agoHandshake completed91 ms
16 days agoHandshake completed169 ms
18 days agoHandshake completed213 ms
18 days agoHandshake completed207 ms
19 days agoHandshake completed318 ms
21 days agoHandshake completed226 ms
22 days agoHandshake completed302 ms
25 days agoHandshake completed249 ms
27 days agoHandshake completed314 ms

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

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