Skip to content

classifier.dev MCP server

dev.classifier/classifierclassifier.devstreamable-httpv1.0.0Scanned

Sort up to 1,000 texts into your own labels with a calibrated confidence per answer. No API key.

5 tools: 5 change things.

Tools: 0 delete, 0 irreversible, 5 write, 0 read.
  • Reads private data · 0
  • Reads text others write · 5
  • Can send data out · 3
  • 1 finding

Tools listed without sign-in. Remote posture

Anlyon alternative

5 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

What the classifier.dev MCP server can do

The classifier.dev MCP server is published by classifier.dev, a domain the MCP Registry verified. It has 5 tools. It can create or change data (5 tools: classify_texts, classify_dimensions, classify_multi_label, count_labels and 1 more), but cannot delete data. None of its tools only reads.

5 tools bring in text other people can write (classify_texts, classify_dimensions, classify_multi_label and 2 more); 3 tools can send data out of your system (classify_texts, classify_dimensions and classify_multi_label).

The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 11, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

5 tools

Changes things 5Claude Code: ask
  • classify_dimensionsClassify each text by several named dimensions, such as team, urgency and kind, in one request.Reads text others writeCan send data outNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Classify several dimensions per text
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
  • classify_multi_labelLike classify_texts, but each text gets every label that applies (possibly none), with an independent 0-1 score per label.Reads text others writeCan send data outNo findings

    Why it is in this group

    • The name "classify_multi_label" says "label": a word for a change.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Tag texts with every label that applies
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
  • classify_textsSort up to 1,000 texts into exactly one of your own labels each, with confidence per answer.Reads text others writeCan send data outNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Classify texts into one label each
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
  • count_labelsClassify up to 1,000 texts and return only a histogram: how many landed on each label, and how many the model was unsure about.Reads text others write1 finding

    Why it is in this group

    • The name "count_labels" says "count": a word for reading.
    • The server marks it as not read-only (readOnlyHint: false).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.

    Findings

    • Warn

      The server marks "count_labels" as not read-only (readOnlyHint: false), and its words say it reads.

      Matched text

      annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":true}; The name "count_labels" says "count": a word for reading.

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Count how many texts fall under each label
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
  • review_uncertainClassify 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.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Find the texts the classifier was unsure about
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write5
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out3
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:51 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
5
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://classifier.dev/.well-known/oauth-protected-resource
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 5 tools that change things (5 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://classifier.dev/mcp: tools/list returned 5 tools to an anonymous client, including classify_texts (write), classify_dimensions (write), classify_multi_label (write), count_labels (write), review_uncertain (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

1 warn
  • The server marks "count_labels" as not read-only (readOnlyHint: false), and its words say it reads.

    Matched text

    annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":true}; The name "count_labels" says "count": a word for reading.

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [],
    "ask": [
      "mcp__classifier__classify_texts",
      "mcp__classifier__classify_dimensions",
      "mcp__classifier__classify_multi_label",
      "mcp__classifier__count_labels",
      "mcp__classifier__review_uncertain"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as classifier. Review it before you use it.

Capability tags behind 5 rules
  • mcp__classifier__classify_texts untrusted-input, outbound
  • mcp__classifier__classify_dimensions untrusted-input, outbound
  • mcp__classifier__classify_multi_label untrusted-input, outbound
  • mcp__classifier__count_labels untrusted-input
  • mcp__classifier__review_uncertain untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/dev.classifier/classifier/verify?hash=60c34596c5fe6c8e771ec8585e7cdbb197f2e0d37ab2f4c412e1b11fc7a6ed00" | jq -e '.changed == false'

Pinned hash 60c34596c5fe, from Nov 11, 2026, 07:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/dev.classifier/classifier/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for dev.classifier/classifier
[![Anlyon Radar](https://radar.anlyon.com/badge/dev.classifier/classifier.svg)](https://radar.anlyon.com/servers/dev.classifier/classifier)

Source: MCP Registry · repository. Synced Oct 21, 2026, 18:11 UTC.

classifier.dev MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the classifier.dev MCP server safe?

No scan can promise that. What its definitions show: 5 tools, 5 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the classifier.dev MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the classifier.dev MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the classifier.dev MCP server have?

5 tools: 5 write. classify_texts, classify_dimensions, classify_multi_label, count_labels and review_uncertain.

Does the classifier.dev MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the classifier.dev MCP server send data to outside services?

3 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): classify_texts, classify_dimensions and classify_multi_label.

Has the classifier.dev MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 11, 2026.