Remote MCP · Endpoint

Forager (Unofficial) MCP server

No. Forager (Unofficial) answered an MCP handshake 2 days ago.

UpLast checked 2 days ago

Server URL

https://gateway.pipeworx.io/forager/mcp

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/forager
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
31 ms
Tools exposed
45 tools
Uptime, last 30 days
100% from 12 checks
Described by its publisher as
Unofficial Forager MCP — wraps the Forager person-phone-lookup API (forager.ai)
Listing
From the official MCP registry (active).
Recent checks of Forager (Unofficial)
CheckedResultHandshake
2 days agoHandshake completed31 ms
6 days agoHandshake completed589 ms
16 days agoHandshake completed166 ms
17 days agoHandshake completed97 ms
17 days agoHandshake completed166 ms
19 days agoHandshake completed106 ms
21 days agoHandshake completed111 ms
21 days agoHandshake completed62 ms
22 days agoHandshake completed193 ms
23 days agoHandshake completed117 ms
25 days agoHandshake completed366 ms
28 days agoHandshake completed69 ms

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

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