Check every MCP server before Codex connects to it.
Sends your wallet private key over the network (index.js:215).
In Codex, the plugin stops a
codex mcp addof this version and tells you why.
It installs on a computer. Send yourself this page:
codex plugin marketplace add AgentAvow/AgentAvowcodex plugin add agentavow-trust@agentavowFree · No account · Paste into your terminal, start Codex, then choose Trust all and continue.
Or, from your phone:
Check a serverOn a computer? Paste these into your terminal, then start Codex. Free · No account.
codex plugin marketplace add AgentAvow/AgentAvowcodex plugin add agentavow-trust@agentavowEach answer has its reason, a signed 0-100 trust score and an adoption score, with a link to the full report.
How it works
When a session starts, and when Codex adds a server or installs a package, the plugin checks it with AgentAvow. Codex opens its first reply with one line, like this:
AgentAvow pre-check: checked 1 MCP server — 1 Safe, 0 Review. Ask for the AgentAvow pre-check for details.
✅ MCP 'deepwiki' (https://mcp.deepwiki.com/mcp): Safe to connect — tool definitions clean; server code not inspected · AgentAvow 74/100.
✅ dependency 'python-multipart' (pypi:python-multipart@>=0.0.7): Safe to connect · Certified — nothing found in 8 files · AgentAvow 90/100
Real output from Codex sessions, November 2026
Codex asks you to trust the plugin's hooks the first time, and again after each plugin update. The checks run only while the hooks are trusted; choose Trust all and continue, or trust them later with /hooks.
What it checks
- MCP servers in
~/.codex/config.tomland a trusted project's.codex/config.toml, at session start codex mcp add <name> --url …andcodex mcp add <name> -- <command>- Packages installed by name with npm, pnpm, yarn, bun, pip, uv, pipx or poetry, at the exact version you typed
- Your project's direct dependencies, a few at each session start. Those are already installed, so their answer is advice, never a stop
What it doesn't do
- The IDE extension doesn't run plugins. Add the connector there instead:
codex mcp add agentavow --url https://agentavow.com/mcp - Hooks run only while you trust them, and Codex asks again after each update
codex execskips hooks you haven't trusted, without a warning- Lockfile installs, requirements files and URL installs are left alone
- If AgentAvow can't be reached, your work carries on with no check
- A check can miss things. It stops a step only on Do not connect
One package, two versions.
gadgethumans-mcp 1.2.4 reads Safe to connect, 82/100. Version 1.0.15 is still on npm and reads Do not connect, 45/100: line 215 of its index.js sends the WALLET_PRIVATE_KEY environment variable to the vendor's API. A README or a teammate's config that pins @1.0.15 runs that code, so the plugin checks the version you typed, not the latest one. When Codex tries to add 1.0.15, the step stops:
$ codex mcp add gadget -- npx -y gadgethumans-mcp@1.0.15
AgentAvow checked this before it is added:
⛔ MCP 'gadget' (npm:gadgethumans-mcp@1.0.15): Do not connect — one critical finding in its code: wallet private key sent over the network · AgentAvow 45/100; sandbox: did not run (the sandbox has not observed this release), static analysis only. Report: https://agentavow.com/check/pkg/npm/gadgethumans-mcp?version=1.0.15
AgentAvow says: Do not connect, so it stopped this step (Codex cannot ask you first). If you reviewed the report and still want to add this server, run the same command yourself in your own terminal outside Codex, or switch AgentAvow's hooks off in Codex (/hooks) for this session. Do not retry it another way from here.
Real output of the plugin's Codex hook for this command, November 2026
The same command with @1.2.4 goes ahead. Reports: 1.0.15 · 1.2.4. Knostic wrote up this package's wallet-key behavior first, in September 2026.
No hooks? Use the connector.
The connector and the scan-before-connect skill check a tool when you ask, in the CLI, the IDE extension and the ChatGPT desktop app. Add the connector with one line:
codex mcp add agentavow --url https://agentavow.com/mcpThe skill and the config.toml setup are in the Codex setup guide →
Why developers can trust the answer
Each result is signed with Ed25519, and you can verify it offline against our public keys.
Our tool definition digest is in the TRACE spec as trace.mcp-tool-definition.v1.
An outside party reproduced our conformance vectors byte for byte in a Linux Foundation Decentralized Trust lab.
Our founder co-authors the action-ref Internet-Draft, an individual submission to the IETF.
Add it now.
codex plugin marketplace add AgentAvow/AgentAvowcodex plugin add agentavow-trust@agentavowNeeds the Codex CLI and python3. Remove it any time with codex plugin remove agentavow-trust@agentavow. Full setup: /docs/codex.
