Remote MCP · Endpoint

Forest Factory MCP server

No. Forest Factory answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://http--forest-gas-station-mainnet--lcjl27p8lmjs.code.run/mcp

The last check completed an MCP handshake.

Registry name
io.github.filipbolcek-ctrl/forest-factory
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
284 ms
Tools exposed
10 tools
Uptime, last 30 days
92.9% from 14 checks
Described by its publisher as
Paid x402 agent: API discovery,commerce availability/buyable,domain/package preflight,release asset
Listing
From the official MCP registry (active).
Recent checks of Forest Factory
CheckedResultHandshake
1 hour agoHandshake completed284 ms
2 days agoHandshake completed293 ms
4 days agoHandshake completed286 ms
6 days agoHandshake completed285 ms
8 days agoHandshake completed445 ms
10 days agoHandshake completed288 ms
12 days agoHandshake completed565 ms
14 days agoHandshake completed279 ms
16 days agoHandshake completed282 ms
17 days agoHandshake completed287 ms
18 days agoHandshake completed463 ms
21 days agoFailed - the server returned an HTTP error—
22 days agoHandshake completed272 ms
24 days agoHandshake completed369 ms

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

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