Home / MCP registry index / io.github.epistemedeus/ein-llc
io.github.epistemedeus/ein-llc
io.github.epistemedeus/ein-llc in the official MCP registry.
Endpoint https://ein.llc/mcp. Source: github.com/epistemedeus/ein-llc-lean.
The registry describes it as: A human must claim and pay before EIN.LLC files. Agents may assess, prepare, and read status.
We read its 7 tools on 2026-10-27. 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
assess_formation prepare_application get_application_status get_formation_contract compare_states explain_ein_route get_compliance_deadlines
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-github-epistemedeus-ein-llc)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.