Remote MCP · Endpoint

walalook tools MCP server

No. walalook tools answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://walalook.me/mcp/tomd

The last check completed an MCP handshake.

Registry name
me.walalook/tools
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
637 ms
Tools exposed
1 tool
Uptime, last 30 days
100% from 13 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
1 hour agoHandshake completed637 ms
9 hours agoHandshake completed602 ms
2 days agoHandshake completed619 ms
4 days agoHandshake completed205 ms
7 days agoHandshake completed198 ms
9 days agoHandshake completed194 ms
11 days agoHandshake completed209 ms
14 days agoHandshake completed219 ms
15 days agoHandshake completed212 ms
18 days agoHandshake completed629 ms
20 days agoHandshake completed612 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 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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

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.