Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Python Code Validator

REMOTE · API.STATEMIND.AI · SCANNED AUG 8

Validates AI-generated Python: syntax, lint, security scan and deterministic repair.

Available components

61 Trust /100
Trust breakdown (6 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score →

Endpoint Security83
Transport & Reachability100
Schema Quality & AI Usability38
  • AI-judged instruction clarity (fair).Partial
  • Context-footprint check failed: tool/resource definitions use about 318 tokens (~318/item across 1 items; 1 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management3
  • Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · api.statemind.ai

# add to Claude Code
claude mcp add --transport http jkanselaar-python-code-validator https://api.statemind.ai/mcp
# ~/.codex/config.toml
[mcp_servers.jkanselaar-python-code-validator]
url = "https://api.statemind.ai/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "jkanselaar-python-code-validator": {
      "type": "remote",
      "url": "https://api.statemind.ai/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add jkanselaar-python-code-validator --url https://api.statemind.ai/mcp --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  jkanselaar-python-code-validator:
    url: "https://api.statemind.ai/mcp"
// mcp.json
{
  "mcpServers": {
    "jkanselaar-python-code-validator": {
      "type": "http",
      "url": "https://api.statemind.ai/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 8 Aug 26 0
    • Stability: unverified → 0.03 functional
  • 7 Aug 26 +28
    • Transport: unverified → pass security
    • Authorization: Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token. security
    • MCP protocol: unverified → fail functional
    • Tool coverage: unverified → 100 functional
    • First check of Tool coverage: 0 functional
    • First check of Schema quality: fair functional
    • First check of Schema quality: fail functional
    • First check of Tool coverage: 100 functional
    • First check of Schema quality: fail functional
  • 6 Aug 26 33

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 8 Aug 2026 · Probed https://api.statemind.ai/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=api.statemind.ai CN=YE1,O=Let's Encrypt,C=US 5 Aug 2026 3 Nov 2026 ECDSA 256 ECDSA-SHA384 643c1bc349e7cfb563219b2d9ceb51fa794
SANs: api.statemind.ai
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd
DNSSEC insecure

Validation of api.statemind.ai. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
ai. present 3799 8 Verified
statemind.ai. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Challenged, unverified

The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.

Result Challenged, unverified
Enforced On tool calls
HTTP status 200

WWW-Authenticate challenge Bearer realm="python-code-validator", error="invalid_token", error_description="POST /v1/keys for a free key"

Bearer realm="python-code-validator", error="invalid_token", error_description="POST /v1/keys for a free key"

Protected resource metadata

Retrieved No
Problem no_resource_metadata
Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://api.statemind.ai/mcp Verified 200
http (plaintext) http://api.statemind.ai/mcp HTTPS enforced 301 https://api.statemind.ai/mcp
MCP tools · 1 exposed · ~318 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.

Tool Tokens
python_code_validator ~318

Validates, repairs and hardens AI-generated Python: syntax and lint diagnostics, security scanning (bandit, AST policy, credential scan), deterministic auto-fixes and optimisation via SMIRE, optional sandboxed execution and Python-to-JavaScript transpilation. mode=static (default) never runs the submitted code: it parses it, lints it (ruff), type-checks it (mypy), applies an AST security policy and scans for credentials. mode=repair adds deterministic fixes and returns the rewritten source in fixed_code, keeping the original when it cannot prove the fix. mode=execute additionally runs the code in a container sandbox — no network, read-only filesystem, killed at options.timeout_s — and reports its exit code, stdout and stderr; treat that as a side effect and do not submit code you do not want executed. Auth: a key is required for every call and static is free (100 calls per day, then HTTP 429); repair, execute need a paid key and answer 402 without one. Nothing outside the sandbox is written, and the code plus its verdict are retained to improve the service. Returns valid, score 0..1, diagnostics (rule, message, line, column), security findings, fixes, fixed_code and runtime; see outputSchema. Use it on Python you generated or edited before writing it to disk, and prefer static unless you need the fix or proof that it runs.

NameTypeReqDescription
codestringyes
language
mode
options
NameTypeReqDescription
diagnosticsarray
fixed_code
fixesarray
metayes
runtime
scorenumberyes
securityarray
transpiled
validbooleanyes

No examples provided.