GLP Audit Proxy runs on your own machine — the client starts it, so there is no endpoint to ping. 1 465 installs a week from pypi. Last commit 22 Oct 2026.
Local MCP proxy with a tamper-evident audit trail for GLP traceability.
What the code does
We read the source, 50 min 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.
completed = subprocess.run( # noqa: S603 # nosec B603
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
This code can reach further than it looks
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.
Connect this server
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 mcp-glp-audit-proxy -e 'GLP_CONFIG=<GLP_CONFIG>' -e 'GLP_PRINCIPAL_ID=<GLP_PRINCIPAL_ID>' -e 'GLP_PRINCIPAL_NAME=<GLP_PRINCIPAL_NAME>' -e 'GLP_PRINCIPAL_ROLE=<GLP_PRINCIPAL_ROLE>' -- uvx mcp-glp-audit-proxy{
"mcpServers": {
"mcp-glp-audit-proxy": {
"command": "uvx",
"args": [
"mcp-glp-audit-proxy"
],
"env": {
"GLP_CONFIG": "<GLP_CONFIG>",
"GLP_PRINCIPAL_ID": "<GLP_PRINCIPAL_ID>",
"GLP_PRINCIPAL_NAME": "<GLP_PRINCIPAL_NAME>",
"GLP_PRINCIPAL_ROLE": "<GLP_PRINCIPAL_ROLE>"
}
}
}
}[mcp_servers.mcp-glp-audit-proxy]
command = "uvx"
args = ["mcp-glp-audit-proxy"]
env = { GLP_CONFIG = "<GLP_CONFIG>", GLP_PRINCIPAL_ID = "<GLP_PRINCIPAL_ID>", GLP_PRINCIPAL_NAME = "<GLP_PRINCIPAL_NAME>", GLP_PRINCIPAL_ROLE = "<GLP_PRINCIPAL_ROLE>" }{
"mcpServers": {
"mcp-glp-audit-proxy": {
"command": "uvx",
"args": [
"mcp-glp-audit-proxy"
],
"env": {
"GLP_CONFIG": "<GLP_CONFIG>",
"GLP_PRINCIPAL_ID": "<GLP_PRINCIPAL_ID>",
"GLP_PRINCIPAL_NAME": "<GLP_PRINCIPAL_NAME>",
"GLP_PRINCIPAL_ROLE": "<GLP_PRINCIPAL_ROLE>"
}
}
}
}{
"servers": {
"mcp-glp-audit-proxy": {
"type": "stdio",
"command": "uvx",
"args": [
"mcp-glp-audit-proxy"
],
"env": {
"GLP_CONFIG": "<GLP_CONFIG>",
"GLP_PRINCIPAL_ID": "<GLP_PRINCIPAL_ID>",
"GLP_PRINCIPAL_NAME": "<GLP_PRINCIPAL_NAME>",
"GLP_PRINCIPAL_ROLE": "<GLP_PRINCIPAL_ROLE>"
}
}
}
}Put your own values in place of
<GLP_CONFIG> (Path to the proxy JSON config (upstreams, policy, audit file)), <GLP_PRINCIPAL_ID> (Authenticated human id for this process. Stdio identity comes from the environment), <GLP_PRINCIPAL_NAME> (Printed name of the human principal), <GLP_PRINCIPAL_ROLE> (One of operator, approver, qa, admin).
The author’s registry entry marks them as required.
Alternatives to GLP Audit Proxy
same job, measured the same wayAudit trail and traceability for AI agents. MCP gate: evaluate, ingest, request approval.
BYOK Reddit/YouTube research CLI with a tamper-evident audit log and an MCP server.
Pre-execution gate for AI-agent tool calls. Touch ID approval. Tamper-evident audit log.
Commit-time policy checks for AI agent writes (ALLOW/DENY/STEP_UP) with a tamper-evident audit log.
Commit-time policy checks for AI agent writes (ALLOW/DENY/STEP_UP) with a tamper-evident audit log.
Local MCP server for architectural decisions, traceability, and non-authoritative proposals.
Tamper-evident proof creation and verification for AI agents via MCP, A2A, and REST.
Transparent audit proxy for MCP servers: logs every tool call, flags poisoning and rug pulls.
GLP Audit Proxy — questions
Answers built from our own checks of this server.