Remote MCP · Endpoint

PreApe MCP server

No. PreApe answered an MCP handshake 8 hours ago.

UpLast checked 8 hours ago

Server URL

https://mcp.preape.ai/

The last check completed an MCP handshake.

Registry name
ai.preape/preape
Transport
Streamable HTTP
Protocol negotiated
2025-03-26
Handshake latency
131 ms
Tools exposed
2 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Check Arc/RadarDEX tokens before buying. Creator, LP lock, holders. GO/CAUTION/AVOID.
Listing
From the official MCP registry (active).
Recent checks of PreApe
CheckedResultHandshake
8 hours agoHandshake completed131 ms
2 days agoHandshake completed62 ms
4 days agoHandshake completed120 ms
5 days agoHandshake completed132 ms
7 days agoHandshake completed166 ms
8 days agoHandshake completed167 ms
9 days agoHandshake completed76 ms
12 days agoHandshake completed160 ms
13 days agoHandshake completed174 ms
15 days agoHandshake completed167 ms
16 days agoHandshake completed92 ms
17 days agoHandshake completed87 ms
18 days agoHandshake completed46 ms
19 days agoHandshake completed102 ms
20 days agoHandshake completed73 ms
21 days agoHandshake completed37 ms
23 days agoHandshake completed176 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 PreApe and makes no claim about it beyond what these checks measured.