mcp-devtools@2.2.14
VERIFIED· not startedPublisher claims: "multi-functional MCP-devtools server over SSE" 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: Verified 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
Code inventory arrives with this version's next honeypot run.- It will ask for
- unknown until the next run
- Where it talks to
- unknown until the next run
- What the honeypot saw
- no credential files read · no network
- What we could not test
- server startup · the tool list · tool behavior
Not enough was observed to say yet. Not started: dependency install failed; the server itself was not observed. This version's code has not been inventoried for credentials and hosts either; both arrive with its next honeypot run (popular servers first). `vet-skills try mcp-devtools` runs it now and prints the full answer.
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-07 and scored it 87/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: no network, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 0 s · 2 scenarios · 0 deviationsStatic findings
Loads environment variables from .env files found in various locations,Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.workdir_env = os.path.join(repo_path, ".env")Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.<summary> <h4> Configuration: </h4> </summary> - Create or copy provided [.aider.conf.yml](./.aider.conf.yml) into your home directory (🐧`~/.aider.conf.yml`) oFix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.# The server scripts create a .env file.Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.<summary> <h4> ⚠️ Show Disclaimer </h4> </summary> - 🛡️ For automated workflows, always run AI agents in isolated environments: - Containers: 🐧 [daoch4n/waylaFix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.env_file: An optional specific path to a .env file to load.Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.logger.debug(f"Searching for .env files in and around: {repo_path}")Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.# Use port from args, then .env, then defaultFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.<summary> <h4> 🪪 Show Description </h4> </summary> - Just connect Roo to `mcp-devtools` server and code as usual but use `❓ Ask` mode instead of `💻 Code`, AI Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.environment variables from various locations (.aider.conf.yml, .env).Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.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 mcp-devtools@2.2.14 as of 7d ago. This is the package itself, not its dependencies.