god-prompt-mcp@1.1.1
VERIFIEDPublisher claims: "GodPrompt MCP server + portable Agent Skill for coding agents — TDD, debugging, verification gates, task routing, and progressive disclosure." 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
GITHUB_TOKENConfiguration, not credentials: GODPROMPT_FEEDBACK_FILE, XDG_STATE_HOME- Where it talks to
- no vendor host named in the code
- 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 GITHUB_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.
What changed since 1.0.45
vet-skills diff god-prompt-mcp 1.0.45 1.1.1This version reaches for something 1.0.45 did not: 1 new credential variable (GITHUB_TOKEN) · 2 new tools (create_work_contract, review_work_evidence). Compared from the two recorded runs, not from source.
- New credential variables
- GITHUB_TOKEN
- New tools
- create_work_contract, review_work_evidence
Tool descriptor hashes were not recorded for both runs; renamed or added tools are compared, rewritten descriptions are not.
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 80/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 · 30 s · 2 scenarios · 0 deviationsStatic findings
- [ ] All config via environment variables (.env file)Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.1. Open **Plugins**, select **+**, then **Add custom MCP server**. The current Plugins flow does **not** require Developer Mode.Fix: Keep SKILL.md to visible, descriptive text. Remove comments and encoded text that address the agent.- [ ] All config via environment variables (.env file)Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.### Fix Report FormatFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.### Fix Report FormatFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.### Commit Message FormatFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.- [ ] .env.example file with all required variablesFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.- [ ] .env.example file with all required variablesFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.1. Open **Plugins**, select **+**, then **Add custom MCP server**. The current Plugins flow does **not** require Developer Mode.Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.### Commit Message FormatFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.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.