pyobfus-mcp runs on your own machine — the client starts it, so there is no endpoint to ping. 1 223 installs a week from pypi. Last commit 2 Nov 2026.
9 local Python protection tools, delivery checks and traceback reverse mapping. No telemetry.
We read the source, 1 h ago · rules 995398eba69f
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
compile_proc = subprocess.run(
Found in continuous integration, deployment or infrastructure files, or in a neighbouring package of the same monorepo. None of this is installed when you add the server: it describes how the project is built and released. We list it because a leaked key in a build pipeline is still a real problem, but it is not something this server does on your machine.
"TracerPid, IsDebuggerPresent, timing skew (Pro).",
execFile(
const candidate = path.join(cwd, name);
code = marshal.loads(plaintext) # noqa: S302
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add pyobfus-mcp -- uvx pyobfus-mcp
{
"mcpServers": {
"pyobfus-mcp": {
"command": "uvx",
"args": [
"pyobfus-mcp"
]
}
}
}
[mcp_servers.pyobfus-mcp]
command = "uvx"
args = ["pyobfus-mcp"]
{
"mcpServers": {
"pyobfus-mcp": {
"command": "uvx",
"args": [
"pyobfus-mcp"
]
}
}
}
{
"servers": {
"pyobfus-mcp": {
"type": "stdio",
"command": "uvx",
"args": [
"pyobfus-mcp"
]
}
}
}
MCP server providing log snippet and Python traceback extraction tools.
Local MCP server for architectural decisions, traceability, and non-authoritative proposals.
High-resolution MCP tool call latency profiler and P50/P90/P95/P99 telemetry metrics collector
Local MCP proxy for tool restrictions, response redaction, audit logs, and database schema context.
30+ deterministic dev and delivery tools: linting, metrics, diagrams, model advice, AI-text checks.
Public DNS, HTTPS and deployment checks, plus offline email header and delivery-log tracing.
Transparent audit proxy for MCP servers: logs every tool call, flags poisoning and rug pulls.
Production telemetry for NestJS apps: traces, errors, regressions, jobs and alerts.
Answers built from our own checks of this server.