Remote MCP · Endpoint

walalook tools MCP server

No. walalook tools answered an MCP handshake 34 minutes ago.

UpLast checked 34 minutes ago

Server URL

https://walalook.me/mcp/board

The last check completed an MCP handshake.

Registry name
me.walalook/tools
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
221 ms
Tools exposed
0 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
File share + doc tools: Markdown/Excel/Word/PPT. Anonymous tier: no token, 30 calls/day.
Listing
From the official MCP registry (active).
Recent checks of walalook tools
CheckedResultHandshake
34 minutes agoHandshake completed221 ms
9 days agoHandshake completed612 ms
10 days agoHandshake completed607 ms
11 days agoHandshake completed208 ms
12 days agoHandshake completed210 ms
14 days agoHandshake completed202 ms
14 days agoHandshake completed196 ms
15 days agoHandshake completed284 ms
17 days agoHandshake completed206 ms
19 days agoHandshake completed209 ms
21 days agoHandshake completed604 ms
24 days agoHandshake completed603 ms
26 days agoHandshake completed643 ms
28 days agoHandshake completed630 ms

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

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.