GxP Gateway Audit

● Active

io.github.antonio-castellon/mcp-glp-audit-proxy

Audits MCP and HTTPS calls. Tamper-evident trail for GLP.

Connect this server

One click to install, or copy the config below. Suits: Claude Desktop · Cursor.

Add to Cursor Add to VS CodeClaude Desktop / Claude Code: paste the config below.

Or add it manually — claude_desktop_config.json (Claude Desktop) or .cursor/mcp.json (Cursor):

{
  "mcpServers": {
    "mcp-glp-audit-proxy": {
      "command": "uvx",
      "args": [
        "mcp-glp-audit-proxy"
      ],
      "env": {
        "GLP_CONFIG": "<your GLP_CONFIG>",
        "GLP_PRINCIPAL_ID": "<your GLP_PRINCIPAL_ID>",
        "GLP_PRINCIPAL_NAME": "<your GLP_PRINCIPAL_NAME>",
        "GLP_PRINCIPAL_ROLE": "<your GLP_PRINCIPAL_ROLE>"
      }
    }
  }
}
One line, from the terminal
Claude Code
claude mcp add --env GLP_CONFIG='<your GLP_CONFIG>' --env GLP_PRINCIPAL_ID='<your GLP_PRINCIPAL_ID>' --env GLP_PRINCIPAL_NAME='<your GLP_PRINCIPAL_NAME>' --env GLP_PRINCIPAL_ROLE='<your GLP_PRINCIPAL_ROLE>' --transport stdio mcp-glp-audit-proxy -- uvx mcp-glp-audit-proxy
OpenAI Codex CLI
codex mcp add mcp-glp-audit-proxy --env GLP_CONFIG='<your GLP_CONFIG>' --env GLP_PRINCIPAL_ID='<your GLP_PRINCIPAL_ID>' --env GLP_PRINCIPAL_NAME='<your GLP_PRINCIPAL_NAME>' --env GLP_PRINCIPAL_ROLE='<your GLP_PRINCIPAL_ROLE>' -- uvx mcp-glp-audit-proxy
VS Code
code --add-mcp '{"name":"mcp-glp-audit-proxy","type":"stdio","command":"uvx","args":["mcp-glp-audit-proxy"],"env":{"GLP_CONFIG":"<your GLP_CONFIG>","GLP_PRINCIPAL_ID":"<your GLP_PRINCIPAL_ID>","GLP_PRINCIPAL_NAME":"<your GLP_PRINCIPAL_NAME>","GLP_PRINCIPAL_ROLE":"<your GLP_PRINCIPAL_ROLE>"}}'

Syntax from each client's docs (Claude Code: claude mcp add; Codex: codex mcp add; VS Code: code --add-mcp). Placeholders in angle brackets are values you fill in.

Environment variables
  • GLP_CONFIGrequiredPath to the proxy JSON config (upstreams, policy, audit file).
  • GLP_PRINCIPAL_IDrequiredAuthenticated human id for this process. Stdio identity comes from the environment.
  • GLP_PRINCIPAL_NAMErequiredPrinted name of the human principal.
  • GLP_PRINCIPAL_ROLErequiredOne of operator, approver, qa, admin.

A starting point — check the repository for exact arguments and setup. Restart your client after editing the config.

Category
APIs & Integrations
Version
0.4.0
Registry
active
Published
10/25/2026
Listed in:Official MCP registry ↗how this is checked

Is it safe? Is it maintained?

Serverdex check: Nov 17, 2026

Looks healthy: GxP Gateway Audit is maintained, open source.

Maintained
Active
Last commit 5 days ago (Nov 17, 2026), 0 open issues.
Official registry
Active
Published as io.github.antonio-castellon/mcp-glp-audit-proxy in the official MCP registry, version 0.4.0.
Source
Open source, MIT
Public repository under the MIT licence, 0 stars, 0 forks.
Runs
On your machine
A local PyPI package started by your client; it can reach whatever your user account can.
Credentials
4 required
Declared environment variables: GLP_CONFIG, GLP_PRINCIPAL_ID, GLP_PRINCIPAL_NAME, GLP_PRINCIPAL_ROLE. They stay on your machine; the config on this page shows where each goes.
Owner
Unclaimed
Nobody has claimed this page yet; the data above comes from the registry, GitHub and the live check.

Facts only: last commit and licence from GitHub, the entry's status from the official registry, credentials from the live check. Not a code audit — run the security scan on the endpoint yourself.

On GitHub

read Nov 17, 2026
Stars
0
Forks
0
Last push
Nov 17, 2026
License
MIT

Python

From the README

mcp-name: io.github.antonio-castellon/mcp-glp-audit-proxy mcp-glp-audit-proxy GxP Gateway Audit (package mcp-glp-audit-proxy) audits MCP and HTTP(S) APIs, gateways, and LLM endpoints. Community edition, v0.4.0. The package name, the command names, and the MCP Registry id stay mcp-glp-audit-proxy. Changes since 0.2.0 are in CHANGELOG.md. The listener and every remote URL are HTTPS with TLS 1.3. Plain HTTP is refused. With no listen object the process is still the stdio MCP proxy between a host and its MCP servers. It is designed to support GLP / 21 CFR Part 11 / EU GMP Annex 11 workflows. Data stays on the customer's infrastructure. This package is the open core. Signed checkpoints, WORM storage, PDF/CSV reports, the IQ/OQ pack and SSO/OAuth are Pro features and are not in this repository. Personal Part 11 e-signatures are out of scope. Community is tamper-evident via the hash chain. It is not signed. Signing is Pro. Install Requires Python 3.11 or newer. From a checkout: The mcp dependency is pinned to >=2.2.0, =1.8.0, =2.0.0, entryhash= . Copy that line into a ticket, an email or a LIMS record. Check it later with --expect-head : or --expect-head-file (the file may hold that same line). The command exits 1 when the chain tip differs. The sidecar data/audit.jsonl.head makes a cut of whole trailing lines fail verification. Someone who can edit both the log and the sidecar can move them together; the external copy is the control. Community is tamper-evident via the hash chain.…

Read the full README on GitHub →

The most-starred APIs & Integrations servers in the index, with their live-check result.

ServerStarsLast pushLive check
OpenWork MCP Gateway24,576Nov 2026Needs sign-in
API Anything3,699Nov 2026Local / not checked
GoModel1,322Nov 2026Local / not checked
Scaleway MCP server1,027Nov 2026Local / not checked
AnythingMCP817Nov 2026Needs sign-in

GxP Gateway Audit: questions people ask

Is GxP Gateway Audit a remote or a local MCP server?
According to its entry in the official MCP registry, GxP Gateway Audit ships as a local package (PyPI) that your client starts on your machine.
Does GxP Gateway Audit need an API key?
Its registry entry declares 4 required environment variables: GLP_CONFIG, GLP_PRINCIPAL_ID, GLP_PRINCIPAL_NAME, GLP_PRINCIPAL_ROLE. The config on this page shows where each goes.
Is GxP Gateway Audit safe to use?
Looks healthy: GxP Gateway Audit is maintained, open source. In detail — maintained: Active; official registry: Active; source: Open source, MIT; runs: On your machine; credentials: 4 required. Serverdex check of Nov 17, 2026. This is a reading of the repository, the registry entry and the live check, not a code audit; run the Serverdex security scan on the endpoint before trusting it with real data.
Is GxP Gateway Audit still maintained?
Active: the repository's last commit 5 days ago. Last push Nov 17, 2026, 0 GitHub stars, MIT licence. Read from GitHub on Nov 17, 2026.
How do I add GxP Gateway Audit to Claude, Cursor or VS Code?
Copy the config in "Connect this server" into your client's MCP config file (claude_desktop_config.json, ~/.cursor/mcp.json or .vscode/mcp.json), or use the one-click Add to Cursor / Add to VS Code buttons and the one-line commands for Claude Code and Codex; then restart the client.

More from antonio-castellon

All 2 servers by antonio-castellon →
  1. Telegram BridgeStdio MCP bridge to Telegram with scrubbing and a fail-closed allowlist.
  2. Advanced ExcelNormalize messy lab Excel and CSV exports into structured tables.
Browse all APIs & Integrations →

Add the badge to your site

Show visitors that GxP Gateway Audit is listed here — it’s also the link we check for a free listing.

GxP Gateway Audit — listed on Serverdex

HTML — for your website

<a href="https://serverdex.io/server/io-github-antonio-castellon-mcp-glp-audit-proxy?utm_source=badge"><img src="https://serverdex.io/brand/badge.svg" alt="GxP Gateway Audit — listed on Serverdex" width="123" height="40" loading="lazy"></a>

Recommended. A dofollow link from your own domain is the one that counts for search engines, and it's the link we check for a free listing.

Markdown — for your README

[![GxP Gateway Audit — listed on Serverdex](https://serverdex.io/brand/badge.svg)](https://serverdex.io/server/io-github-antonio-castellon-mcp-glp-audit-proxy?utm_source=badge)

Nice for visibility, but GitHub marks README links nofollow, so it doesn't pass authority. Use the HTML badge on your site as well.

Add to CursorAdd to VS CodeOpen in Claude Code

Install buttons — for your README

[![Add to Cursor](https://serverdex.io/brand/install-cursor.svg)](https://serverdex.io/install/cursor/io-github-antonio-castellon-mcp-glp-audit-proxy) [![Add to VS Code](https://serverdex.io/brand/install-vscode.svg)](https://serverdex.io/install/vscode/io-github-antonio-castellon-mcp-glp-audit-proxy) [![Open in Claude Code](https://serverdex.io/brand/install-claude-code.svg)](https://serverdex.io/install/claude-code/io-github-antonio-castellon-mcp-glp-audit-proxy)

One click opens Cursor or VS Code with this server's config prefilled; the Claude Code button lands on the one-line command. The links point at Serverdex, so when your config changes the buttons keep working.

Install buttons — HTML for your docs

<a href="https://serverdex.io/install/cursor/io-github-antonio-castellon-mcp-glp-audit-proxy"><img src="https://serverdex.io/brand/install-cursor.svg" alt="Add to Cursor — via Serverdex" width="140" height="28"></a>
<a href="https://serverdex.io/install/vscode/io-github-antonio-castellon-mcp-glp-audit-proxy"><img src="https://serverdex.io/brand/install-vscode.svg" alt="Add to VS Code — via Serverdex" width="147" height="28"></a>
<a href="https://serverdex.io/install/claude-code/io-github-antonio-castellon-mcp-glp-audit-proxy"><img src="https://serverdex.io/brand/install-claude-code.svg" alt="Open in Claude Code — via Serverdex" width="180" height="28"></a>

Same buttons as plain links for a docs page or website.

Prefer a live badge with the score, stars and live check? Score badge (links to a page that explains the number and back to this listing).