classifier.dev docs MCP Server

by classifier Your server? Claim it

answering

classifier.dev docs is answering right now. Last checked 11 min ago. It exposes 4 tools. Last commit 19 Oct 2026.

classifier.dev documentation as tools: list, read and search the reference, benchmark and guides.

Uptime history 50 days of history · worst day 95%

50 days agonow

100.0%

Uptime 24h

91 of 91 checks

Tools

read from the server

354 ms

Response time

average over 24h

436

Stars

last commit 19 Oct 2026

What the code does

We read the source, 7 d ago · tools taken from the live server · rules 995398eba69f

Capabilities

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

A line of code looks encrypted src/brand.ts:21

  "iVBORw0KGgoAAAANSUhEUgAABLAAAAJ2CAIAAADAIuwLAAAQAElEQVR4nOzdBXxb1/338SMysx07sR1DDGFmatKUmzIzLCvT1m7rtu5Zx/uv3daVmZkxbRpmapjjsO04ZmbRc2SnrmOUbd0ruJ/361aVr5Q2V5Z07/f8Dhg//LddAAAAAIBz/IOFwSDgG/QCAAAAAJxmNQv4DAIhAAAAgB6wmIWdXoa+gkAIAAAAoCfswmYR8A0EQgAAAAA9Y6bXqK8gEAIAAADoGVkhtFoFf…

Runs an external command cli/release.js:10

const sh = (cmd) => execSync(cmd, { stdio: "inherit" });

Runs an external command inference/jevomni/podtest.py:34, inference/jevomni/server.py:190, inference/jevomni/smoke.py:41

        subprocess.run(["ffmpeg", "-y", "-v", "error", "-f", "lavfi",

Reads files and sends them to the network skills/submit.mjs:8

import { readdirSync, readFileSync, statSync } from "node:fs";

Long encoded blob in source src/brand.ts:21

  "iVBORw0KGgoAAAANSUhEUgAABLAAAAJ2CAIAAADAIuwLAAAQAElEQVR4nOzdBXxb1/338SMysx07sR1DDGFmatKUmzIzLCvT1m7rtu5Zx/uv3daVmZkxbRpmapjjsO04ZmbRc2SnrmOUbd0ruJ/361aVr5Q2V5Z07/f8Dhg//LddAAAAAIBz/IOFwSDgG/QCAAAAAJxmNQv4DAIhAAAAgB6wmIWdXoa+gkAIAAAAoCfswmYR8A0EQgAAAAA9Y6bXqK8gEAIAAADoGVkhtFoFf…

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

This code can reach further than it looks

We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 11 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add docs --transport http https://classifier.dev/mcp/docs

Settings → Connectors → Add custom connector, then paste this address

https://classifier.dev/mcp/docs

~/.codex/config.toml

[mcp_servers.docs]
url = "https://classifier.dev/mcp/docs"

.cursor/mcp.json

{
  "mcpServers": {
    "docs": {
      "url": "https://classifier.dev/mcp/docs"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "docs": {
      "type": "http",
      "url": "https://classifier.dev/mcp/docs"
    }
  }
}

Available tools 4

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

docs

list_docs

List every classifier.dev document available over this server — the API reference, the benchmark, the agent skill, the CLI, pricing, privacy, terms and the MCP setup guide — with an id, a title, its section headings and its size. Call this first, then read_doc for the one you need.

search_docs

Full-text search across every classifier.dev document. Returns the paragraphs that contain all of your query's words, with the document and section each came from. Use it for a specific question — rate limits, how confidence is calibrated, how to connect from Claude or ChatGPT — instead of reading whole documents.

doc

read_doc

Return one document in full, or just one of its sections. ids: api, developers, mcp-setup, benchmark, skill, llms, pricing, auth, agents, privacy, terms, about, contact. Use section to fetch a single heading (case-insensitive prefix match) when the whole document is more than you need.

examples

get_examples

Return a copy-pasteable example of calling classifier.dev from a given client: curl, javascript (fetch), python (requests), the classify CLI, or an MCP tools/call payload. Use this when you are about to write integration code and want the exact request shape rather than reading the whole reference.

Endpoints

URL	Transport	State	Latency	Checked
https://classifier.dev/mcp/docs	streamable-http	answering	338 ms	11 min ago

Alternatives to classifier.dev docs

same job, measured the same way

Druxt docs

by druxtjs

Search and read the Druxt documentation and API reference.

3 tools answering

Claude Platform Docs

by claude-platform

Search and read the Claude Platform documentation and API reference.

4 tools answering

Celo Docs

by celo

Search and read the Celo developer documentation

3 tools answering

Tailor

by tailor

Tailor Platform for AI assistants: search, list and read the platform documentation.

3 tools answering

AI Developer Toolkit documentation

by mjaskolski

Search and read guides on Claude Code, Codex and Cursor, in English and Polish.

2 tools answering

Lithuanian Data Portal documentation

by gov-dataportal-guides

Search and read the Lithuanian Data Portal user guide and Data API docs, in Lithuanian and English

3 tools answering

Lium Docs

by datura-ai

Search and read the Lium GPU rental docs: pods, CLI, SDK, REST API and agent guides.

11 tools answering

Mammoth Docs

by mammoth

Search and read the Mammoth Analytics docs. Tools: search_docs, get_doc, list_docs.

3 tools answering

classifier.dev docs — questions

Answers built from our own checks of this server.

What can classifier.dev docs do?

It exposes 4 tools, read directly from the server on our last check. Among them: get_examples, list_docs, read_doc, search_docs. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is classifier.dev docs working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 354 ms. The bar chart above shows every period we have measured.

How do I connect classifier.dev docs?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does classifier.dev docs need an API key?

No. classifier.dev docs completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 4 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is classifier.dev docs?

It answers our handshake in 354 ms on average, which is faster than 39% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.

Is classifier.dev docs open source?

The code is open source: it is published under the MIT licence, written in TypeScript, 436 stars on GitHub and 2 open issues. The licence covers the code in the repository, not the hosted service at classifier.dev, which runs on its operator's own terms.