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
166 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 18 checks
Described by its publisher as
classifier.dev documentation as tools: list, read and search the reference, benchmark and guides.
Listing
From the official MCP registry (active).
Recent checks of classifier.dev docs
CheckedResultHandshake
1 hour agoHandshake completed166 ms
1 day agoHandshake completed639 ms
2 days agoHandshake completed246 ms
3 days agoHandshake completed170 ms
4 days agoHandshake completed187 ms
5 days agoHandshake completed281 ms
6 days agoHandshake completed156 ms
9 days agoHandshake completed215 ms
11 days agoHandshake completed177 ms
14 days agoHandshake completed138 ms
16 days agoHandshake completed187 ms
18 days agoHandshake completed253 ms
20 days agoHandshake completed171 ms
22 days agoHandshake completed154 ms
24 days agoHandshake completed127 ms
26 days agoHandshake completed136 ms
27 days agoHandshake completed222 ms
28 days agoHandshake completed460 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 classifier.dev docs and makes no claim about it beyond what these checks measured.