mcp-server@3.24.0
VERIFIEDPublisher claims: "Approve plans, track initiatives and work items, and steer AI engineering crews in AnyForge." 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
ANYFORGE_API_TOKENConfiguration, not credentials: ANYFORGE_API_URL- Where it talks to
- anyforge.ai (its own)
- What we saw when it ran
- 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 ANYFORGE_API_TOKEN and talks to anyforge.ai. 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.
What changed since 3.23.0
vet-skills diff mcp-server 3.23.0 3.24.0This version reaches for something 3.23.0 did not: 1 rewritten tool descriptor (anyforge_update_work_item). Compared from the two recorded runs, not from source.
- Rewritten tool descriptors
- anyforge_update_work_item
The guard can hold an update like this until someone approves it (runtime.on_change: hold). A change that only shows with a real credential, or on a path the run did not reach, is not in a trace and so not in this comparison.
Is [email protected] safe to install?
KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios) on 2026-11-20 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 · 25 s · 2 scenarios · 0 deviationsStatic findings
…tore()}:{},...Gt(e)},...r!==void 0?{body:JSON.stringify(r)}:{}}),u;try{u=await m.json()}catch{throw new f("invalid_response",m.status,`non-JSON response from ${p}`)}if(!m.ok||u.ok===!1)throw Jt(u,m.status);return u.data}function Jt(e,t){le…Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.…eads the repo tree for a checked-in coverage report (lcov.info, coverage-summary.json, cobertura, clover) and records the parsed %, so a repo that publishes coverage in git shows a number without a crew run or a manual upload. Runs in the …Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.…ndpoint:t||r.endpoint||Bt};throw new Error("No AnyForge credentials found. Run `npx @anyforge/control init` to authorise this machine, or set ANYFORGE_API_TOKEN (and optionally ANYF…Fix: Pin versions and sources; vendor anything fetched at install time.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
Not checked against OSV yet; the weekly check has not reached this version.