Home / MCP registry index / app.meistron/meistron
Meistron
app.meistron/meistron in the official MCP registry.
Endpoint https://meistron.app/api/mcp.
The registry describes it as: Auftraege, Rechnungen, Material und Zeiten eines Handwerksbetriebs abfragen und pflegen.
We read its 31 tools on 2026-10-21. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
betrieb_ueberblick tagesuebersicht beleg_pdf auftragsnachweis_pdf bestandsliste_pdf auftraege_suchen auftrag_ansehen rechnungen_suchen rechnung_ansehen rechnung_versand_vorschau angebote_suchen zeiten_auswerten kunden_suchen material_suchen material_ansehen material_buchen material_zuweisen rechnung_anlegen angebot_anlegen einstellungen_ansehen einstellungen_aendern lieferanten_auflisten rechnung_versenden datei_anfordern datei_stand mitarbeiter_auflisten auftrag_anlegen auftrag_aendern kunde_anlegen wartungsvertraege_suchen wartungsvertrag_ansehen
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/app-meistron-meistron)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.