io.github.Kisyntra/agent-sudo-mcp
PYPI · AGENT-SUDO-MCP · SCANNED SEP 20
MCP adapter for Agent_Sudo: authorization, delegation, provenance, and audit for AI agents.
Available components
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 native-build step with no shell scripting around it. View diagnostics → Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency19
- Repository check failed: no source repository is declared. See how to fix → View diagnostics → Fail
- 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 100 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability73
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 208 tokens (~52/item across 4 items; 4 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
- Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities40
- Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28. See how to fix → Fail
How do I install the io.github.Kisyntra/agent-sudo-mcp server?
io.github.Kisyntra/agent-sudo-mcp runs locally as a PyPI package, launched with uvx agent-sudo-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · agent-sudo-mcp
claude mcp add kisyntra-agent-sudo-mcp -- uvx agent-sudo-mcp
{
"mcpServers": {
"kisyntra-agent-sudo-mcp": {
"command": "uvx",
"args": [
"agent-sudo-mcp"
]
}
}
} {
"servers": {
"kisyntra-agent-sudo-mcp": {
"command": "uvx",
"args": [
"agent-sudo-mcp"
]
}
}
} codex mcp add kisyntra-agent-sudo-mcp -- uvx agent-sudo-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"kisyntra-agent-sudo-mcp": {
"type": "local",
"command": [
"uvx",
"agent-sudo-mcp"
],
"enabled": true
}
}
} openclaw mcp add kisyntra-agent-sudo-mcp --command uvx --arg agent-sudo-mcp
mcp_servers:
kisyntra-agent-sudo-mcp:
command: "uvx"
args: ["agent-sudo-mcp"] {
"McpServers": {
"kisyntra-agent-sudo-mcp": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"agent-sudo-mcp"
]
}
}
} assistant mcp add kisyntra-agent-sudo-mcp -t stdio -c uvx -a agent-sudo-mcp
{
"mcpServers": {
"kisyntra-agent-sudo-mcp": {
"command": "uvx",
"args": [
"agent-sudo-mcp"
]
}
}
} 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.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 −1
- Security disclosure: pass → unverified ▼ functional
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 −2
- Stability: pass → 0.80 functional
- 15 Sept 26 0
- Stability: 0.97 → pass security
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 −2
- Stability: pass → 0.83 functional
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 20 Sept 2026 · Analysed pypi/agent-sudo-mcp@0.5.6
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
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 0 packages
| Packages resolved | 0 |
|---|---|
| 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 →
get_runtime_context ~26
Get current working directory, git repository root, active branch, and workspace status details.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
read_file ~30
Read a local file through agent-sudo policy enforcement.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | File path to read. |
No output schema declared.
No examples provided.
run_shell_command ~71
DEMO/REFERENCE executor: classifies and gates the command through agent-sudo, then executes only a narrow allowlist. It is not a general shell. To gate real commands, embed the agent-sudo authorization engine in your agent (see README).
| Name | Type | Req | Description |
|---|---|---|---|
| command | string | yes | Command line to evaluate. |
No output schema declared.
No examples provided.
write_file ~81
DEMO/REFERENCE executor: classifies and gates the write through agent-sudo, then writes inside the configured workspace (defaults to /tmp/agent-sudo-demo if no workspace is configured). It does not write to arbitrary paths outside the workspace.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | UTF-8 text content. |
| path | string | yes | File path to write. |
No output schema declared.
No examples provided.
What is the io.github.Kisyntra/agent-sudo-mcp server?
io.github.Kisyntra/agent-sudo-mcp is listed in the public MCP registry as io.github.Kisyntra/agent-sudo-mcp. MCP adapter for Agent_Sudo: authorization, delegation, provenance, and audit for AI agents. This page covers its PyPI package (agent-sudo-mcp).
Is the io.github.Kisyntra/agent-sudo-mcp server safe to use?
io.github.Kisyntra/agent-sudo-mcp scores 76 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 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.Kisyntra/agent-sudo-mcp server expose?
io.github.Kisyntra/agent-sudo-mcp exposes 4 tools: read_file, write_file, run_shell_command, get_runtime_context. Their descriptions and schemas cost roughly 208 tokens of context every time the server is loaded.
Is the io.github.Kisyntra/agent-sudo-mcp server still maintained?
io.github.Kisyntra/agent-sudo-mcp is still listed as active in the MCP registry. We last reached this channel on 20 September 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.Kisyntra/agent-sudo-mcp server under?
io.github.Kisyntra/agent-sudo-mcp 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.