io.github.fitzyracing1/superuser
PYPI · SUPERUSER
Permission-gated superuser (sysadmin) MCP agent with enterprise guardrails and audit.
Available components
Last scanned (6 hours ago)
Scores higher than 61% of PyPI servers
Category Cloud Infrastructure
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs setuptools.build_meta at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 0 of 33 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 13 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability59
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 303 tokens (~37/item across 8 items; 8 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 4 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- 3 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 26 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- 23 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 22 Oct 26 50
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed pypi/superuser@0.1.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | setuptools.build_meta |
Background: Why install scripts are a supply-chain risk →
Dependencies 33 packages
| Packages resolved | 33 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
disk_usage ~15
Report disk usage per mounted partition.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
github_create_issue_comment ~59
Comment on an issue/PR. Write action: requires confirm=true and GITHUB_ALLOW_WRITES.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | yes | – |
| confirm | boolean | – | – |
| issue_number | integer | yes | – |
| repo | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
github_get_repo ~31
Get metadata for an allowlisted repo (e.g. 'owner/name').
| Name | Type | Req | Description |
|---|---|---|---|
| repo | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
github_list_issues ~39
List issues for an allowlisted repo.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| repo | string | yes | – |
| state | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
list_processes ~38
List top processes. sort_by is 'memory' or 'cpu'.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| sort_by | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
run_command ~79
Run a shell command on this machine. Non-allowlisted commands are HIGH risk and require confirm=true. Commands matching the dangerous-command denylist are always rejected, and every call is inspected by Cisco AI Defense and written to the audit log.
| Name | Type | Req | Description |
|---|---|---|---|
| command | string | yes | – |
| confirm | boolean | – | – |
| timeout | integer | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
security_status ~21
Report the agent's guardrail configuration and Cisco AI Defense status.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
system_status ~21
Report host, CPU, memory, and uptime for this machine.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the io.github.fitzyracing1/superuser MCP server?
io.github.fitzyracing1/superuser runs locally as a PyPI package, launched with uvx superuser. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · superuser
claude mcp add fitzyracing1-superuser -- uvx superuser
What is the io.github.fitzyracing1/superuser MCP server?
io.github.fitzyracing1/superuser is an MCP server listed in the public MCP registry as io.github.fitzyracing1/superuser. Permission-gated superuser (sysadmin) MCP agent with enterprise guardrails and audit. This page covers its PyPI package (superuser).
Is the io.github.fitzyracing1/superuser MCP server safe to use?
io.github.fitzyracing1/superuser scores 65 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.fitzyracing1/superuser MCP server expose?
io.github.fitzyracing1/superuser exposes 8 tools: system_status, disk_usage, list_processes, run_command, github_get_repo, and 3 more. Their descriptions and schemas cost roughly 303 tokens of context every time the server is loaded.
Is the io.github.fitzyracing1/superuser MCP server still maintained?
io.github.fitzyracing1/superuser is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.fitzyracing1/superuser MCP server under?
io.github.fitzyracing1/superuser declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.