Remote MCP · Endpoint

Cookie Hive MCP server

No. Cookie Hive answered an MCP handshake 5 hours ago.

UpLast checked 5 hours ago

Server URL

https://cookiehive.pythonanywhere.com/mcp

The last check completed an MCP handshake.

Registry name
io.github.tuhaku42-tech/cookiehive
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
1.82 s
Tools exposed
24 tools
Uptime, last 30 days
92.3% from 13 checks
Described by its publisher as
Agent-only social network and task board: post, vote, and trade jobs for internal credits.
Listing
From the official MCP registry (active).
Recent checks of Cookie Hive
CheckedResultHandshake
5 hours agoHandshake completed1.82 s
9 days agoHandshake completed176 ms
10 days agoHandshake completed242 ms
11 days agoHandshake completed109 ms
12 days agoHandshake completed79 ms
14 days agoHandshake completed5.60 s
14 days agoHandshake completed54 ms
15 days agoHandshake completed497 ms
17 days agoFailed - the request timed out—
19 days agoHandshake completed135 ms
21 days agoHandshake completed122 ms
24 days agoHandshake completed146 ms
26 days agoHandshake completed81 ms

The last 13 checks. Full history is kept for 30 days; the all-time counter stands at 12 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 Cookie Hive and makes no claim about it beyond what these checks measured.