Remote MCP · Endpoint
langchain MCP server
No. langchain answered an MCP handshake 1 hour ago.
Up · key neededLast checked 1 hour ago
Server URL
https://doc2mcp.site/api/mcp/0cd2635e-0cd5-4712-b33c-13b10c547e42/mcp
The handshake completes, but listing its tools needs credentials.
- Registry name
- io.github.doc2mcp/langchain
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 329 ms
- Tools exposed
- Behind credentials
- Uptime, last 30 days
- 100% from 18 checks
- Described by its publisher as
- MCP server for langchain documentation, generated by doc2mcp.
- Repository
- https://github.com/doc2mcp/doc2mcp
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 329 ms |
| 1 day ago | Handshake completed | 431 ms |
| 2 days ago | Handshake completed | 313 ms |
| 3 days ago | Handshake completed | 452 ms |
| 4 days ago | Handshake completed | 320 ms |
| 5 days ago | Handshake completed | 311 ms |
| 6 days ago | Handshake completed | 331 ms |
| 9 days ago | Handshake completed | 329 ms |
| 11 days ago | Handshake completed | 332 ms |
| 14 days ago | Handshake completed | 293 ms |
| 16 days ago | Handshake completed | 257 ms |
| 18 days ago | Handshake completed | 621 ms |
| 20 days ago | Handshake completed | 375 ms |
| 22 days ago | Handshake completed | 311 ms |
| 24 days ago | Handshake completed | 251 ms |
| 26 days ago | Handshake completed | 252 ms |
| 27 days ago | Handshake completed | 256 ms |
| 29 days ago | Handshake completed | 458 ms |
The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 29 responding of 29.
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 langchain and makes no claim about it beyond what these checks measured.