autocodeflow-mcp-server@2.2.0
VERIFIEDPublisher claims: "MCP server for AutoCodeFlow — lets AI agents (Claude, Cursor, etc.) manage tasks and executions" Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Started with a decoy AUTOCODEFLOW_API_TOKEN; tool list observed. Tool calls with a real credential not tested.- Tested
- server startup with a tagged decoy in AUTOCODEFLOW_API_TOKEN · MCP initialize and tools/list · every tool description, for hidden instructions · where the decoy credential went · every file read, file written and host contacted by what ran
- Not tested
- what the tools do when called with a real credential
- Needs
- AUTOCODEFLOW_API_TOKEN — give it to the server where it runs, through vet-skills run --secrets, so the value never enters the server's environment. Never paste a credential into a chat, a ticket or a report.
Before you give it your token
- It will ask for
AUTOCODEFLOW_API_REFRESH_TOKENAUTOCODEFLOW_API_TOKENConfiguration, not credentials: AUTOCODEFLOW_API_URL, VITEST- 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 a real credential
Connect it with a scoped credential, under the guard. It asks for AUTOCODEFLOW_API_REFRESH_TOKEN, AUTOCODEFLOW_API_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-09 and scored it 92/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 · 55 s · 2 scenarios · 0 deviationsStatic findings
…TION .nullable() .optional() .describe('Timeout action: kill (default — executor kills the process tree) | kill_retry (kill + re-enqueue once…Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.No other findings across 4,071 lines in 40 files.
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 autocodeflow-mcp-server@2.2.0 as of 5d ago. This is the package itself, not its dependencies.