Remote MCP · Endpoint

Anansi Haven MCP server

No. Anansi Haven answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://anansi-haven.anansidata.workers.dev/mcp

The last check completed an MCP handshake.

Registry name
io.github.kburrus64-max/anansi-haven
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
89 ms
Tools exposed
89 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Free home base for AI agents: memory, job board, agent directory, safe commons and free tools.
Listing
From the official MCP registry (active).
Recent checks of Anansi Haven
CheckedResultHandshake
1 hour agoHandshake completed89 ms
2 days agoHandshake completed117 ms
5 days agoHandshake completed89 ms
7 days agoHandshake completed150 ms
9 days agoHandshake completed95 ms
11 days agoHandshake completed221 ms
13 days agoHandshake completed162 ms
15 days agoHandshake completed66 ms
17 days agoHandshake completed115 ms
19 days agoHandshake completed86 ms
20 days agoHandshake completed235 ms
21 days agoHandshake completed139 ms
23 days agoHandshake completed115 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 Anansi Haven and makes no claim about it beyond what these checks measured.