Remote MCP · Endpoint

io.github.ForkastPredict/forkast-mcp-docs MCP server

No. io.github.ForkastPredict/forkast-mcp-docs answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://mcp.forkast.gg/mcp

The last check completed an MCP handshake.

Registry name
io.github.ForkastPredict/forkast-mcp-docs
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
194 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
MCP server for querying Forkast documentation
Listing
From the official MCP registry (active).
Recent checks of io.github.ForkastPredict/forkast-mcp-docs
CheckedResultHandshake
2 hours agoHandshake completed194 ms
2 days agoHandshake completed843 ms
4 days agoHandshake completed217 ms
5 days agoHandshake completed242 ms
7 days agoHandshake completed285 ms
8 days agoHandshake completed596 ms
9 days agoHandshake completed246 ms
12 days agoHandshake completed219 ms
13 days agoHandshake completed210 ms
15 days agoHandshake completed233 ms
17 days agoHandshake completed735 ms
18 days agoHandshake completed716 ms
19 days agoHandshake completed696 ms
20 days agoHandshake completed195 ms
20 days agoHandshake completed722 ms
21 days agoHandshake completed726 ms
22 days agoHandshake completed215 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.

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 io.github.ForkastPredict/forkast-mcp-docs and makes no claim about it beyond what these checks measured.