Remote MCP · Endpoint
Metabind Docs MCP server
No. Metabind Docs answered an MCP handshake 2 hours ago.
UpLast checked 2 hours ago
Server URL
https://docs.metabind.ai/mcp
The last check completed an MCP handshake.
- Registry name
- ai.metabind/docs
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 147 ms
- Tools exposed
- 3 tools
- Uptime, last 30 days
- 100% from 15 checks
- Described by its publisher as
- Search and read the Metabind documentation: MCP Apps, BindJS, the SDKs, the CLI, and the APIs.
- Website
- https://docs.metabind.ai/
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 2 hours ago | Handshake completed | 147 ms |
| 2 days ago | Handshake completed | 219 ms |
| 4 days ago | Handshake completed | 173 ms |
| 6 days ago | Handshake completed | 269 ms |
| 8 days ago | Handshake completed | 302 ms |
| 10 days ago | Handshake completed | 340 ms |
| 12 days ago | Handshake completed | 277 ms |
| 13 days ago | Handshake completed | 262 ms |
| 14 days ago | Handshake completed | 122 ms |
| 16 days ago | Handshake completed | 199 ms |
| 18 days ago | Handshake completed | 188 ms |
| 20 days ago | Handshake completed | 239 ms |
| 21 days ago | Handshake completed | 167 ms |
| 23 days ago | Handshake completed | 290 ms |
| 24 days ago | Handshake completed | 275 ms |
The last 15 checks. Full history is kept for 30 days; the all-time counter stands at 15 responding of 15.
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 Metabind Docs and makes no claim about it beyond what these checks measured.