simply-mcp@0.1.0
CAUTION· not startedPublisher claims: "A modern Python framework for building MCP servers with multiple API styles" Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Not started: dependency install failed; the server itself was not observed.- Tested
- the dependency install step · every file read, file written and host contacted by what ran
- Not tested
- server startup · the tool list · tool behavior
What this means for the label: Caution here covers what ran. The server's tools were not exercised with a real credential, so nothing about their behavior is asserted; the credential summary below says what to do with that.
Before you give it your token
- It will ask for
MCP_HTTP_AUTH__ENABLEDConfiguration, not credentials: MCP_HTTP_SERVER__PORT- Where it talks to
- no vendor host named in the codeAlso astral.sh, provider.com — not the publisher's domain; check what for before connecting.
- What the honeypot saw
- no credential files read · no network
- What we could not test
- server startup · the tool list · tool behavior
Connect it with a scoped credential, under the guard, and read the third-party hosts first. The code names astral.sh, provider.com as well as its own vendor. The guard injects MCP_HTTP_AUTH__ENABLED only into requests to the host you bind (and its subdomains) and refuses the rest.
Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.
Is [email protected] safe to install?
KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios; not started: dependency install failed; the server itself was not observed) on 2026-11-18 and scored it 77/100 (Caution). It is not known to be malicious, but it has behaviour or code a security policy should decide on before install. Notable findings: OS command execution function call detected. Summary: no network, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 0 s · 2 scenarios · 0 deviationsStatic findings
os.system("cls" if os.name == "nt" else "clear")Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.result = subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.# Force kill if graceful shutdown failsFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.process = subprocess.Popen(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.self.process = subprocess.Popen(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.…g_lines": 0, "excluded_lines": 0}, "missing_lines": [], "excluded_lines": []}, "mcp_server": {"executed_lines": [442, 548], "summary": {"covered_lines": 2, "num_statements": 2, "percent_covered": 100.0, "percent_covered_display": "100", "m…Fix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.self.process = subprocess.Popen(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.result = subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.spec.loader.exec_module(module)Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.spec.loader.exec_module(module)Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.spec = importlib.util.find_spec(module_path)Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.module = importlib.util.module_from_spec(spec)Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.- [ ] Create `SimplyMCPConfig` root modelFix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.pkg_module = importlib.util.module_from_spec(pkg_spec)Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.module = importlib.util.module_from_spec(spec)Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.pkg_spec.loader.exec_module(pkg_module)Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.Cost to the agent
Tokens estimated at four characters each. The tool list is re-read by the agent on every turn, so it is the number to compare between servers that do the same job: ranked across the index.
Known vulnerabilities
No advisories in OSV for simply-mcp@0.1.0 as of 30 min ago. This is the package itself, not its dependencies.
What would make this Verified
3 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%- OS command execution function call detected≈ +9 on the totalBuild commands from fixed arguments; do not interpolate untrusted strings into a shell.
- Unclaimed publisher≈ +8 on the totalClaim clockwork-innovations: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
- Python subprocess execution detected≈ +2 on the totalBuild commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.
- Process kill command≈ +2 on the totalBuild commands from fixed arguments; do not interpolate untrusted strings into a shell.
- MCP server using network transport (SSE/HTTP)≈ +2 on the totalNamespace tool names and keep tool descriptions literal; no instructions to the agent inside them.
- Dynamic module loading≈ +1 on the totalBuild commands from fixed arguments; do not interpolate untrusted strings into a shell.