Python Code Validator README
The full upstream README, mirrored here for reference. Install config, tool schemas, adoption signals, and an original overview live on the Python Code Validator listing page.
Python Code Validator
An MCP server that validates, repairs and runs Python against the examples it
is supposed to satisfy — validate_python, repair_python and execute_python
over HTTP at https://api.statemind.ai/mcp, with a free key and no account.
A hosted service that proves AI-generated Python does what you asked. State the
intent — assertions or doctest lines — and the code is run against it inside a
container with no network and a read-only filesystem; a fix comes back only when
every example passes. On the QuixBugs defects that is 41% repaired and 77%
refused as not doing what they say, with no false alarms on the corrected
programs — where ruff and mypy flag the defect in none of them
(the numbers).
The checks that need no intent come with it: syntax and lint diagnostics, an AST
security policy that also catches calls hidden behind dynamic imports and runtime
attribute lookups, a bandit pass, a credential scan and deterministic repair —
one verdict with a score. Asking the same question twice inside ten minutes is
answered from the first answer and costs nothing (x-msvc-repeat: 1).
This repository holds the client side: the MCP configuration, the CI script and
the pre-commit hook. The service itself runs at https://api.statemind.ai, so
there is nothing to install or host.
A key, without an account
25 static checks a day, metered per UTC day, and a few keys per address: enough
to try it and to run it over a small project, not a supply. Every answer carries
the state of the allowance (x-quota-remaining, x-quota-reset), so a client
can back off before it is cut off.
MCP
Registered in the official MCP registry as
ai.statemind/python-code-validator, a name verified against the domain that
serves it rather than a GitHub account. Any MCP client adds it with one
block:
- Claude Code:
claude mcp add --transport http python-code-validator https://api.statemind.ai/mcp --header "Authorization: Bearer msvc_free_…" - Cursor:
~/.cursor/mcp.json, same block. - VS Code / Copilot:
.vscode/mcp.jsonunder"servers".
A client that only launches a command uses the stdio bridge in this repository instead, which forwards the same tool over HTTPS:
Or as a container, which the Dockerfile here builds:
Gemini CLI installs the same bridge as an extension, with the instruction file that makes it get used:
Three tools, named after what they do to the code:
| tool | runs the code | key |
|---|---|---|
validate_python | no | free |
repair_python — also returns fixed_code | no | paid |
execute_python — also runs it in a sandbox | yes | paid |
The old single python_code_validator tool, with its mode argument, still
answers for clients that already configured it, but is no longer listed.
Saying what the code was supposed to do
Every check above passes on a function that computes the wrong answer. The one thing that catches it is the intent, and the agent that asked for the code is the only one who has it — so pass it along:
Doctest lines (>>> bitcount(127) then 7) work the same way, as do >>>
examples already written in the source. execute_python runs them in the
sandbox: one that does not hold is a python:example-mismatch error, and the
repair search returns a fix only when every example passes. On the QuixBugs
defect set — real bugs, hidden test inputs deciding correctness — that repairs
41% and refuses 77% as not doing what they say, with no false alarms on the
corrected programs.
Repeating a call costs nothing: the same key asking the same question — same
mode, same code, same examples — is answered from the answer it already got,
marked x-msvc-repeat: 1, so an agent that checks its work at every step is not
billed for verdicts that cannot have changed.
Claude Code plugin
An instruction can be ignored; a hook cannot. The plugin checks every Python file Claude Code writes or edits, in the turn it was written, and hands the errors back to the model instead of to you:
Nothing to configure: it mints and keeps its own free key on first use. A file that comes back accepted is silent, a rejected one stops the turn with the offending lines named, and an identical file is not asked about twice. It never ends a session over its own trouble — an unreachable service or a spent allowance lets the turn continue, and the allowance says how to raise it.
Set VALIDATOR_API_KEY to use a paid key instead of the free tier, and
VALIDATOR_URL to point at your own deployment. The plugin also carries the
validate-python skill, for the part a hook cannot do: stating the intent as
examples and running the code against them.
Cursor hook
The same script, wired to Cursor's postToolUse, where the verdict comes back
as context on the conversation instead of as an exit code:
Project hooks run from the project root, which is why the command in
cursor/hooks.json is a path relative to it. For a hook
that applies to every project instead, put the script in ~/.cursor/hooks/ and
the same block in ~/.cursor/hooks.json with the command
python3 ./hooks/validate_written.py --cursor.
Making the agent use it
Configuring the server is not what gets it called: the instruction file is.
AGENTS.md in this repository is that text, written to be dropped
into any project under whichever name the client reads:
Cursor reads rules with front matter instead, so that one is a separate file —
copy .cursor/rules/python-code-validator.mdc
into .cursor/rules/ of the project.
The short version, if you would rather add a line to instructions you already have:
Write what the code should do as
assertexamples before writing the code, and pass them inoptions.examples. Callvalidate_pythonafter every edit andexecute_pythononce a function is finished, not again until what it does has changed. When a call returnsfixed_code, take it — the service ran it against your examples. Do not present code that came backvalid: false.
CI
The service hands out the client, so a workflow needs no checkout of this repository and no secret:
Or as an action, from the Marketplace:
The changed Python is validated and offending lines are annotated on the diff, failing the job on syntax errors and unsafe patterns. Files the service refuses outright (over its 200 kB limit) are skipped with a warning rather than failing the run.
The run also leaves one comment on the pull request, edited in place on later
pushes rather than repeated: what was accepted, what was repaired and how much of
the day's allowance is left. Without pull-requests: write nothing is written
and the job is unaffected; comment: "false" turns it off.
On the free tier the action keeps its key in the workflow cache, one per
repository per day, so the allowance belongs to the repository rather than to the
run. With api-key set the cache is skipped.
Pre-commit
The client itself
validate.py is standard library only, so it also works as python validate.py file.py in a Makefile, a git hook or a container:
VALIDATOR_API_KEY is used when set; otherwise the client mints a free key —
keeping it in VALIDATOR_KEY_FILE when that names a path, which is how a series
of runs shares one allowance. VALIDATOR_URL points it at another deployment.
VALIDATOR_SOURCE names the caller, which is only ever counted: a run inside a
workflow says github-action by itself.
The badge
A repository whose Python is checked on every pull request can say so:
HTTP
mode is static, repair or execute; repair and execute need a
configured key. Submitted code is not logged.
A refused call says what to do about it, so a caller with no operator to ask can resolve it itself:
Paying for calls
A free key covers 25 static checks a day, and one address gets a few keys a day, so the allowance is a trial rather than a supply. Beyond it a key carries credits: a static check costs 1, a repair 3 and a sandboxed run 10, and an identical call repeated within ten minutes is answered from the first one for free.
Credits are bought with a card, without an invoice or anyone to ask:
That answers with a Stripe Checkout page; the credits are on the key seconds
after the card clears (500 credits is €10). An agent with a Gnosis wallet can
instead pay in xDAI without a browser — GET /v1/pricing states both routes.
Examples
examples/ holds three files and the client to send them with: one
that passes every check and still returns the wrong number, one the security
policy refuses, and one that comes back accepted from the sandbox.
Licence
MIT.