Remote MCP · Endpoint

Perkadoo MCP server

No. Perkadoo answered an MCP handshake 44 minutes ago.

UpLast checked 44 minutes ago

Server URL

https://mcp.perkadoo.com/mcp

The last check completed an MCP handshake.

Registry name
com.perkadoo/perkadoo
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
314 ms
Tools exposed
25 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Manage Perkadoo giveaways, streak programs and perks, plus verifiable draws and streak badges.
Listing
From the official MCP registry (active).
Recent checks of Perkadoo
CheckedResultHandshake
44 minutes agoHandshake completed314 ms
3 days agoHandshake completed272 ms
12 days agoHandshake completed397 ms
13 days agoHandshake completed293 ms
14 days agoHandshake completed316 ms
15 days agoHandshake completed313 ms
16 days agoHandshake completed459 ms
17 days agoHandshake completed687 ms
18 days agoHandshake completed404 ms
19 days agoHandshake completed594 ms
22 days agoHandshake completed516 ms
25 days agoHandshake completed230 ms
27 days agoHandshake completed499 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 Perkadoo and makes no claim about it beyond what these checks measured.