Skip to content

Teollimi MCP server

com.teollimi/teollimiteollimi.comstreamable-httpv1.0.0Scanned

Data breaches in Korea, Japan, the US and beyond with sources, open settlements and what to do.

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
  • 1 finding

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 Teollimi MCP server can do

The Teollimi MCP server is published by teollimi.com, a domain the MCP Registry verified. It has 5 tools. It can create or change data (4 tools: recent_breaches, check_services, open_settlements and breach_response_steps), 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.

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 4Claude Code: ask
  • breach_response_stepsSteps to take after a breach notice, by the kinds of data that leaked (password, card, national ID and so on), with official places to check exposure or get help in Korea, the US a…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
    Steps to take after a breach notice, by the kinds of data that leaked (password, card, national ID and so on), with official places to check exposure or get help in Korea, the US and Japan.

    Annotations the server declares

    • title: What to do after a data breach
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • check_servicesGiven up to 10 companies or services a person uses, say for each whether Teollimi has a reported breach, how many, and the latest one with what leaked.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
    Given up to 10 companies or services a person uses, say for each whether Teollimi has a reported breach, how many, and the latest one with what leaked. Absence of a record does not mean the service was never breached.

    Annotations the server declares

    • title: Check services I use for breaches
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • open_settlementsUS class action data breach settlements that are still taking claims, soonest deadline first, optionally for one company.1 finding

    Why it is in this group

    • The name "open_settlements" says "open": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "open_settlements" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "open_settlements" says "open": a word for a change.

      What this check looks for
    Description, as the server wrote it
    US class action data breach settlements that are still taking claims, soonest deadline first, optionally for one company. Returns up to 5 with claim deadline, maximum payout per person, whether proof is needed, the official claim site and the Teollimi page.

    Annotations the server declares

    • title: Find open data breach settlements
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • recent_breachesData breaches announced in the last few days (default 30), newest first, optionally in one country.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
    Data breaches announced in the last few days (default 30), newest first, optionally in one country. Returns up to 10 incidents with date, scale, leaked data types, a source link and the Teollimi page.

    Annotations the server declares

    • title: List recent data breaches
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
Only reads 1Show 1 read-only tool
  • search_breachesFind publicly reported data breaches of a company or service by name (any language, e.g.No findings

    Why it is in this group

    • The name "search_breaches" says "search": a word for reading.
    Description, as the server wrote it
    Find publicly reported data breaches of a company or service by name (any language, e.g. Coupang, 쿠팡, SK Telecom, Ticketmaster, アスクル). Returns up to 5 most recent incidents with date, number affected, leaked data types, compensation and fine flags, a source link and the Teollimi page, plus how many incidents match in total.

    Annotations the server declares

    • title: Search data breaches by company
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

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 18, 2026, 16:21 UTC, unchanged since Nov 11, 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://teollimi.com/mcp: tools/list returned 5 tools to an anonymous client, including recent_breaches (write), check_services (write), open_settlements (write), breach_response_steps (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

1 warn
  • The server marks "open_settlements" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "open_settlements" says "open": a word for a change.

    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 teollimi https://teollimi.com/mcp
claude mcp add --transport http teollimi https://teollimi.com/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": [
      "mcp__teollimi__search_breaches"
    ],
    "ask": [
      "mcp__teollimi__recent_breaches",
      "mcp__teollimi__check_services",
      "mcp__teollimi__open_settlements",
      "mcp__teollimi__breach_response_steps"
    ],
    "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 teollimi. 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/com.teollimi/teollimi/verify?hash=5cf66d0e865843da09412aa51940d70576ed75b64df2a085d14f66e9cc4c6a40" | jq -e '.changed == false'

Pinned hash 5cf66d0e8658, from Nov 11, 2026, 03:17 UTC.

Watch

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

https://radar.anlyon.com/servers/com.teollimi/teollimi/changes.xml

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

Badge

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

Source: MCP Registry. Synced Nov 11, 2026, 03:17 UTC.

Teollimi MCP server: questions and answers

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

Is the Teollimi MCP server safe?

No scan can promise that. What its definitions show: 5 tools, 4 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 Teollimi MCP server delete data?

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

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

5 tools: 4 write, 1 read. recent_breaches, check_services, open_settlements, breach_response_steps and search_breaches.

Does the Teollimi MCP server need sign-in or OAuth?

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

Does the Teollimi MCP server send data to outside services?

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

Has the Teollimi MCP server changed its tools?

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