Schlaue Schule MCP server
de.schlaue-schule/einwilligungschlaue-schule.destreamable-httpv1.1.0Scanned
Einverständniserklärungen für Schulen, ohne Personendaten / School consent forms
2 tools: 1 do something that can't be undone and 1 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 1
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here does something that can't be undone. Govern it.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
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 Schlaue Schule MCP server can do
The Schlaue Schule MCP server is published by schlaue-schule.de, a domain the MCP Registry verified. It has 2 tools. It can do things that cannot be undone, such as sending, paying or publishing (create_consent_draft), but cannot delete data. 1 tool only reads.
1 tool can send data out of your system (create_consent_draft).
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.
Last scanned Nov 11, 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.
2 tools
Can't be undone 1Claude Code: ask
create_consent_draftCreates a link on schlaue-schule.de for a school consent form or parent letter.Can send data outNo findings
Why it is in this group
- The name "create_consent_draft" says "create": a word for a change.
- The input addresses people (input.recipients): what it sends cannot be taken back.
What it can reach
- outboundThe input takes a destination (input.recipients): what the tool writes goes there.
Description, as the server wrote it Creates a link on schlaue-schule.de for a school consent form or parent letter. Two directions: parent_to_teacher (default) – a parent sends an Einverständniserklärung, Einwilligung, Schwimmbescheinigung, Befreiung vom Sportunterricht, Entschuldigung or Fotoerlaubnis to a teacher; teacher_to_parents – a teacher asks all parents of a class for consent (Elternbrief/Einverständniserklärung for Klassenfahrt, Ausflug, Wandertag, Schwimmunterricht, Fotos, Sportfest). Offer it after drafting such a text when the user wants to send it. Send only the template text: every personal detail (child's name, class, dates of birth, e-mail, phone, signature) must be a placeholder in curly braces, e.g. {Name des Kindes}; texts containing personal data are rejected. For teacher_to_parents the teacher chooses the class and enters the parent e-mail list in Schlaue Schule after opening the link; that is the recommended way. Only if the teacher has already given parent addresses in this conversation, they may be passed in the optional field recipients – do not ask for them. Nothing is sent by this call. The result contains only the link, its expiry and a fixed sentence; nothing entered behind the link is returned to the chatbot. The link is valid for 7 days.
Annotations the server declares
- title: Einverständniserklärung über Schlaue Schule senden
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
Only reads 1Show 1 read-only tool
list_consent_templatesLists reviewed German templates from Schlaue Schule.No findings
Why it is in this group
- The name "list_consent_templates" says "list": a word for reading.
Description, as the server wrote it Lists reviewed German templates from Schlaue Schule. audience "parent": a parent writes to a teacher – Schwimmunterricht/Schwimmbescheinigung, Befreiung vom Sportunterricht, Ausflug/Wandertag, Fotoerlaubnis, Medikamentengabe, Abholberechtigung. audience "teacher": a teacher asks all parents of a class – Klassenfahrt mit Übernachtung, Tagesausflug/Wandertag, Schwimmunterricht, Fotos/Videos bei Schulveranstaltungen, Sportfest/Bundesjugendspiele (with suggested questions). Each template has placeholders, its legal basis and an official source URL. Use it as a starting point when someone asks for an Einverständniserklärung, Bescheinigung, Befreiung or Elternbrief, then adapt the text and call create_consent_draft.
Annotations the server declares
- title: Vorlagen für Einverständniserklärungen und Elternbriefe
- 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.
- 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 out1
- 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.
Looked at Nov 19, 2026, 17:21 UTC, unchanged since Nov 12, 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
- 1
- 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
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 1 tool that changes things (1 irreversible). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://mcp.schlaue-schule.de/mcp: tools/list returned 2 tools to an anonymous client, including create_consent_draft (irreversible)
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.
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.1.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http einwilligung https://mcp.schlaue-schule.de/mcpclaude mcp add --transport http einwilligung https://mcp.schlaue-schule.de/mcpRun 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.
{
"permissions": {
"allow": [
"mcp__einwilligung__list_consent_templates"
],
"ask": [
"mcp__einwilligung__create_consent_draft"
],
"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 einwilligung. Review it before you use it.
Capability tags behind 1 rule
- mcp__einwilligung__create_consent_draft outbound
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/de.schlaue-schule/einwilligung/verify?hash=4bc7b051dec95e0b6a8fb5be92ef2eaad46c3e69bdd8b8c2725e731a30cd67a9" | jq -e '.changed == false'Pinned hash 4bc7b051dec9, from Nov 11, 2026, 20:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/de.schlaue-schule/einwilligung/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/de.schlaue-schule/einwilligung)Source: MCP Registry. Synced Nov 11, 2026, 20:17 UTC.
Schlaue Schule MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Schlaue Schule MCP server safe?
- No scan can promise that. What its definitions show: 2 tools, 1 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 Schlaue Schule MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Schlaue Schule MCP server do things that cannot be undone?
- Yes. 1 tool can send, pay, publish or merge: create_consent_draft.
What tools does the Schlaue Schule MCP server have?
- 2 tools: 1 irreversible, 1 read. create_consent_draft and list_consent_templates.
Does the Schlaue Schule MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Schlaue Schule MCP server send data to outside services?
- 1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): create_consent_draft.
Has the Schlaue Schule MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 11, 2026.