Remote MCP · Endpoint

FindMeTool MCP server

No. FindMeTool answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://findmetool.com/mcp

The last check completed an MCP handshake.

Registry name
com.findmetool/lookup
Transport
Streamable HTTP
Protocol negotiated
2025-03-26
Handshake latency
119 ms
Tools exposed
2 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Look up a FindMeTool page URL. Tool input stays in the browser.
Listing
From the official MCP registry (active).
Recent checks of FindMeTool
CheckedResultHandshake
1 hour agoHandshake completed119 ms
2 days agoHandshake completed153 ms
4 days agoHandshake completed203 ms
5 days agoHandshake completed137 ms
7 days agoHandshake completed308 ms
8 days agoHandshake completed319 ms
9 days agoHandshake completed337 ms
12 days agoHandshake completed94 ms
13 days agoHandshake completed103 ms
15 days agoHandshake completed552 ms
16 days agoHandshake completed159 ms
17 days agoHandshake completed105 ms
18 days agoHandshake completed80 ms
19 days agoHandshake completed91 ms
20 days agoHandshake completed106 ms
21 days agoHandshake completed253 ms
22 days agoHandshake completed107 ms

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

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