io.github.zhurong2020/pyobfus-mcp
pyobfus-mcp
Is the pyobfus- MCP server down? No. It answered initialize and tools/list in the probe of 2026-10-30.
9 local Python protection tools, delivery checks and traceback reverse mapping. No telemetry.
alive probed 2026-11-15 · unchanged since 2026-10-30
- Run it
- uvx pyobfus-mcp@0.3.17 (stdio, probed in a container with the network off)
- Host
- pypi.org
- Reports itself as
- pyobfus 0.3.17
- Capabilities
- prompts, resources, tools
- Instructions
- none
- Of a 1M window
- 0.2 % of a 1M context window
- Count
- 2.2k tokens in Claude Opus 5.5, exact, measured 2026-10-26. With the Claude Code prefix mcp__…__ on each tool name: 2.3k. The o200k_base estimate is 1.2k. Counted again when the tool definitions change. Method.
- Repository
- https://github.com/zhurong2020/pyobfus
- Registry
- active, updated 2026-10-30 · registry entry
- Changes
- 2 recorded, reachable in 2 of them. A row is added when the result, the tool count or the cost changes.
Most expensive tools
The Claude column scales the o200k estimate of each tool by this server's ratio of exact to estimate, 1.81×.
| Tool | ≈ Claude tokens | o200k estimate | Share of this server |
|---|---|---|---|
| protect_project | 479 | 265 | 22 % |
| check_obfuscation_risks | 405 | 224 | 19 % |
| check_delivery | 331 | 183 | 15 % |
| generate_pyobfus_config | 220 | 122 | 10 % |
| unmap_stack_trace | 172 | 95 | 8 % |
Compare this server with others.
More servers
Other registry entries on pypi.org, the ones next to this name; all of them.
- io.github.zhaoxinghua09-cell/uibc-core · alive
- LLM Usage io.github.zhaoyue722/llm-usage-mcp · alive
- io.github.zhongweili/nanobanana-mcp-server · not found
- AutoClip io.github.zhouxiaoka/autoclip-mcp · alive
- backlink-guard io.github.zhuyansen/backlink-guard · needs args
- New-Term Radar io.github.zhuyansen/new-term-radar · crashed on start
- GitHub Release MCP io.github.zishuowang696/gh-release-mcp · alive
- io.github.zlatkoc/youtube-summarize · alive
Servers that mention protection or telemetry.
- FairMind Project Context ai.fairmind/project-context · needs auth
- ai.getvda/llm-orchestration-agent-opentelemetry-api · newer protocol
- ai.getvda/llm-orchestration-agent-opentelemetry-instrumentation-fastapi · newer protocol
- ai.getvda/traced-openai-langchain-agent · newer protocol
- Auth Posture — Email Deliverability & Spoofability Audit app.rowb.auth-posture/audit · alive
- bot.402/discovery-oracle · timeout
- Atlasemoji com.atlasemoji/mcp · alive
- Breach402 — Email Data-Breach Check com.bmcxiv/breach402-owner-protection · alive
History
We add a row when the result changes. A server with no change keeps its last row.
| Probed | Result | Init | Tools | Claude | o200k |
|---|---|---|---|---|---|
| 2026-10-26 07:07 | alive | 3.3 s | 9 | 2.2k | 1.2k |
| 2026-10-20 06:46 | alive | 2.2 s | 9 | 1.2k |
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- The server answers initialize and tools/list. Nothing to fix.