Remote MCP · Endpoint
classifier.dev docs MCP server
No. classifier.dev docs answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://classifier.dev/mcp/docs
The last check completed an MCP handshake.
- Registry name
- dev.classifier/docs
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 171 ms
- Tools exposed
- 4 tools
- Uptime, last 30 days
- 100% from 17 checks
- Described by its publisher as
- classifier.dev documentation as tools: list, read and search the reference, benchmark and guides.
- Repository
- https://github.com/mrmps/classifier-dev
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 171 ms |
| 2 days ago | Handshake completed | 154 ms |
| 4 days ago | Handshake completed | 127 ms |
| 5 days ago | Handshake completed | 136 ms |
| 7 days ago | Handshake completed | 222 ms |
| 8 days ago | Handshake completed | 460 ms |
| 9 days ago | Handshake completed | 121 ms |
| 12 days ago | Handshake completed | 118 ms |
| 13 days ago | Handshake completed | 149 ms |
| 15 days ago | Handshake completed | 169 ms |
| 16 days ago | Handshake completed | 505 ms |
| 18 days ago | Handshake completed | 113 ms |
| 19 days ago | Handshake completed | 143 ms |
| 20 days ago | Handshake completed | 107 ms |
| 20 days ago | Handshake completed | 106 ms |
| 21 days ago | Handshake completed | 155 ms |
| 22 days ago | Handshake completed | 440 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 classifier.dev docs and makes no claim about it beyond what these checks measured.