Verfy
Config check

Check an MCP config in your browser

Paste the MCP config of your agent and see, for each server, what in the way it is started could hurt you. These are the rules verfy scan runs, in the same engine, on this page. Nothing is sent anywhere and no server is started.

What it checks

The config rules, the same as in the CLI
VFY-CFG-001mediumA package runner (npx, uvx, bunx, pipx, pnpm dlx) with no exact version: each start can download a different release, with different tools.
VFY-CFG-002highA remote server over plain http://, so anyone on the network can read or change tool calls.
VFY-CFG-003highA key or token written into the file (args, env, headers or the address). The value is never shown here.
VFY-CFG-004criticalA launch command that downloads a script and runs it in a shell (curl … | sh, iex).
VFY-CFG-005highA container started with --privileged, on the host network, or with the whole disk or home folder mounted.
VFY-CFG-006lowA server that is not behind the Verfy gateway, so its calls are not checked or receipted.
VFY-CFG-007infoA remote server with no credentials in the config: your client signs in with OAuth if the server asks, or the server is open to anyone.

Nothing leaves this page

  • The check runs in your browser with Verfy's JavaScript engine, the one the CLI's tests hold to the same results as the Python rules.
  • The config is not uploaded, stored or logged, and no MCP server is started.
  • A key in the config is reported by its kind, never by its value.

What it cannot see

  • Only how a server is started. The tools it serves are not looked at: verfy scan --live and verfy lock check do that on your machine.
  • An npx package that your project's own package.json lists is pinned by your lockfile; this page cannot see that file, so it may report one.
  • Codex CLI keeps its servers in TOML; check that file with verfy scan --discover.

Then fix it on your machine

The CLI finds every config on your computer and does the fixing: verfy setup puts each server behind the gateway (every call checked, with a signed receipt), and verfy lock pin writes exact versions. verfy setup --undo takes it out again.

pip install verfy
verfy scan --discover
verfy setup
verfy setup --write