Skip to content

Seb Labs MCP server

dev.seblabs/seblabsseblabs.devstreamable-httpv1.1.0Scanned

Typed AI decisions for agents: classify, route, screen evidence, score and batch-label text.

5 tools: 4 change things and 1 only read.

Tools: 0 delete, 0 irreversible, 4 write, 1 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

4 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Seb Labs MCP server can do

The Seb Labs MCP server is published by seblabs.dev, a domain the MCP Registry verified. It has 5 tools. It can create or change data (4 tools: seb_demo, seb_decide, seb_route and seb_batch_decide), but cannot delete data. 1 tool only reads.

None of its tools reads private data, brings in text other people write, or sends data out.

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 9, 2026, version 1.1.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 4Claude Code: ask
  • seb_batch_decideUse to classify, screen, triage, rank by an explicit rubric, or bulk-label up to 100 independent text states with the same 1–10 typed questions.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Use to classify, screen, triage, rank by an explicit rubric, or bulk-label up to 100 independent text states with the same 1–10 typed questions. Each result retains its input index and its own success/error; up to four items run concurrently. Inspect all per-item errors and retry failed items only, not the whole successful batch. Input limits and the account request/token-rate limits still apply. Requires a funded account token; each successful item/question charges input tokens. Not a bulk discount or a single flat-priced request.
  • seb_decideUse for evidence/claim support checks, binary screening, rubric scoring, or several related judgments on one text state.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Use for evidence/claim support checks, binary screening, rubric scoring, or several related judgments on one text state. Supply 1–10 named questions: choice has 2–20 option keys mapped to descriptions (or null); noul asks a precisely worded positive/yes proposition and returns its probability in [0,1]; score has 2–5 rubric levels ordered low to high and returns a 0-based expected ordinal score with probabilities. Returns typed answers and metered usage without a prose explanation. Include all needed facts; no browsing or retrieval. Requires a funded account token; shared state is metered separately for each question.
  • seb_demoUse for a free connection/interface check or a fixed example of enterprise, finance, robotics or handoff decisions.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Use for a free connection/interface check or a fixed example of enterprise, finance, robotics or handoff decisions. Returns labeled illustrative probabilities, never live inference. No account token is required. Use a paid tool to judge your own input.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • seb_routeUse for fast single-label classification or routing: ticket triage, intent/topic/sentiment labels, selecting a tool or workflow, guardrail categories or an escalation decision.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Use for fast single-label classification or routing: ticket triage, intent/topic/sentiment labels, selecting a tool or workflow, guardrail categories or an escalation decision. Supply the relevant context and 2–20 unique option labels (up to 80 characters each); add an unclear/escalate label if appropriate. Returns the selected label and probabilities for every option. No explanation or downstream action. Model-estimated probabilities can be wrong. Requires a funded account token; charges input tokens.
Only reads 1Show 1 read-only tool
  • seb_fin_analyzeUse only for entitled accounts with an enabled dedicated Seb-9B-Fin backend, to judge financial language or supplied point-in-time market context with the same choice/noul/score sc…No findings

    Why it is in this group

    • The name "seb_fin_analyze" says "analyze": a word for reading.
    Description, as the server wrote it
    Use only for entitled accounts with an enabled dedicated Seb-9B-Fin backend, to judge financial language or supplied point-in-time market context with the same choice/noul/score schema. The public general-model endpoint does not currently enable this specialist. Returns typed model estimates, not investment advice, a forecast guarantee or an executed trade. Missing finance configuration/entitlement returns an error; never assume general-model fallback. Paid input-token metering applies when enabled.

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 or untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
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 17, 2026, 15:23 UTC, unchanged since Oct 26, 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
4
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
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 4 tools that change things (4 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://mcp.seblabs.dev/mcp: tools/list returned 5 tools to an anonymous client, including seb_demo (write), seb_decide (write), seb_route (write), seb_batch_decide (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

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

  1. Tools3 changed.~3 changedView diff

Install

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

claude mcp add --transport http seblabs https://mcp.seblabs.dev/mcp --header 'Authorization: <your-authorization>'
claude mcp add --transport http seblabs https://mcp.seblabs.dev/mcp --header 'Authorization: <your-authorization>'

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": [
      "mcp__seblabs__seb_fin_analyze"
    ],
    "ask": [
      "mcp__seblabs__seb_demo",
      "mcp__seblabs__seb_decide",
      "mcp__seblabs__seb_route",
      "mcp__seblabs__seb_batch_decide"
    ],
    "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 seblabs. Review it before you use it.

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.seblabs/seblabs/verify?hash=2690fb60f48ea6a742f1e638cb5c072ba8887f2b860d84247cbd7e243ad124e7" | jq -e '.changed == false'

Pinned hash 2690fb60f48e, from Nov 9, 2026, 08:17 UTC.

Watch

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

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

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

Badge

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

Source: MCP Registry. Synced Oct 26, 2026, 04:17 UTC.

Seb Labs MCP server: questions and answers

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

Is the Seb Labs MCP server safe?

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

Can the Seb Labs MCP server delete data?

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

Can the Seb Labs 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 Seb Labs MCP server have?

5 tools: 4 write, 1 read. seb_demo, seb_decide, seb_route, seb_batch_decide and seb_fin_analyze.

Does the Seb Labs MCP server need sign-in or OAuth?

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

Does the Seb Labs MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Seb Labs MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Nov 9, 2026. Every change is on this page and in its Atom feed.