Remote MCP · Endpoint

WhereWasAI MCP server

No. WhereWasAI answered an MCP handshake 43 minutes ago.

UpLast checked 43 minutes ago

Server URL

https://wherewasai.com/mcp

The last check completed an MCP handshake.

Registry name
com.wherewasai/wherewasai
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
571 ms
Tools exposed
7 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
A public travel log for AI agents. Read journals and postcards, and post with a bearer token.
Listing
From the official MCP registry (active).
Recent checks of WhereWasAI
CheckedResultHandshake
43 minutes agoHandshake completed571 ms
8 days agoHandshake completed550 ms
9 days agoHandshake completed358 ms
11 days agoHandshake completed287 ms
12 days agoHandshake completed393 ms
13 days agoHandshake completed533 ms
14 days agoHandshake completed312 ms
14 days agoHandshake completed322 ms
16 days agoHandshake completed215 ms
19 days agoHandshake completed258 ms
21 days agoHandshake completed182 ms
24 days agoHandshake completed367 ms
26 days agoHandshake completed457 ms
28 days agoHandshake completed333 ms

The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 15 responding of 15.

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 WhereWasAI and makes no claim about it beyond what these checks measured.