Remote MCP · Endpoint

docbin MCP server

No. docbin answered an MCP handshake 11 hours ago.

UpLast checked 11 hours ago

Server URL

https://mcp.docbin.app/mcp

The last check completed an MCP handshake.

Registry name
app.docbin/docbin
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
1.04 s
Tools exposed
3 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Give an agent a place to put large output. Build logs and reports get a stable versioned URL.
Listing
From the official MCP registry (active).
Recent checks of docbin
CheckedResultHandshake
11 hours agoHandshake completed1.04 s
2 days agoHandshake completed760 ms
4 days agoHandshake completed760 ms
6 days agoHandshake completed621 ms
7 days agoHandshake completed434 ms
8 days agoHandshake completed399 ms
9 days agoHandshake completed582 ms
12 days agoHandshake completed441 ms
14 days agoHandshake completed657 ms
15 days agoHandshake completed879 ms
16 days agoHandshake completed413 ms
18 days agoHandshake completed565 ms
19 days agoHandshake completed399 ms
19 days agoHandshake completed45 ms
20 days agoHandshake completed467 ms
21 days agoHandshake completed954 ms
23 days agoHandshake completed580 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 docbin and makes no claim about it beyond what these checks measured.