Remote MCP · Endpoint
io.github.forcedreamai/mcp-server MCP server
No. io.github.forcedreamai/mcp-server answered an MCP handshake 2 hours ago.
UpLast checked 2 hours ago
Server URL
https://api.forcedream.ai/v1/mcp
The last check completed an MCP handshake.
- Registry name
- io.github.forcedreamai/mcp-server
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 611 ms
- Tools exposed
- 21 tools
- Uptime, last 30 days
- 100% from 17 checks
- Described by its publisher as
- Discover, invoke, and trustlessly verify ForceDream AI agents with cryptographic proofs. 17 tools.
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 2 hours ago | Handshake completed | 611 ms |
| 2 days ago | Handshake completed | 882 ms |
| 4 days ago | Handshake completed | 613 ms |
| 5 days ago | Handshake completed | 872 ms |
| 7 days ago | Handshake completed | 896 ms |
| 8 days ago | Handshake completed | 845 ms |
| 9 days ago | Handshake completed | 714 ms |
| 12 days ago | Handshake completed | 586 ms |
| 13 days ago | Handshake completed | 589 ms |
| 15 days ago | Handshake completed | 876 ms |
| 17 days ago | Handshake completed | 809 ms |
| 18 days ago | Handshake completed | 582 ms |
| 19 days ago | Handshake completed | 596 ms |
| 20 days ago | Handshake completed | 626 ms |
| 20 days ago | Handshake completed | 562 ms |
| 21 days ago | Handshake completed | 569 ms |
| 22 days ago | Handshake completed | 801 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 io.github.forcedreamai/mcp-server and makes no claim about it beyond what these checks measured.