Remote MCP · Endpoint
classifier.dev MCP server
No. classifier.dev answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://classifier.dev/mcp
The last check completed an MCP handshake.
- Registry name
- dev.classifier/classifier
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 143 ms
- Tools exposed
- 5 tools
- Uptime, last 30 days
- 100% from 17 checks
- Described by its publisher as
- Sort up to 1,000 texts into your own labels with a calibrated confidence per answer. No API key.
- Website
- https://classifier.dev/
- Repository
- https://github.com/mrmps/classifier-dev
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 143 ms |
| 2 days ago | Handshake completed | 130 ms |
| 4 days ago | Handshake completed | 108 ms |
| 5 days ago | Handshake completed | 139 ms |
| 7 days ago | Handshake completed | 116 ms |
| 8 days ago | Handshake completed | 413 ms |
| 9 days ago | Handshake completed | 128 ms |
| 12 days ago | Handshake completed | 109 ms |
| 13 days ago | Handshake completed | 147 ms |
| 15 days ago | Handshake completed | 143 ms |
| 16 days ago | Handshake completed | 121 ms |
| 18 days ago | Handshake completed | 157 ms |
| 19 days ago | Handshake completed | 105 ms |
| 20 days ago | Handshake completed | 119 ms |
| 20 days ago | Handshake completed | 121 ms |
| 21 days ago | Handshake completed | 132 ms |
| 22 days ago | Handshake completed | 540 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 and makes no claim about it beyond what these checks measured.