World Monitor
Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 100 tools.
Audits MCP and HTTPS calls. Tamper-evident trail for GLP.
列表按使用分(满分 100)排序,由以下部分组成
| 热度 | 0/80 | GitHub 星标或每周下载量:较大的计 60,较小的计 20 |
|---|---|---|
| 新鲜度 | 12/12 | 30 天内有发布或代码更新得满分 |
| 仍在响应 | 0/8 | 上次检查时云端端点有响应 |
| 使用分 | 12/100 |
质量: 基础检查通过 3/3 项(仅展示,不用于排序) · 上升势头: 暂无数据 (只用于“上升中”标签)
选择你使用的 AI 应用,然后复制设置。
用一句话让 AI 帮你安装
请帮我安装 GxP Gateway Audit。按照 https://mcp.popnx.com/i/antonio-castellon-mcp-glp-audit-proxy.md 操作,先把命令给我看,等我同意后再运行。粘贴到能在你电脑上工作的 AI(如 Claude Code、Cursor)。它会读取我们的步骤,先给你看命令,等你同意。无需密钥,无需注册。 · 查看 AI 会读取的全文
通过 3/3 项检查 · 在你的电脑上运行 · ✓ 命令已检查 2026年11月13日
第一步:你用哪个 AI?
选择你用的应用,步骤会显示在下方。
可连接 Claude,但需要先准备
需要填写 4 项设置(GLP_CONFIG, GLP_PRINCIPAL_ID, GLP_PRINCIPAL_NAME, GLP_PRINCIPAL_ROLE) · 需要先在电脑上安装 Python (uv)(只需一次) · 仅限电脑上的 Claude 应用(Windows 或 Mac),网页和手机不可用
把这段话复制到 Claude 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。
请在这台电脑上为 Claude 安装 MCP server GxP Gateway Audit,按顺序:1) 用 uv --version 检查是否有 uv。没有的话,请让我从 https://docs.astral.sh/uv/getting-started/installation/ 安装,不要自己安装。2) 只使用这份配置(已通过 PopNx MCP 检查):{ "mcpServers": { "glp-audit-proxy": { "command": "uvx", "args": [ "mcp-glp-audit-proxy" ], "env": { "GLP_CONFIG": "your-value", "GLP_PRINCIPAL_ID": "your-value", "GLP_PRINCIPAL_NAME": "your-value", "GLP_PRINCIPAL_ROLE": "your-value" } } } } 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) GLP_CONFIG, GLP_PRINCIPAL_ID, GLP_PRINCIPAL_NAME, GLP_PRINCIPAL_ROLE 先保留 "your-value",请我自己把真实值粘贴到文件或应用的输入框里。不要让我在对话里输入密钥。5) 按约定执行,然后确认 GxP Gateway Audit 的工具真的出现了。这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。
已经装好了吗?先检查 · 打开终端,输入这条命令后按 Enter
uv --versionMac:按 ⌘ + Space,输入 Terminal 后按 Enter
Windows:打开“开始”菜单,输入 Windows PowerShell,然后选“打开”
还没安装: uv 没有点选式安装程序。从 uv 官方页面复制适合你系统(macOS 或 Windows)的一行命令,粘贴到终端 · 不需要单独安装 Python,uv 会在需要时自动下载
装好后关掉终端再打开,重新运行同一条命令,应显示版本号: uv --version
安装一次,所有需要 uv 的工具都能用
这些是程序设置,不是密钥,无需注册。按开发者的说明填写。
GLP_CONFIG 代理 JSON 配置文件的路径(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 operator、approver、qa、admin 之一。 说明为自动翻译,变量名保持原样;不确定时请查看原文。
SettingsDeveloperEdit Config
{
"mcpServers": {
"glp-audit-proxy": {
"command": "uvx",
"args": [
"mcp-glp-audit-proxy"
],
"env": {
"GLP_CONFIG": "your-value",
"GLP_PRINCIPAL_ID": "your-value",
"GLP_PRINCIPAL_NAME": "your-value",
"GLP_PRINCIPAL_ROLE": "your-value"
}
}
}
}用 GxP Gateway Audit 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude 说正在使用 GxP Gateway Audit,或回答中出现 GxP Gateway Audit 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
ChatGPT 暂时无法连接 GxP Gateway Audit
GxP Gateway Audit 需要安装在你的电脑上,而 ChatGPT 只能连接在网上运行的服务器
A · 使用能连接 GxP Gateway Audit 的应用
B · 其他 类中能连接 ChatGPT 的其他服务器
从同类中使用较多的里挑选,仅限用地址即可连接、无需密钥的
可连接 Claude Code,但需要先准备
需要填写 4 项设置(GLP_CONFIG, GLP_PRINCIPAL_ID, GLP_PRINCIPAL_NAME, GLP_PRINCIPAL_ROLE) · 需要先在电脑上安装 Python (uv)(只需一次)
把这段话复制到 Claude Code 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。
请在这台电脑上为 Claude Code 安装 MCP server GxP Gateway Audit,按顺序:1) 用 uv --version 检查是否有 uv。没有的话,请让我从 https://docs.astral.sh/uv/getting-started/installation/ 安装,不要自己安装。2) 只使用这份配置(已通过 PopNx MCP 检查):claude mcp add --scope user glp-audit-proxy --env GLP_CONFIG=your-value --env GLP_PRINCIPAL_ID=your-value --env GLP_PRINCIPAL_NAME=your-value --env GLP_PRINCIPAL_ROLE=your-value -- uvx mcp-glp-audit-proxy 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) GLP_CONFIG, GLP_PRINCIPAL_ID, GLP_PRINCIPAL_NAME, GLP_PRINCIPAL_ROLE 先保留 "your-value",请我自己把真实值粘贴到文件或应用的输入框里。不要让我在对话里输入密钥。5) 按约定执行,然后确认 GxP Gateway Audit 的工具真的出现了。这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。
已经装好了吗?先检查 · 打开终端,输入这条命令后按 Enter
uv --versionMac:按 ⌘ + Space,输入 Terminal 后按 Enter
Windows:打开“开始”菜单,输入 Windows PowerShell,然后选“打开”
还没安装: uv 没有点选式安装程序。从 uv 官方页面复制适合你系统(macOS 或 Windows)的一行命令,粘贴到终端 · 不需要单独安装 Python,uv 会在需要时自动下载
装好后关掉终端再打开,重新运行同一条命令,应显示版本号: uv --version
安装一次,所有需要 uv 的工具都能用
这些是程序设置,不是密钥,无需注册。按开发者的说明填写。
GLP_CONFIG 代理 JSON 配置文件的路径(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 operator、approver、qa、admin 之一。 说明为自动翻译,变量名保持原样;不确定时请查看原文。
Mac:按 Command+空格,输入 Terminal · Windows:打开 PowerShell
claude mcp add --scope user glp-audit-proxy --env GLP_CONFIG=your-value --env GLP_PRINCIPAL_ID=your-value --env GLP_PRINCIPAL_NAME=your-value --env GLP_PRINCIPAL_ROLE=your-value -- uvx mcp-glp-audit-proxy应能看到 GxP Gateway Audit 在列表中并显示已连接
用 GxP Gateway Audit 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude Code 说正在使用 GxP Gateway Audit,或回答中出现 GxP Gateway Audit 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
可连接 Cursor,但需要先准备
需要填写 4 项设置(GLP_CONFIG, GLP_PRINCIPAL_ID, GLP_PRINCIPAL_NAME, GLP_PRINCIPAL_ROLE) · 需要先在电脑上安装 Python (uv)(只需一次)
把这段话复制到 Cursor 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。
请在这台电脑上为 Cursor 安装 MCP server GxP Gateway Audit,按顺序:1) 用 uv --version 检查是否有 uv。没有的话,请让我从 https://docs.astral.sh/uv/getting-started/installation/ 安装,不要自己安装。2) 只使用这份配置(已通过 PopNx MCP 检查):{ "mcpServers": { "glp-audit-proxy": { "command": "uvx", "args": [ "mcp-glp-audit-proxy" ], "env": { "GLP_CONFIG": "your-value", "GLP_PRINCIPAL_ID": "your-value", "GLP_PRINCIPAL_NAME": "your-value", "GLP_PRINCIPAL_ROLE": "your-value" } } } } 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) GLP_CONFIG, GLP_PRINCIPAL_ID, GLP_PRINCIPAL_NAME, GLP_PRINCIPAL_ROLE 先保留 "your-value",请我自己把真实值粘贴到文件或应用的输入框里。不要让我在对话里输入密钥。5) 按约定执行,然后确认 GxP Gateway Audit 的工具真的出现了。这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。
已经装好了吗?先检查 · 打开终端,输入这条命令后按 Enter
uv --versionMac:按 ⌘ + Space,输入 Terminal 后按 Enter
Windows:打开“开始”菜单,输入 Windows PowerShell,然后选“打开”
还没安装: uv 没有点选式安装程序。从 uv 官方页面复制适合你系统(macOS 或 Windows)的一行命令,粘贴到终端 · 不需要单独安装 Python,uv 会在需要时自动下载
装好后关掉终端再打开,重新运行同一条命令,应显示版本号: uv --version
安装一次,所有需要 uv 的工具都能用
这些是程序设置,不是密钥,无需注册。按开发者的说明填写。
GLP_CONFIG 代理 JSON 配置文件的路径(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 operator、approver、qa、admin 之一。 说明为自动翻译,变量名保持原样;不确定时请查看原文。
在 GxP Gateway Audit 的设置中,GLP_CONFIG, GLP_PRINCIPAL_ID, GLP_PRINCIPAL_NAME, GLP_PRINCIPAL_ROLE 还是空的,填入你的密钥并保存
用 GxP Gateway Audit 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Cursor 说正在使用 GxP Gateway Audit,或回答中出现 GxP Gateway Audit 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Cursor 帮助页面核实 · 你的界面可能因版本略有不同
可连接 VS Code,但需要先准备
需要填写 4 项设置(GLP_CONFIG, GLP_PRINCIPAL_ID, GLP_PRINCIPAL_NAME, GLP_PRINCIPAL_ROLE) · 需要先在电脑上安装 Python (uv)(只需一次)
把这段话复制到 VS Code 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。
请在这台电脑上为 VS Code 安装 MCP server GxP Gateway Audit,按顺序:1) 用 uv --version 检查是否有 uv。没有的话,请让我从 https://docs.astral.sh/uv/getting-started/installation/ 安装,不要自己安装。2) 只使用这份配置(已通过 PopNx MCP 检查):{ "servers": { "glp-audit-proxy": { "type": "stdio", "command": "uvx", "args": [ "mcp-glp-audit-proxy" ], "env": { "GLP_CONFIG": "your-value", "GLP_PRINCIPAL_ID": "your-value", "GLP_PRINCIPAL_NAME": "your-value", "GLP_PRINCIPAL_ROLE": "your-value" } } } } 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) GLP_CONFIG, GLP_PRINCIPAL_ID, GLP_PRINCIPAL_NAME, GLP_PRINCIPAL_ROLE 先保留 "your-value",请我自己把真实值粘贴到文件或应用的输入框里。不要让我在对话里输入密钥。5) 按约定执行,然后确认 GxP Gateway Audit 的工具真的出现了。这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。
已经装好了吗?先检查 · 打开终端,输入这条命令后按 Enter
uv --versionMac:按 ⌘ + Space,输入 Terminal 后按 Enter
Windows:打开“开始”菜单,输入 Windows PowerShell,然后选“打开”
还没安装: uv 没有点选式安装程序。从 uv 官方页面复制适合你系统(macOS 或 Windows)的一行命令,粘贴到终端 · 不需要单独安装 Python,uv 会在需要时自动下载
装好后关掉终端再打开,重新运行同一条命令,应显示版本号: uv --version
安装一次,所有需要 uv 的工具都能用
这些是程序设置,不是密钥,无需注册。按开发者的说明填写。
GLP_CONFIG 代理 JSON 配置文件的路径(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 operator、approver、qa、admin 之一。 说明为自动翻译,变量名保持原样;不确定时请查看原文。
在 GxP Gateway Audit 的设置中,GLP_CONFIG, GLP_PRINCIPAL_ID, GLP_PRINCIPAL_NAME, GLP_PRINCIPAL_ROLE 还是空的,填入你的密钥并保存
用 GxP Gateway Audit 告诉我你能帮我做什么,然后做一件给我看✓ 如果 VS Code 说正在使用 GxP Gateway Audit,或回答中出现 GxP Gateway Audit 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 VS Code 帮助页面核实 · 你的界面可能因版本略有不同
Claude Code
claude mcp add --scope user glp-audit-proxy --env GLP_CONFIG=your-value --env GLP_PRINCIPAL_ID=your-value --env GLP_PRINCIPAL_NAME=your-value --env GLP_PRINCIPAL_ROLE=your-value -- uvx mcp-glp-audit-proxyClaude Desktop (claude_desktop_config.json)
{
"mcpServers": {
"glp-audit-proxy": {
"command": "uvx",
"args": [
"mcp-glp-audit-proxy"
],
"env": {
"GLP_CONFIG": "your-value",
"GLP_PRINCIPAL_ID": "your-value",
"GLP_PRINCIPAL_NAME": "your-value",
"GLP_PRINCIPAL_ROLE": "your-value"
}
}
}
}Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"glp-audit-proxy": {
"command": "uvx",
"args": [
"mcp-glp-audit-proxy"
],
"env": {
"GLP_CONFIG": "your-value",
"GLP_PRINCIPAL_ID": "your-value",
"GLP_PRINCIPAL_NAME": "your-value",
"GLP_PRINCIPAL_ROLE": "your-value"
}
}
}
}VS Code (mcp.json)
{
"servers": {
"glp-audit-proxy": {
"type": "stdio",
"command": "uvx",
"args": [
"mcp-glp-audit-proxy"
],
"env": {
"GLP_CONFIG": "your-value",
"GLP_PRINCIPAL_ID": "your-value",
"GLP_PRINCIPAL_NAME": "your-value",
"GLP_PRINCIPAL_ROLE": "your-value"
}
}
}
}GLP_CONFIG 必填 envGLP_PRINCIPAL_ID 必填 envGLP_PRINCIPAL_NAME 必填 envGLP_PRINCIPAL_ROLE 必填 env说明为自动翻译,变量名保持原样;不确定时请查看原文。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。
在你的电脑上运行,适用于
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月19日
注册名称已通过 GitHub 账户 antonio-castellon 验证,该账户拥有此仓库
代码最后更新于前天
使用 MIT
它在你的电脑上运行,没有互联网端点
在你的电脑上运行,改用本地设置
它在你的电脑上运行;我们只能读取互联网端点的工具列表
如果你是作者,可把这段代码贴到 README。徽章会链接回本页。
[](https://mcp.popnx.com/en/servers/antonio-castellon-mcp-glp-audit-proxy)提问、分享技巧或报告无法使用。按“有帮助”数量排序。
还没有评价
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 3 项适用的基础检查中通过了 3 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
GitHub 仓库最后更新于前天,最新版本(0.4.0)于25天前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Python (uv)。
同一分类中有:World Monitor, openstatus, Oh My Posh Validator, Strata, Jitsu
同一分类、其他作者、命令已通过检查。官方的排在前面,再按星标排序。
如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 100 tools.
Manage monitors, status pages, incidents and maintenances in your openstatus workspace.
Validate oh-my-posh configurations and segment snippets against the official schema.
MCP server for progressive tool usage at any scale (see https://klavis.ai)
Manage Jitsu data pipelines: destinations, streams, connections, functions, live events.
| 本项 GxP Gateway Audit | World Monitor | openstatus | Oh My Posh Validator | Strata | Jitsu | |
|---|---|---|---|---|---|---|
| 运行位置 | 需要安装在电脑上 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 |
| 需要密钥 | 否 | 否 | 否 | 否 | 否 | 否 |
| 可在 Claude 中按 + 添加 | 否 | 否 | 否 | 否 | 否 | 否 |
| 基础检查 | 3/3 | 4/4 | 4/4 | 4/4 | 1/4 | 4/4 |
| 许可证 | MIT | AGPL-3.0 | AGPL-3.0 | MIT | Apache-2.0 | MIT |
| 价格 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 |
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
mcp-name: io.github.antonio-castellon/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.
Requires Python 3.11 or newer.
pip install mcp-glp-audit-proxy
From a checkout:
pip install -e ".[dev]"
The mcp dependency is pinned to >=2.2.0,<3. That floor is outside GHSA-84m7-p3x7-pcfv (affected ranges are mcp >=1.8.0,<1.30.0 and >=2.0.0,<2.2.0). The process refuses to start on an older SDK.
export GLP_PRINCIPAL_ID=operator-1
export GLP_PRINCIPAL_NAME="Ada Analyst" export GLP_PRINCIPAL_ROLE=operator mcp-glp-audit-proxy --config config.json
Stdio identity comes from the environment (GLP_PRINCIPAL_ID, GLP_PRINCIPAL_NAME, GLP_PRINCIPAL_ROLE). When the config has no listen object, the process reads newline-delimited JSON-RPC on stdin and writes it on stdout, and it does not open a socket. When listen is set, the same command serves HTTPS and does not read stdio. A Cursor snippet is in mcp.json. A full config is in config.example.json. The config reference is docs/manual-guides/README.md.
plugins.storage, plugins.signer, plugins.reporters and plugins.auth select entry points. The defaults are jsonl, unsigned, json plus text, and env. env returns the principal from GLP_PRINCIPAL_* or the config file. It is not an identity provider. An unknown plugin, or a plugin whose declared licence feature is not enabled, refuses to start. The factory is not called. The proxy does not fall back to another backend. See docs/PLUGINS.md.
Verify a chain and write a searchable JSON export (the export is skipped when the chain does not verify):
mcp-glp-audit-proxy-verify data/audit.jsonl --json-export exports/audit.json
mcp-glp-audit-proxy-verify data/audit.jsonl --tool excel__write_cell --status ok mcp-glp-audit-proxy-verify data/audit.jsonl --print-head
--print-head prints seq= entry_hash=<64 hex>. 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. It is not signed. Signing is Pro. --pubkey passes a pinned public key file to the licensed signer plugin. With no licensed signer the check fails. Pass --licence and --client-id, or set GLP_LICENCE_PATH and GLP_CLIENT_ID, to load that signer. With no licence path, no licence file is read. A missing or invalid licence exits 2. Unsigned checkpoints stay the default and are not treated as signed. The log and the .head sidecar are mode 0600 on open. A log directory created by the store is mode 0700.
init asks for the audit log path, the tool allow list, the principal (id, name, role), and the retention profile and legal hold. It writes a JSON config the same loader as startup accepts, with mode 0600. Prompts and the file are ASCII. The wizard does not open a network connection. If the destination already exists, it is left unchanged unless you answer yes to the overwrite question.
mcp-glp-audit-proxy init
mcp-glp-audit-proxy init /srv/glp/config.json
The default path is GLP_CONFIG when that variable is set, otherwise config.json. That is the same file the proxy reads.
config check loads a config and prints a plain-language error when it does not load. The process exits 0 when the file loads and 1 when it does not. It uses the same loader as startup, including the GLP_* overrides. The default path matches init.
mcp-glp-audit-proxy config check
mcp-glp-audit-proxy config check config.json
A licensed plugin can add questions and a validation step through the mcp_glp_audit_proxy.wizard entry point. An unlicensed plugin is not called and adds nothing. See docs/PLUGINS.md.
A licence file is local. There is no network call. LM1 is three lines: LM1, base64 of the body, and base64 of an RSA-2048 PSS signature over those raw bytes. LM2 is three lines: LM2, base64 of the body, and base64 of a 64-byte Ed25519 signature over those raw bytes, and the body must be compact sorted JSON. LM1, and LM2 with no features list, enable the features declared by the installed licensed plugins. An LM2 file that lists features enables only the listed names. Any other file is rejected. The production public keys are in release_trust.json and are loaded by trusted_keys() in mcp_glp_audit_proxy.trust. The fingerprint is not a machine id. Details are in docs/PLUGINS.md.
Every mediated call, including denials and failures, is one JSON object on an append-only JSONL file. Each line is RFC 8785 canonical JSON. entry_hash is the SHA-256 of that object with entry_hash removed. prev_hash is the previous entry (64 zero digits for the first). hash_algo and canonicalization are stored on the entry. The open schema is schema/audit-record.schema.json. Cross-language vectors are in schema/jcs-test-vectors.json.
Fields include who (principal id, name, role), which tool, inputs, outputs, UTC timestamp plus utc_offset, protocol version, optional session id, record class (gxp_data, access, technical, config), reason for writes, and the previous hash.
Schema 1.3.0 stores transport (stdio or https), channel (mcp or https), flow (mcp2mcp, mcp2api, api2mcp, api2api, mcp2llm, api2llm, or null on local records), http, arguments_sha256, and result_sha256. The http object holds the method, the route template, the path with the query string removed, the kept headers, the names of stripped credential headers, the body SHA-256, body_mode, the stored body, the status, latency_ms, and kind (api, llm, or mcp). The query string is forwarded and is not stored. 1.0.0 and 1.1.0 lines omit the later keys. 1.2.0 lines omit the two SHA-256 fields. Older lines stay valid in the same chain.
The GxP trail is that file. The Python logging logger mcp_glp_audit_proxy.technical writes method, status and record class to stderr. It is not the record. Arguments are not written there.
excel__write_cell). Deny wins. An empty allow list denies every upstream tool.operator, approver, qa and admin. Only operator may call upstream tools. qa is read-only on the trail (glp_verify_chain, glp_search_audit, glp_export_audit). approver may record an approval and read the trail. admin may change policy and read the trail, and cannot call upstream tools.glp_update_policy with audit_enabled: false is denied and logged.write_tools) require a reason by default. The reason is _meta["io.github.antonio-castellon/reason"] or the argument _glp_reason (stripped before the upstream call).approver role records meaning approved. reviewed is stored with status reviewed and does not authorise the write. A log written before schema 1.1.0 may show that decision as status approved with meaning reviewed; those lines still verify and still do not authorise the write. rejected rejects it. An approval is single-use, bound to the SHA-256 of the canonical {tool, arguments}, and expires (default 3600 seconds). A successful write that presents a matching approval records it as consumed even if require_approval_for_writes was turned off before that call. A failed upstream call does not consume it. The record label is approval. It is not an electronic signature.http_allow and http_deny. Each entry is METHOD /path with a shell-style glob on the path (GET /v1/studies/*). Deny wins. An empty http_allow denies every HTTPS route. It does not deny MCP tool calls. Only operator may call an HTTPS route.audit.body_mode is hash_only (the default for a new config), redacted, or full. Which value to use is the customer's and QA's decision. body_mode applies to HTTPS bodies and to MCP tool-call arguments and results. The SHA-256 of the raw request body is always recorded, and the SHA-256 of MCP tool arguments and results is recorded the same way. hash_only stores no body bytes and no MCP payload. redacted stores JSON with the paths in audit.redact_paths replaced by *** (a non-JSON body stores no plaintext). full stores the parsed JSON, or the UTF-8 text, of the request inside the hash-chained record, and full also stores the response text as response_body next to response_sha256. The log file is mode 0600. Binary that is not UTF-8 is hashed and not stored as the request body. The response body is returned to the client in every mode. A write request without Content-Length, or with Transfer-Encoding, is refused with 411 and logged. In hash_only and redacted modes the trail proves that a payload existed and was unaltered, but does not show its content; the content record must be kept by the target system (OECD N