Remote MCP · Endpoint

Perq MCP server

No. Perq answered an MCP handshake 34 minutes ago.

UpLast checked 34 minutes ago

Server URL

https://perq.sh/mcp

The last check completed an MCP handshake.

Registry name
sh.perq/perq
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
533 ms
Tools exposed
8 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Verified free AI credits, free tiers and startup programs, each with source link and verified date.
Listing
From the official MCP registry (active).
Recent checks of Perq
CheckedResultHandshake
34 minutes agoHandshake completed533 ms
9 days agoHandshake completed313 ms
10 days agoHandshake completed326 ms
11 days agoHandshake completed467 ms
12 days agoHandshake completed535 ms
14 days agoHandshake completed111 ms
14 days agoHandshake completed354 ms
15 days agoHandshake completed371 ms
17 days agoHandshake completed333 ms
19 days agoHandshake completed603 ms
21 days agoHandshake completed398 ms
24 days agoHandshake completed302 ms
26 days agoHandshake completed170 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 Perq and makes no claim about it beyond what these checks measured.