Skills/npm/mcp

mcp@4.0.0

VERIFIED

Publisher 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.

Registry npm (MCP server)Publisher aisdlc · publishing for 43 daysInstalls 5,142Last detonated 5d ago
$claude mcp add mcp -- npx -y @aisdlc/mcp
WatchReport an issue

Coverage

Server started and answered tools/list.
Tested
MCP initialize and tools/list · every tool description, for hidden instructions · every file read, file written and host contacted by what ran
Not tested
what the tools do when called with real credentials

Before you give it your token

It will ask for
no credential variables read in the code
Where it talks to
no vendor host named in the code
What the honeypot saw
no credential files read · no network
What we could not test
what the tools do when called with real credentials

Reasonable to connect. No credential asked for, no third-party host named, Server started and answered tools/list.

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) on 2026-11-09 and scored it 83/100 (Verified). It did what it claims and nothing else we could detect: no undeclared network egress, no credential reads, no persistent instruction writes. Summary: no network, touches nothing outside the project, writes no memory.

Behavior trace

Honeypot run · 31 s · 2 scenarios · 0 deviations
t+CategoryObserved action
0.0sprocessno install scripts in bundle
10sprocessdependency install exit 0
31sclaimed26 tools: new, verify, report, sdd_change_new, sdd_check_fix, sdd_deposit, sdd_integrate, get_active_handoff, review_submit, inspect_element, verify_quality, verify_schemas, verify_security, verify_traceability, verify_governance, verify_testing, verify_licenses, verify_duplicates, verify_friction, verify_pdac, verify_privacy, report_dashboard, report_quality, kpi_pr, kpi_release
31sprocessscript backend runs setup only
31sprocessno install scripts to re-run

Static findings

MEDIUM
MCP server using network transport (SSE/HTTP)dist/index.d.ts:59 · MCP server using network transport (SSE/HTTP) — data sent over network…cpServer(options?: CreateMcpServerOptions): Promise<void>; export { type CreateMcpServerOptions, MUTATION_TOOLS, type McpAuditLogEntry, type McpRole, READONLY_ROLES, REVIEWER_ONLY_TOOLS, type RegisterResourcesOptions, type RegisterToolsOpt…Fix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.
AST04
LOW
Prompt injectionREADME.md:141 · Prompt injection — explicit attempt to bypass safety measures · informational: not an instruction file…(string)* | | `verify_friction` | Evaluates progressive friction rules and anti-bypass guardrails (prevents patch-profile changes from modifying protected paths). | `change` *(…Fix: Keep SKILL.md to visible, descriptive text. Remove comments and encoded text that address the agent.
AST01
HIGH
Tool description instructs the agent: safety bypass instructionmcp:tools/verify_friction:1 · Instruction aimed at the agent: safety bypass instructiontes progressive friction rules and anti-bypass guardrails. {"type":"object","properties":{"change":{"type":"string"},Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.
AST01

Cost to the agent

Instructions loaded
≈55 tok
1 file · 10 in bundle
Tool list per prompt
≈2,343 tok
26 tools · 90 per tool
Handshake
788 ms
launch to tools/list, stdio
Undocumented tools
0
description under 20 chars · avg 61

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 @aisdlc/mcp@4.0.0 as of 5d ago. This is the package itself, not its dependencies.