mcp@3.1.0
CAUTIONPublisher claims: "Model Context Protocol (MCP) native server for AI-SDLC tools, resources, and governance" Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Is [email protected] safe to install?
KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios) on 2026-11-03 and scored it 75/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: Prompt injection. Summary: no network, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 2 s · 2 scenarios · 0 deviationst+CategoryObserved action
0.0sprocessno install scripts in bundle
1.8sprocessdependency install exit 1
2.1sprocessexec /usr/bin/timeout
2.1sprocessexited 1: Node.js v22.23.4
2.1sclaimedno tools/list reply (exit 1)
2.1sprocessscript backend runs setup only
Static findings
CRITICAL
Prompt injectionREADME.md:141 · Prompt injection — explicit attempt to bypass safety measuresFix: Keep SKILL.md to visible, descriptive text. Remove comments and encoded text that address the agent.
AST01MEDIUM
MCP server using network transport (SSE/HTTP)dist/index.d.ts:55 · MCP server using network transport (SSE/HTTP) — data sent over networkFix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.
AST04What would make this Verified
5 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%- Text that tells the agent to ignore its instructions≈ +9 on the totalDelete phrases like "ignore previous instructions", "override", "bypass" from SKILL.md and tool descriptions. Describe what the skill does; do not instruct the agent about other rules.
- Unclaimed publisher≈ +8 on the totalClaim aisdlc: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
- Does not do what the description says≈ +5 on the totalIn the sandbox the skill never performed the task it claims (no call to the service it is for). Make sure the happy path runs without extra setup, or describe the real behavior.
- New publisher≈ +3 on the totalTime clears this on its own after 14 and 30 days. Claiming the handle (+50) is the fastest way past it.
- 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.
Publish a new version to npm, then queue it here. Not your skill? Claim the handle to get verdict changes by email.Claim aisdlc