Remote MCP · Endpoint

Shared Forest MCP server

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

UpLast checked 1 hour ago

Server URL

https://sharedforest.com/mcp

The last check completed an MCP handshake.

Registry name
io.github.ArneFfm/shared-forest
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
215 ms
Tools exposed
13 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Plant or sponsor trees in a shared forest that grows from its traffic. Sponsoring uses OAuth.
Listing
From the official MCP registry (active).
Recent checks of Shared Forest
CheckedResultHandshake
1 hour agoHandshake completed215 ms
8 days agoHandshake completed100 ms
9 days agoHandshake completed65 ms
11 days agoHandshake completed228 ms
12 days agoHandshake completed164 ms
12 days agoHandshake completed304 ms
14 days agoHandshake completed421 ms
14 days agoHandshake completed95 ms
16 days agoHandshake completed393 ms
19 days agoHandshake completed385 ms
21 days agoHandshake completed159 ms
24 days agoHandshake completed221 ms
26 days agoHandshake completed245 ms
28 days agoHandshake completed149 ms

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

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