pyobfus-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| protect_projectA | 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. |
| check_obfuscation_risksA | 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. |
| generate_pyobfus_configA | 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. |
| unmap_stack_traceA | 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. |
| list_presetsA | List every pyobfus preset available, grouped by tier (community / framework-aware / Pro). |
| explain_presetA | 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). |
| recommend_tierB | 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. |
| start_pro_trialA | Return structured guidance for starting the 5-day pyobfus Pro trial. Does NOT invoke the side effect — the user runs |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
Most tools target distinct actions: listing presets, explaining presets, generating configs, protecting projects, recommending tiers, starting trials, and unmapping traces. Some overlap exists between check_obfuscation_risks and recommend_tier, and between generate_pyobfus_config and protect_project, but their descriptions clarify different purposes.
All tool names follow a consistent verb-first snake_case pattern: list_, explain_, generate_, protect_, recommend_, start_, unmap_. This makes the tool set predictable and easy for an agent to navigate.
Eight tools is well-scoped for a Python obfuscation helper server. Each tool covers a meaningful part of the workflow without unnecessary redundancy or feature bloat.
The tool set covers the main pyobfus workflows: preset discovery, risk assessment, config generation, project protection with verification, tier recommendation, trial guidance, and stack trace unmapping. Minor gaps exist such as no standalone obfuscate-only tool or direct deobfuscation path, but core usage is well covered.