classifier.dev docs
listed under this name in a public catalogue; the server gives only its address, classifier.dev
Registry code: 451095344e3cbd3f
classifier.dev sorts text into labels you name, many texts per call, with a calibrated confidence on every answer. Use classify_texts for one label per text, classify_multi_label when several can apply, count_labels for a histogram over a corpus, and review_uncertain to pull out only the answers worth a human (or your own) look. Reach for it when reading the inputs is the expensive part: forty search results, a thousand log lines, a backlog of tickets. Under about five items you can already see, just decide yourself. Labels are free text; descriptive names classify better. No key is needed.…
- endpoint
- https://classifier.dev/mcp
- door code
- 8ef02a441f386fdb
- protocol
- streamable-http ·2025-06-18
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is classifier.dev docs live?
- Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
- Is classifier.dev docs free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does classifier.dev docs have?
- 5 tools: classify_texts, count_labels, review_uncertain, classify_dimensions, classify_multi_label.
- Is classifier.dev docs safe to connect?
- The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
90 days 99.4%· all time 99.3%
last good check
of 5 tools
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- live → degraded· timeout after 20000ms
- down → live
- used for
- classify texts into custom labels
- apply multiple labels to texts
- count label distribution over a corpus
- find uncertain classifications for review
- takes → gives
- text → data
- tools
- 5 reads
Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.
through this hub
successful
what callers paid
Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run
Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.
classify_texts reads unknown 31d ago
Sort up to 1,000 texts into exactly one of your own labels each, with confidence per answer. Use this when you have many items to triage, route, filter or bucket and do not want to read them all: search results before opening them, tickets, log lines, changed files, feedback. Do not use it for fewer than about five items you can already see — just decide. For default Jev, confidence is calibrated (answers >= 0.9 are right ~82-92% of the time; < 0.5 about 30-60%); these measurements do not apply to experimental Laya. so act on the sure ones and look at the rest yourself, or pass tier "smart" to have the unsure ones re-asked of a reasoning model.
{ "type": "object", "oneOf": [ { "not": { "required": [ "url" ] }, "required": [ "inputs" ] }, { "not": { "required": [ "inputs" ] }, "required": [ "url" ] } ], "required": [ "labels" ], "properties": { "url": { "type": "string", "pattern": "^https?://", "maxLength": 8192, "description": "Scrape one public URL instead of inputs/items. Requires funded workspace access. Context.dev costs $0.0022 per billed attempt plus classification; long articles need Fast. Errors disclose retained charges. No automatic scrape retries." }, "tier": { "enum": [ "fast", "smart" ], "type": "string", "description": "fast (default) or smart, which re-asks answers under 0.7 confidence of a reasoning model (slower, single-label only). Independent of the Laya processing lane." }, "model": { "enum": [ "jev", "laya", "kev", "chunklaya" ], "type": "string", "description": "Jev is default. Default/explicit jev inputs over 32,000 characters use paid Fast-only long context: up to 250,000 original cl100k_base context tokens total, 20 documents, 32 decisions and a 1 MB body. Requires paid workspace balance or active paid subscription, not signup credit. $0.084/M original context tokens counted once across inputs, independent of dimensions. Final Jev uses selected evidence; eligible chunks may be omitted, disclosed in usage.long_context. No evidence returns 422 long_context_no_evidence without charge. Explicit 'chunklaya' retains legacy opt-in (4,000,000 characters/input, 20 inputs, subject to body limit). 'laya' (512-token context) and 'kev' (8K context) remain experimental alternatives." }, "inputs": { "type": "array", "items": { "type": "string" }, "maxItems": 1000, "minItems": 1, "description": "1 to 1,000 texts to classify. Results come back in the same order." }, "labels": { "type": "array", "items": { "type": "string" }, "maxItems": 100, "minItems": 2, "description": "2 to 100 category names. Descriptive names classify better: \"urgent bug\" beats \"p0\". Add a label like \"none of these\" when none-of-the-above is a real outcome." }, "include": { "type": "array", "items": { "enum": [ "markdown", "html" ], "type": "string" }, "description": "With url: return article.markdown and/or article.html at no extra scrape cost. Omit for compact output." }, "processing": { "enum": [ "fast", "bulk" ], "type": "string", "description": "Optional. Implies Laya if model is omitted; has no effect with explicit Jev. With Laya, omit to select fast for one decision or bulk for batches automatically. Explicit fast accepts one decision. Shared capacity limits can return 429." }, "share_data": { "type": "boolean", "default": true, "description": "Synchronous classification request text, labels, instructions and model results are retained for model training and operator review in private Cloudflare storage by default. Shared requests receive double per-minute and daily classification quotas. Set share_data: false or X-Classifier-Share-Data: false to opt out and use standard limits. Share only data you have permission to contribute; do not include confidential or personal information. Redaction is best effort. Billing, spending caps and input-size limits still apply." }, "instructions": { "type": "string", "description": "Optional extra criteria, e.g. \"judge only the service, ignore the food\"." } }, "additionalProperties": false }arguments 101 linescount_labels reads unknown 33d ago
Classify up to 1,000 texts and return only a histogram: how many landed on each label, and how many the model was unsure about. Use this when you want the shape of a corpus — what share of feedback is bugs vs praise, how many search results are relevant — without pulling a thousand individual answers into context. Use classify_texts when you need the answer per item.
{ "type": "object", "required": [ "inputs", "labels" ], "properties": { "inputs": { "type": "array", "items": { "type": "string" }, "maxItems": 1000, "minItems": 1, "description": "1 to 1,000 texts to classify. Results come back in the same order." }, "labels": { "type": "array", "items": { "type": "string" }, "maxItems": 100, "minItems": 2, "description": "2 to 100 category names. Descriptive names classify better: \"urgent bug\" beats \"p0\". Add a label like \"none of these\" when none-of-the-above is a real outcome." }, "share_data": { "type": "boolean", "default": true, "description": "Synchronous classification request text, labels, instructions and model results are retained for model training and operator review in private Cloudflare storage by default. Shared requests receive double per-minute and daily classification quotas. Set share_data: false or X-Classifier-Share-Data: false to opt out and use standard limits. Share only data you have permission to contribute; do not include confidential or personal information. Redaction is best effort. Billing, spending caps and input-size limits still apply." }, "instructions": { "type": "string", "description": "Optional extra criteria, e.g. \"judge only the service, ignore the food\"." }, "unsure_below": { "type": "number", "default": 0.7, "maximum": 1, "minimum": 0, "description": "Answers with confidence under this count as unsure." } }, "additionalProperties": false }arguments 44 linesreview_uncertain reads unknown 33d ago
Classify up to 1,000 texts and return only the ones whose confidence fell under a threshold (default 0.7), each with its two most likely labels. Use this after a bulk classification to decide which items deserve your own attention: the confident answers can be trusted, these are the ones to read. Returns the index of each item so you can map back to your list.
{ "type": "object", "required": [ "inputs", "labels" ], "properties": { "below": { "type": "number", "default": 0.7, "maximum": 1, "minimum": 0, "description": "Return items with confidence under this." }, "inputs": { "type": "array", "items": { "type": "string" }, "maxItems": 1000, "minItems": 1, "description": "1 to 1,000 texts to classify. Results come back in the same order." }, "labels": { "type": "array", "items": { "type": "string" }, "maxItems": 100, "minItems": 2, "description": "2 to 100 category names. Descriptive names classify better: \"urgent bug\" beats \"p0\". Add a label like \"none of these\" when none-of-the-above is a real outcome." }, "share_data": { "type": "boolean", "default": true, "description": "Synchronous classification request text, labels, instructions and model results are retained for model training and operator review in private Cloudflare storage by default. Shared requests receive double per-minute and daily classification quotas. Set share_data: false or X-Classifier-Share-Data: false to opt out and use standard limits. Share only data you have permission to contribute; do not include confidential or personal information. Redaction is best effort. Billing, spending caps and input-size limits still apply." }, "instructions": { "type": "string", "description": "Optional extra criteria, e.g. \"judge only the service, ignore the food\"." } }, "additionalProperties": false }arguments 44 linesclassify_dimensions reads unknown 31d ago
Classify each text by several named dimensions, such as team, urgency and kind, in one request. Returns a label, confidence, scores and model for each field. At most 1,000 item × dimension decisions; every field counts toward the quota. Use per-dimension instructions to define ambiguous categories.
{ "type": "object", "oneOf": [ { "not": { "required": [ "url" ] }, "required": [ "items" ] }, { "not": { "required": [ "items" ] }, "required": [ "url" ] } ], "required": [ "dimensions" ], "properties": { "url": { "type": "string", "pattern": "^https?://", "maxLength": 8192, "description": "Scrape one public URL instead of inputs/items. Requires funded workspace access. Context.dev costs $0.0022 per billed attempt plus classification; long articles need Fast. Errors disclose retained charges. No automatic scrape retries." }, "tier": { "enum": [ "fast", "smart" ], "type": "string", "description": "fast (default) or smart, which re-asks answers under 0.7 confidence of a reasoning model (slower, single-label only). Independent of the Laya processing lane." }, "items": { "type": "array", "items": { "type": "string" }, "maxItems": 1000, "minItems": 1, "description": "1 to 1,000 texts to classify. Results come back in the same order." }, "model": { "enum": [ "jev", "laya", "kev", "chunklaya" ], "type": "string" }, "include": { "type": "array", "items": { "enum": [ "markdown", "html" ], "type": "string" }, "description": "With url: return article.markdown and/or article.html at no extra scrape cost. Omit for compact output." }, "dimensions": { "type": "object", "description": "Named dimensions. Each is a label array or {labels, instructions}. At most 1,000 item × dimension decisions; definitions at most 16,000 characters combined.", "maxProperties": 20, "minProperties": 1, "propertyNames": { "pattern": "\\S", "maxLength": 64, "minLength": 1 }, "additionalProperties": { "oneOf": [ { "type": "array", "items": { "type": "string", "pattern": "\\S", "maxLength": 200, "minLength": 1 }, "maxItems": 100, "minItems": 2, "uniqueItems": true }, { "type": "object", "required": [ "labels" ], "properties": { "labels": { "type": "array", "items": { "type": "string", "pattern": "\\S", "maxLength": 200, "minLength": 1 }, "maxItems": 100, "minItems": 2, "uniqueItems": true }, "instructions": { "type": "string", "maxLength": 4000 } }, "additionalProperties": false } ] } }, "processing": { "enum": [ "fast", "bulk" ], "type": "string", "description": "Optional. Implies Laya if model is omitted; has no effect with explicit Jev. Omit for automatic fast/bulk selection based on item × dimension decisions." }, "share_data": { "type": "boolean", "default": true, "description": "Synchronous classification request text, labels, instructions and model results are retained for model training and operator review in private Cloudflare storage by default. Shared requests receive double per-minute and daily classification quotas. Set share_data: false or X-Classifier-Share-Data: false to opt out and use standard limits. Share only data you have permission to contribute; do not include confidential or personal information. Redaction is best effort. Billing, spending caps and input-size limits still apply." }, "instructions": { "type": "string", "maxLength": 4000, "description": "Optional extra criteria, e.g. \"judge only the service, ignore the food\"." } }, "additionalProperties": false }arguments 144 linesclassify_multi_label reads unknown 31d ago
Like classify_texts, but each text gets every label that applies (possibly none), with an independent 0-1 score per label. Use this for tagging — topics of an article, components touched by a ticket — where one answer is not enough. Set max_labels to cap how many come back per text. Labels scoring >= 0.7 are kept.
{ "type": "object", "oneOf": [ { "not": { "required": [ "url" ] }, "required": [ "inputs" ] }, { "not": { "required": [ "inputs" ] }, "required": [ "url" ] } ], "required": [ "labels" ], "properties": { "url": { "type": "string", "pattern": "^https?://", "maxLength": 8192, "description": "Scrape one public URL instead of inputs/items. Requires funded workspace access. Context.dev costs $0.0022 per billed attempt plus classification; long articles need Fast. Errors disclose retained charges. No automatic scrape retries." }, "model": { "enum": [ "jev", "laya", "kev", "chunklaya" ], "type": "string" }, "inputs": { "type": "array", "items": { "type": "string" }, "maxItems": 1000, "minItems": 1, "description": "1 to 1,000 texts to classify. Results come back in the same order." }, "labels": { "type": "array", "items": { "type": "string" }, "maxItems": 100, "minItems": 2, "description": "2 to 100 category names. Descriptive names classify better: \"urgent bug\" beats \"p0\". Add a label like \"none of these\" when none-of-the-above is a real outcome." }, "include": { "type": "array", "items": { "enum": [ "markdown", "html" ], "type": "string" }, "description": "With url: return article.markdown and/or article.html at no extra scrape cost. Omit for compact output." }, "max_labels": { "type": "integer", "maximum": 100, "minimum": 1, "description": "At most this many labels per text, most likely first." }, "processing": { "enum": [ "fast", "bulk" ], "type": "string", "description": "Optional. Implies Laya if model is omitted; has no effect with explicit Jev. Omit to select fast for up to four labels on one text, or bulk for larger work automatically." }, "share_data": { "type": "boolean", "default": true, "description": "Synchronous classification request text, labels, instructions and model results are retained for model training and operator review in private Cloudflare storage by default. Shared requests receive double per-minute and daily classification quotas. Set share_data: false or X-Classifier-Share-Data: false to opt out and use standard limits. Share only data you have permission to contribute; do not include confidential or personal information. Redaction is best effort. Billing, spending caps and input-size limits still apply." }, "instructions": { "type": "string", "description": "Optional extra criteria, e.g. \"judge only the service, ignore the food\"." } }, "additionalProperties": false }arguments 98 lines
This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.
Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your MCP server's instructions — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's id451095344e3cbd3f.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/451095344e3cbd3f/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/451095344e3cbd3f?ref=badge)
The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.
An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.