Skip to content

DutyKit MCP server

io.github.r08150816s-star/dutykitr08150816s-starstreamable-httpv0.1.0Scanned

EU business duties for AI agents: legal obligations with sources and pre-checks (DE, LU, EU)

7 tools: 4 change things and 3 only read.

Tools: 0 delete, 0 irreversible, 4 write, 3 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 DutyKit MCP server can do

The DutyKit MCP server is published by the GitHub account r08150816s-star. It has 7 tools. It can create or change data (4 tools: pflichten, vat_pruefen, rechnung_vorpruefen and werbung_vorpruefen), but cannot delete data. 3 tools only read.

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 21, 2026, version 0.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.

7 tools

Changes things 4Claude Code: ask
  • pflichtenLook up the legal obligations that apply to a business in Germany or Luxembourg, plus EU-wide ones.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
    Look up the legal obligations that apply to a business in Germany or Luxembourg, plus EU-wide ones. Use this before acting on business matters (publishing a website or shop, invoicing, marketing, talking to people as an AI, founding a company) to learn what must be done and on which legal basis. Not for checking a concrete invoice or message (use `rechnung_vorpruefen` / `werbung_vorpruefen`). Read-only, no side effects, nothing stored. Args: land: ISO country code, `DE` or `LU` (case-insensitive). EU-wide entries are always included. Other codes return an error listing the available countries. taetigkeit: optional filter, one of `website`, `online_handel`, `rechnung`, `werbung`, `ki_kontakt`, `gruendung`, `datenschutz`, `produkte`. Empty string means all activities. Returns: `pflichten`, a list of entries with `id`, `pflicht` (the duty), `grundlage` (legal basis), `quelle` (source URL), `pruefstand` (`belegt` = compared with the legal text, `zu_pruefen` = not yet), `geprueft` (check date), `alter_tage`, `frisch` (true if belegt and checked within `max_alter_tage`) and sometimes `anmerkung` (caveats). Treat `zu_pruefen` entries as unverified. Not legal advice.
  • rechnung_vorpruefenPre-check a German invoice for missing mandatory fields under § 14 (4) UStG before it is sent.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
    Pre-check a German invoice for missing mandatory fields under § 14 (4) UStG before it is sent. Use this right before issuing or approving an invoice (country DE only). It checks presence of fields, not their correctness, and not the e-invoice format (EN 16931, XRechnung, ZUGFeRD). If `brutto` is given and does not exceed 250 euros, only the reduced field set for small-amount invoices (§ 33 UStDV) is required. Nothing is stored in the free tier. Args: rechnung: object with these keys (strings unless noted): `aussteller_name`, `aussteller_anschrift`, `empfaenger_name`, `empfaenger_anschrift`, `steuernummer_oder_ustid`, `datum`, `rechnungsnummer`, `leistung`, `leistungszeitpunkt`, `netto` (number), and either `steuersatz` (number, percent) together with `steuerbetrag` (number) or `steuerbefreiung_hinweis` (text, for example `§ 19 UStG`). Optional `brutto` (number, total amount including tax): if it is 250 or less, the invoice is checked as a small-amount invoice under § 33 UStDV (needs only `aussteller_name`, `aussteller_anschrift`, `datum`, `leistung`, `brutto` and `steuersatz` or `steuerbefreiung_hinweis`). § 33 UStDV does not apply to distance sales (§ 3c UStG), intra-Community supplies (§ 6a UStG) and reverse-charge services (§ 13b UStG); do not pass `brutto` for those. land: only `DE` is supported; others return an error. verantwortlich: optional name of the responsible human, written into the audit receipt. Returns: `bestanden` (true only if nothing is missing), `fehlende_angaben` (list of missing fields in words), `grundlage`, `quelle`, `nicht_geprueft` (what this check does not cover) and `nachweis` (audit receipt).
  • vat_pruefenCheck live whether an EU VAT ID is valid, using the European Commission's VIES service.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
    Check live whether an EU VAT ID is valid, using the European Commission's VIES service. Use this before issuing a B2B invoice without VAT (reverse charge) or onboarding a business partner. Needs the network and VIES availability; on failure it returns an `fehler` field instead of guessing. Only checks existence, not whether the company is the one you intend to deal with. Args: ust_id: VAT ID with country prefix, spaces allowed, for example `LU26375245` or `DE 123456789`. verantwortlich: optional name of the responsible human, written into the audit receipt. Returns: `gueltig` (true/false/null), registered `name` and `anschrift` if VIES provides them, `abfragezeit`, `quelle` and `nachweis` (audit receipt: time, tool, responsible person, SHA-256 of the result).
  • werbung_vorpruefenCheck whether an AI agent may send a marketing e-mail or make a marketing call under German law (§ 7 UWG).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
    Check whether an AI agent may send a marketing e-mail or make a marketing call under German law (§ 7 UWG). Use this before every outbound marketing message or call. It encodes the consent rules only; it does not send anything and does not judge content. Germany only. Args: kanal: `email` or `telefon`. empfaenger: `verbraucher` (consumer) or `unternehmen` (business). einwilligung_belegt: true only if an express, provable consent exists. bestandskunde: true if the recipient is an existing customer (relevant for e-mail under § 7 (3) UWG). verantwortlich: optional name of the responsible human, written into the audit receipt. Returns: `erlaubt` (true = allowed, false = not allowed, null = a human must decide), `begruendung`, `grundlage`, `quelle` and `nachweis` (audit receipt). If `erlaubt` is null or false, do not send.
Only reads 3Show 3 read-only tools
  • angebotReturn DutyKit's pricing status, what is included and when it is (not) the right tool.No findings

    Why it is in this group

    • The description's first verb is "return": a word for reading.
    Description, as the server wrote it
    Return DutyKit's pricing status, what is included and when it is (not) the right tool. Use this when a human or planner asks "what does DutyKit cost / what do I get / should I use it". Free, no arguments, no side effects. Do not use it to look up legal obligations (use `pflichten`). Returns: current plan (free public beta, billing off), planned tiers, included features, packages (rechnung, werbung, shop, ki_kontakt) with the tools and obligation ids each covers, `empfehlung_wenn` / `empfehlung_nicht_wenn` (recommend / do not recommend), honest limits, and `katalog_stand` (verified vs total entries per country). Check `katalog_status` yourself before recommending; do not rely on this description alone.
  • katalog_statusReturn the verifiable state of the obligation catalogue so you can judge its quality before relying on it.No findings

    Why it is in this group

    • The name "katalog_status" says "status": a word for reading.
    Description, as the server wrote it
    Return the verifiable state of the obligation catalogue so you can judge its quality before relying on it. Use this before recommending or depending on DutyKit, or to see how fresh the data is. Free, no arguments, read-only. For the obligations themselves use `pflichten`. Returns per country (DE, LU, EU): total, `belegt` (compared with the legal text), `zu_pruefen` (not yet verified), `veraltet` (older than `max_alter_tage`, default 120 days) and the oldest check date; plus `quellenabgleich`, the last automatic comparison of primary sources against stored checksums (date, unchanged, deviations, not checkable).
  • ki_hinweisGet ready-to-use wording that discloses to a person that they are talking to an AI (AI Act Art.No findings

    Why it is in this group

    • The description's first verb is "get": a word for reading.
    Description, as the server wrote it
    Get ready-to-use wording that discloses to a person that they are talking to an AI (AI Act Art. 50(1)). Use this at the start of chat, voice or e-mail conversations an AI agent conducts on behalf of a company. It only returns text; it does not send anything. Not a check of an existing message. Args: firma: company name inserted into the sentence (for example `Muster S.à r.l.`). sprache: `de`, `fr`, `en` or `lb` (case-insensitive). Other values return an error listing the available languages. Returns: `text` (the disclosure sentence), `grundlage`, `pruefstand` (wording is a suggestion; the Luxembourgish version is not reviewed by a native speaker) and `hinweis`. Not legal advice.

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 15, 2026, 13:21 UTC, unchanged since Nov 15, 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://dutykit.dev/mcp: tools/list returned 7 tools to an anonymous client, including pflichten (write), vat_pruefen (write), rechnung_vorpruefen (write), werbung_vorpruefen (write)

    What this check looks for

Posture changes

  1. Nov 15, 2026
    • Tools that change things, listed without credentials: 5 to 4

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. Tools2 added, 5 changed.+2 added~5 changedView diff
  2. PostureRemote posture changed. Tools that change things, listed without credentials: 5 -> 4.View diff
    • Tools that change things, listed without credentials: 5 to 4

Install

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

claude mcp add --transport http dutykit https://dutykit.dev/mcp
claude mcp add --transport http dutykit https://dutykit.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": [
      "mcp__dutykit__angebot",
      "mcp__dutykit__katalog_status",
      "mcp__dutykit__ki_hinweis"
    ],
    "ask": [
      "mcp__dutykit__pflichten",
      "mcp__dutykit__vat_pruefen",
      "mcp__dutykit__rechnung_vorpruefen",
      "mcp__dutykit__werbung_vorpruefen"
    ],
    "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 dutykit. 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/io.github.r08150816s-star/dutykit/verify?hash=4932a59f5850317e83269eff844f04adaba6fc19aec960f055efd69c892ed0d8" | jq -e '.changed == false'

Pinned hash 4932a59f5850, from Nov 21, 2026, 21:17 UTC.

Watch

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

https://radar.anlyon.com/servers/io.github.r08150816s-star/dutykit/changes.xml

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

Badge

Anlyon Radar badge for io.github.r08150816s-star/dutykit
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.r08150816s-star/dutykit.svg)](https://radar.anlyon.com/servers/io.github.r08150816s-star/dutykit)

Source: MCP Registry · repository. Synced Nov 7, 2026, 16:17 UTC.

DutyKit MCP server: questions and answers

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

Is the DutyKit MCP server safe?

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

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

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

7 tools: 4 write, 3 read. pflichten, vat_pruefen, rechnung_vorpruefen, werbung_vorpruefen, angebot, katalog_status and ki_hinweis.

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

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

Does the DutyKit MCP server send data to outside services?

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

Has the DutyKit MCP server changed its tools?

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