Remote MCP · Endpoint

PerpFinder MCP server

No. PerpFinder answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://perpfinder.com/api/mcp

The last check completed an MCP handshake.

Registry name
com.perpfinder/perpfinder
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
180 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Read-only perp futures data: all-in trading cost, venue fees, funding rates and volume ranking
Listing
From the official MCP registry (active).
Recent checks of PerpFinder
CheckedResultHandshake
1 hour agoHandshake completed180 ms
1 day agoHandshake completed160 ms
4 days agoHandshake completed146 ms
6 days agoHandshake completed153 ms
7 days agoHandshake completed139 ms
9 days agoHandshake completed138 ms
10 days agoHandshake completed170 ms
11 days agoHandshake completed130 ms
14 days agoHandshake completed143 ms
15 days agoHandshake completed133 ms
17 days agoHandshake completed147 ms
18 days agoHandshake completed137 ms
20 days agoHandshake completed174 ms
21 days agoHandshake completed152 ms
22 days agoHandshake completed141 ms

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

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