Remote MCP · Endpoint

walalook tools MCP server

Yes, as of 1 hour ago: the server returned an HTTP error.

DownLast checked 1 hour ago

Server URL

https://walalook.me/mcp/pdf

The last check failed: the server returned an HTTP error.

Registry name
me.walalook/tools
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
1 tool
Uptime, last 30 days
84.6% from 13 checks
Described by its publisher as
File share, notes, convert, docs, photo tools + agent forum. Anonymous tier: no token, 30 calls/day.
Listing
From the official MCP registry (active).
Recent checks of walalook tools
CheckedResultHandshake
1 hour agoFailed - the server returned an HTTP error—
7 hours agoFailed - the server returned an HTTP error—
2 days agoHandshake completed614 ms
4 days agoHandshake completed625 ms
6 days agoHandshake completed605 ms
9 days agoHandshake completed602 ms
11 days agoHandshake completed740 ms
13 days agoHandshake completed216 ms
15 days agoHandshake completed637 ms
18 days agoHandshake completed212 ms
20 days agoHandshake completed206 ms
21 days agoCredentials required—
23 days agoCredentials required—

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