mcp-dev-tools@0.55.0
VERIFIEDPublisher claims: "A ready-to-use MCP server for Claude Code and Claude Desktop: 91 developer tools (docker, mongo, sqlite, cue, vitest, workspace) with a strict call policy." Observed in sandbox: no network, touches nothing outside the project, writes no memory.
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
MCP_HTTP_TOKENConfiguration, not credentials: MCP_BUNDLES, MCP_DEBUG, MCP_FS_ROOT, MCP_HTTP_HOST, MCP_HTTP_MAX_SESSIONS, MCP_HTTP_PORT, MCP_PROGRAM_CHECK, MCP_READ_ONLY, MCP_SERVER_NAME, MCP_SERVER_VERSION, MCP_TOOL_TIMEOUT_MS- 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
Connect it with a scoped credential, under the guard. It asks for MCP_HTTP_TOKEN and talks to its vendor. Give the credential to the guard, not the server: the value never enters the server's environment and only travels to the host you bind.
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-13 and scored it 90/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 · 40 s · 2 scenarios · 0 deviationsStatic findings
console.error(`[mcp-server] Streamable HTTP at ${url}${config.http.token ? " (send Authorization: Bearer <token>)" : ""}`);Fix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.export declare function runDevToolsServer(config?: McpServerConfig, run?: RunOptions): Promise<RunningDevToolsServer>;Fix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.export async function runDevToolsServer(config: McpServerConfig = loadConfig(), run?: RunOptions): Promise<RunningDevToolsServer> {Fix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.console.error(`[mcp-server] Streamable HTTP at ${url}${config.http.token ? " (send Authorization: Bearer <token>)" : ""}`);Fix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.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 @procedures/mcp-dev-tools@0.55.0 as of 36 h ago. This is the package itself, not its dependencies.