Super is the project name. superuser is the Python package name. io.github.fitzyracing1/superuser is the identity listed in the MCP Registry. Keeping those names together makes it easier to trace a discovery result back to a package and then to the source repository.
One project, three useful names
The public registry entry for version 0.1.0 names the GitHub repository, points to the PyPI package superuser at version 0.1.0, and declares stdio transport. Those are publication facts. They do not imply customer adoption, an independent security audit, or a guarantee that any particular installation has its protections configured.
System tools need a boundary
Super exposes system-administration capabilities over the Model Context Protocol. The public landing describes the guard vocabulary as look, fight, listen, break: inspect the call, authorize it, require approval where configured, and block dangerous commands or leaking responses.
Configured protection, not implied protection
The repository describes inspection, authorization, an approval gate, a command denylist, and audit logging. Behavior changes when integrations are missing. Absence of inspection credentials is not the same as a protected call. A registry entry cannot do that configuration work for you.
Follow the publication trail
Start with the versioned registry entry and the versioned PyPI page, then read the source instructions. Some README installation wording still says the package is not yet on PyPI, while the public version page exists. This note uses the direct package and registry records. There are no enterprise customer claims attached.
Sources: Super repository · superuser 0.1.0 on PyPI · MCP Registry record · Landing page.
