pyobfus-mcp
PYPI · PYOBFUS-MCP · SCANNED SEP 20
Obfuscate Python before shipping; reverse-map tracebacks with your AI agent. No phone-home.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs setuptools.build_meta at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
- 0 of 35 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency48
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 13 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability69
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 685 tokens (~85/item across 8 items; 8 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
- Stability observed for 29 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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the pyobfus-mcp server?
pyobfus-mcp runs locally as a PyPI package, launched with uvx pyobfus-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · pyobfus-mcp
claude mcp add zhurong2020-pyobfus-mcp -- uvx pyobfus-mcp
{
"mcpServers": {
"zhurong2020-pyobfus-mcp": {
"command": "uvx",
"args": [
"pyobfus-mcp"
]
}
}
} {
"servers": {
"zhurong2020-pyobfus-mcp": {
"command": "uvx",
"args": [
"pyobfus-mcp"
]
}
}
} codex mcp add zhurong2020-pyobfus-mcp -- uvx pyobfus-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"zhurong2020-pyobfus-mcp": {
"type": "local",
"command": [
"uvx",
"pyobfus-mcp"
],
"enabled": true
}
}
} openclaw mcp add zhurong2020-pyobfus-mcp --command uvx --arg pyobfus-mcp
mcp_servers:
zhurong2020-pyobfus-mcp:
command: "uvx"
args: ["pyobfus-mcp"] {
"McpServers": {
"zhurong2020-pyobfus-mcp": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"pyobfus-mcp"
]
}
}
} assistant mcp add zhurong2020-pyobfus-mcp -t stdio -c uvx -a pyobfus-mcp
{
"mcpServers": {
"zhurong2020-pyobfus-mcp": {
"command": "uvx",
"args": [
"pyobfus-mcp"
]
}
}
} 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.
- 19 Sept 26 +16
- Malware scan: unverified → pass ▲ security
- 17 Sept 26 −17
- Malware scan: pass → unverified ▼ security
- Stability: pass → 0.87 functional
- 16 Sept 26 +1
- Stability: 0.97 → pass security
- 15 Sept 26 +15
- Malware scan: unverified → pass ▲ security
- 14 Sept 26 −14
- Malware scan: pass → unverified ▼ security
- 13 Sept 26 0
- Package version: 0.3.3 → 0.3.12 functional
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 −3
- Stability: pass → 0.83 functional
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 20 Sept 2026 · Analysed pypi/pyobfus-mcp@0.3.12
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | setuptools.build_meta |
Background: Why install scripts are a supply-chain risk →
Dependencies 35 packages
| Packages resolved | 35 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_obfuscation_risks ~180
Scan a Python project for patterns that may break obfuscation (eval/exec, dynamic attribute access, framework reflection, unsafe model loading). Returns severity counts, detected frameworks (FastAPI/Django/Flask/Pydantic/Click/SQLAlchemy/ML), and a suggested preset. Also locates requirements*.txt / pyproject.toml and, only if verify_dependencies_online=true, checks each declared dependency against public PyPI to flag AI-hallucinated ('slopsquatting') package names -- off by default, this tool makes no outbound network calls unless you opt in. By default the scan honors the project's pyobfus config; set use_project_config=false for the legacy config-free scan.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | – |
| use_project_config | boolean | – | – |
| verify_dependencies_online | boolean | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | object | yes | – |
No examples provided.
explain_preset ~60
Describe what a named preset changes: exclude names count, exclude patterns, preserve_param_names, docstring handling. For Pro presets, returns full pro_unlock metadata (trial command, checkout URL, price, money-back guarantee).
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | object | yes | – |
No examples provided.
generate_pyobfus_config ~70
Generate a pyobfus.yaml for a Python project. Auto-detects frameworks and applies the matching preset. By default returns the YAML text without writing to disk; set write=true to persist.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | – |
| preset_override | – | – | – |
| write | boolean | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | object | yes | – |
No examples provided.
list_presets ~28
List every pyobfus preset available, grouped by tier (community / framework-aware / Pro).
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | object | yes | – |
No examples provided.
protect_project ~158
One call to protect a Python project end-to-end AND verify it still works: scans risks, picks a framework-aware preset, obfuscates, then byte-compiles + import-smoke-tests the output in isolated subprocesses and returns verified:true/false. Writes a private de-obfuscation mapping alongside (not inside) the output. Use this when the user wants to 'protect/obfuscate before shipping' and expects a green check, not just a transform.
| Name | Type | Req | Description |
|---|---|---|---|
| output_dir | string | – | – |
| path | string | yes | – |
| preset | – | – | – |
| save_mapping | boolean | – | – |
| timeout | integer | – | – |
| trace_marker | boolean | – | – |
| verify | boolean | – | – |
| verify_cmd | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | object | yes | – |
No examples provided.
recommend_tier ~60
Analyze a Python project and recommend pyobfus tier (community vs Pro) with reasons. Combines a preflight scan with a sensitive-string-literal heuristic. Returns free_action and pro_action with concrete next-step commands.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | object | yes | – |
No examples provided.
start_pro_trial ~67
Return structured guidance for starting the 5-day pyobfus Pro trial. Does NOT invoke the side effect — the user runs `pyobfus-trial start` in their shell. Detects whether a trial is already active and surfaces the appropriate next step plus post-trial purchase URL.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | object | yes | – |
No examples provided.
unmap_stack_trace ~62
Reverse obfuscated identifiers in a stack trace using a pyobfus mapping.json. Accepts the trace as plain text and the path to a mapping file produced by --save-mapping.
| Name | Type | Req | Description |
|---|---|---|---|
| mapping_path | string | yes | – |
| trace | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | object | yes | – |
No examples provided.
What is the pyobfus-mcp server?
pyobfus-mcp is listed in the public MCP registry as io.github.zhurong2020/pyobfus-mcp. Obfuscate Python before shipping; reverse-map tracebacks with your AI agent. No phone-home. This page covers its PyPI package (pyobfus-mcp).
Is the pyobfus-mcp server safe to use?
pyobfus-mcp scores 81 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the pyobfus-mcp server expose?
pyobfus-mcp exposes 8 tools: protect_project, check_obfuscation_risks, generate_pyobfus_config, unmap_stack_trace, list_presets, and 3 more. Their descriptions and schemas cost roughly 685 tokens of context every time the server is loaded.
Is the pyobfus-mcp server still maintained?
pyobfus-mcp is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the pyobfus-mcp server under?
pyobfus-mcp declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.