Compliance AIops

Name: Compliance AIops
Author: AIops-tools

作者：AIops-tools版本 0.15.0i★ –i在你的电脑上运行

注册名称io.github.AIops-tools/compliance-aiops

安装

概览

作者提供的说明（英文原文）

Compliance evidence from AIops audit trails: HIPAA/PCI/SOC2/GDPR, OSCAL export, 19 tools.

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数：意见、测量和人气是不同的东西。

用户评价i暂无评价评价功能将在后续阶段与账户功能一起开放
我们的基础检查i1 项中通过 1 项依据公开信息检查；尚未扫描代码
使用情况i尚未统计★ –

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

连接方式: 在你的电脑上运行
传输方式: stdio
分类: 法律与政府数据

安装

选择你使用的 AI 应用，然后复制设置。

安装之前

基础检查：1 项中通过 1 项
在你的电脑上运行，拥有你的用户账户的权限（文件、网络、应用）。
注册中心没有列出需要填写的密钥。

你需要

PyPI已安装 Python 的 uv（用于 uvx 命令）

你用的是哪个应用？

ClaudeClaude CodeCursorVS CodeChatGPT

在上方选择你的应用。我们会记住它，下次按钮会显示“安装到 …”。

打开 Claude Desktop → Settings → Developer → Edit Config，把下面的内容粘贴到 claude_desktop_config.json

{
  "mcpServers": {
    "compliance-aiops": {
      "command": "uvx",
      "args": [
        "compliance-aiops"
      ]
    }
  }
}

在终端中运行这条命令

claude mcp add compliance-aiops -- uvx compliance-aiops

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json，或 ~/.cursor/mcp.json

{
  "mcpServers": {
    "compliance-aiops": {
      "command": "uvx",
      "args": [
        "compliance-aiops"
      ]
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

{
  "servers": {
    "compliance-aiops": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "compliance-aiops"
      ]
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

这个服务器在你的电脑上运行，而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。

你的选择通过 Cookie 保存在这台设备上，无需账户。

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。

它能做什么

它在你的电脑上运行；安装后，工具列表会显示在你的 AI 应用中。

基础检查i

我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日

✓ 通过
作者与仓库一致
注册名称已通过 GitHub 账户 AIops-tools 验证，该账户拥有此仓库
… 尚未检查
仍在维护
我们还没有从 GitHub 读取这个仓库
… 尚未检查
有许可证
我们还没有从 GitHub 读取这个仓库
– 不适用
端点有响应
它在你的电脑上运行，没有互联网端点
– 不适用
使用 OAuth 登录
在你的电脑上运行，改用本地设置
… 尚未检查
工具描述中没有隐藏指令
它在你的电脑上运行；我们只能读取互联网端点的工具列表

与“法律与政府数据”中的其他服务器比较i

星标数多于此分类中其他 1731 个服务器的 0%
发布到注册中心的时间比此分类中其他 1731 个服务器的 73% 更新
基础检查结果等于或优于此分类中其他 1731 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。

常见问题

Compliance AIops 安全吗？

它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前，请先看看这个服务器要求哪些权限，并使用只具备所需权限的密钥。

它需要哪些密钥或代码？

注册中心没有列出必需的密钥，不过有些服务器会在首次使用时要求你登录。

它在我的电脑上运行还是在云端？

它在你的电脑上运行。你的 AI 应用会在需要时启动它，数据不会经过作者的服务器（除非它自己调用在线服务）。

它还在维护吗？

GitHub 仓库最后更新于–，最新版本（0.15.0）于8天前进入注册中心。

哪些应用可以使用它？

支持 MCP 的应用，例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Python (uv)。

有什么可以替代它？

同一分类中有：Private Law Wiki, Agentum Entity Resolver, Contract Compass

替代选择

同一分类中其他作者的服务器，按星标数排序。

如何看卡片：★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

Private Law Wiki

作者：privatelawattorneys

Sourced answers, search and bank-case assessment for wiki.private.law by the Mothership runtime.

在云端运行今天更新

安装

Agentum Entity Resolver

作者：Algiras

Company registry, VAT, sanctions, vendor KYB, IBAN and wallet checks; pay per call by x402 or card.

在云端运行今天更新

安装

Contract Compass

作者：sallim-app

Korean public procurement law: rule-engine rulings, statutes search, live court precedents

在云端运行今天更新

安装

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

Compliance AIops

Audit availability: Real writes require a committed pending audit row and stop before contacting the platform if storage is unavailable. Reads and previews may continue with a warning; new audit rows store outcome summaries rather than full responses.

Disclaimer: Community-maintained open-source project. Not affiliated with, endorsed by, or sponsored by any framework body or GRC vendor. HIPAA, PCI-DSS, SOC 2, GDPR and OSCAL are referenced descriptively; the frameworks and trademarks belong to their owners. MIT licensed.

Governed compliance-evidence tooling for AI-agent infrastructure ops. It reads the audit trails your governed AIops agents already write — the local ~/. -aiops/audit.db SQLite trails, all sharing one audit_log schema — and turns that activity into framework-mapped, hash-chain-sealed compliance evidence. It never scans your infrastructure and never replaces a GRC platform: it converts the trails you already produce into auditor-ready, tamper-evident evidence bundles.

Unlike the other tools in the AIops-tools line it is not a platform wrapper: no external API, no network, no platform credentials. Its only inputs are those on-disk audit databases, read read-only. That also makes it the easiest-to-self-test tool in the line — fully offline and deterministic.

Evidence, not certification. Fully offline; the source audit.db

files remain the system of record. OSCAL export is a documented v0.2 roadmap

item (v0.1 emits JSON + Markdown + CSV shaped to ease a future OSCAL

Assessment-Results adapter).

Key features

Framework mapping with honest evidence-strength — audit events map to HIPAA §164.312 / PCI-DSS v4.0 / SOC 2 TSC / GDPR controls. Audit trails prove *operating effectiveness* strongly but *control design / configuration* only partially, and each control is labelled strong or partial. gap_analysis says so per control, with the caveat and a remediation hint.
Hash-chain-sealed evidence bundles — SHA-256 over ordered records (hash = SHA-256(prev_hash ‖ canonical_json(record)), genesis prev = 64 zeros). The chainHead is reproducible for the same (framework, period, sources). verify_bundle catches tampering; verify_source_chain detects row-id gaps / deletions in a source trail. An optional HMAC signature seals a bundle under a stored signing key.
Zero-network, read-only — no credentials, no outbound calls, no mutation of the source trails. Bundles are the only thing written, under ~/.compliance-aiops/bundles/.
Deterministic, test-verified integrity — the integrity claims are themselves covered by tests: synthetic audit DBs are built through the real governance-harness AuditEngine, a golden reproducible chainHead is asserted, and tamper tests confirm detection. No live infrastructure needed.

What this tool does, and does not, decide

It reads your audit trails and writes evidence bundles — and records every operation. It does not decide whether producing or signing a bundle is allowed: that is the agent's judgement, or the filesystem permissions of the account it runs as. The source audit.db files are opened strictly read-only regardless, and the only thing ever written is a bundle under ~/.compliance-aiops/bundles/.

So there is no read-only switch, no policy file, no approval gate to configure. The one thing the tool guarantees is that nothing is silent: every call, over MCP and over the CLI alike, lands an audit row in ~/.compliance-aiops/audit.db.

Each tool declares a risk_level, kept in agreement with its [READ]/[WRITE]

documentation tag by a test, and carried into the audit row as a descriptive

tier — so a reviewer can see at a glance what a row was. It is a label, not a

gate.

Tools (16 MCP tools)

Read / analysis (13)

Tool	Purpose
`list_audit_sources`	Discovered sibling audit DBs (path, tool, readable, row count)
`query_audit_events`	Cross-tool event query — filter by tool/skill/status/risk/approved/selector/since/until
`activity_timeline`	Event counts bucketed by hour or day
`list_frameworks`	Supported frameworks + control counts
`coverage_summary`	Per-control covered/weak/uncovered for ONE framework
`control_evidence`	Evidence rows + population + a reproducible query for ONE control
`gap_analysis`	Controls with no/weak evidence + honest caveat + remediation
`approval_report`	High-risk write ops + who approved + rationale (the CC8.1 / PCI 7-8 / HIPAA §312(a) artifact)
`exceptions_report`	Denied / error / budget_exceeded ops — enforcement + anomaly evidence
`verify_source_chain`	Chain head + row-id gap detection for one source
`verify_bundle`	Verify a sealed bundle: chain + seal head + optional signature
`list_bundles`	Bundles under `~/.compliance-aiops/bundles/`
`oscal_assessment_results`	A sealed bundle as a NIST OSCAL 1.2.3 Assessment Results document, inline, with its limitations named
`bundle_schedule_hint`	Ready-to-paste cron line + non-interactive command for periodic sealing (writes nothing)

Write / artifact (3 — no external mutation)

Tool	Risk	Purpose
`generate_evidence_bundle`	low	One call: coverage + approval trail + exceptions + sealed records → a bundle `.json`
`export_bundle`	low	Render a bundle to markdown / csv / json / oscal
`sign_bundle`	medium	HMAC over the seal using the stored signing key

The CLI exposes a convenience subset; the full 19-tool surface is available over MCP.

Frameworks & controls

Framework	Sample controls (strength)
HIPAA (§164.312)	164.312(b) Audit controls (strong), 164.312(a)(1) Access control (strong), 164.312(c)(1) Integrity (strong)
PCI-DSS v4.0	10.2 Audit log content (strong), 10.3 Protect audit logs (strong), 7-8 Least privilege / authn (partial)
SOC 2 TSC	CC6.1 Logical access (strong), CC7.2 Monitoring (strong), CC8.1 Change management (strong)
GDPR	Art.30 Records of processing (partial), Art.32 Security of processing (strong)
ISO/IEC 27001:2022 (Annex A)	A.5.15 Access control (strong), A.5.16 Identity mgmt (strong), A.5.18 Access rights (partial), A.8.2 Privileged access (partial), A.8.15 Logging (strong), A.8.16 Monitoring (strong), A.8.32 Change management (strong)
等保2.0 (DJCP L3) (GB/T 22239-2019 三级)	8.1.5.4 安全审计 (strong), 8.1.4.2 访问控制 (partial), 8.1.5 安全管理中心/集中审计 (strong)

Install

uv tool install compliance-aiops      # or: pipx install compliance-aiops

Quick start

As a Claude Code plugin

One install gives an agent both the skill and the MCP server:

/plugin marketplace add AIops-tools/marketplace

/plugin install compliance-aiops@aiops-tools

The MCP server is fetched with uv and pinned to the package version this plugin declares, so an audit row can be traced back to the code that wrote it. Credentials are still configured with compliance-aiops init — see below.

As an OpenClaw plugin

The same bundle is published on ClawHub, where one install delivers the skill and its MCP server together:

openclaw plugins install clawhub:@zw008/compliance-aiops

openclaw skills info compliance-aiops # expect: Visible to model: yes

Restart the OpenClaw gateway afterwards so it loads the plugin. The MCP server is fetched with uv, pinned to this exact release, so uvx has to be on PATH — without it the skill still installs but reports Visible to model: no. Credentials are configured exactly as below.

As a CLI or standalone MCP server

compliance-aiops init                 # discover sibling ~/.*-aiops/audit.db, set org name, optional signing key

compliance-aiops doctor # which sibling audit DBs are present/readable compliance-aiops overview # audit sources + per-framework covered/total compliance-aiops report coverage soc2 # per-control SOC 2 coverage compliance-aiops bundle generate soc2 # sealed evidence bundle → ~/.compliance-aiops/bundles/ compliance-aiops bundle verify # re-verify the chain + seal (+ signature)

Run as an MCP server (stdio):

export COMPLIANCE_AIOPS_MASTER_PASSWORD=...   # only needed to unlock a signing key

compliance-aiops mcp # or: compliance-aiops-mcp

Where that password then lives: an exported variable is readable by

every process this shell starts and is recorded by shell history. On a

shared or long-lived host, prefer the interactive prompt, or inject it from

a secret manager for the life of the one command that needs it.

定期封存 (scheduled sealing)

Evidence bundles are most useful when sealed on a cadence (e.g. weekly), so each period has a tamper-evident anchor. This tool ships no daemon — instead bundle schedule prints a ready-to-paste cron line plus the exact non-interactive command, and writes nothing:

compliance-aiops bundle schedule soc2 --cron "0 2 * * 1" --period 7d --sign

It returns a cronLine you paste into crontab -e, for example:

0 2 * * 1 compliance-aiops bundle generate soc2 --period 7d --sign

--period (also available on bundle generate) is a convenience relative window — 7d, 24h, 2w, or last-7-days — resolved to a since/until pair ending "now", so each scheduled run seals the trailing window.
Export COMPLIANCE_AIOPS_MASTER_PASSWORD in the cron job's environment so a stored signing key unlocks non-interactively. Do not inline the real password in the crontab file — reference it from a protected env file.

Integrity & honest limits

Tamper-EVIDENT, not tamper-PROOF. The hash chain and optional signature let an auditor *detect* alteration; they do not prevent it. The source audit.db files remain the system of record — record the chainHead out-of-band if you need an independent anchor.
Operating effectiveness vs. design. An audit trail strongly evidences that a control *ran* (samples, approvals, denials) but only partially evidences that a control is *designed / configured* correctly (e.g. MFA required, least-privilege roles). Every control carries a strong / partial label and gap_analysis surfaces the caveat rather than overclaiming.

Supported scope & limitations

Evidence, not certification. This produces auditor-ready evidence bundles; it does not issue attestations, opinions, or certifications.
In scope: the six frameworks above, over the audit_log trails written by governed AIops tools discovered via ~/.*-aiops/audit.db.
Not in scope: it does not scan infrastructure, connect to any platform, or replace a GRC platform. For platform operations use the other AIops-tools.
OSCAL export is v0.2. v0.1 emits JSON + Markdown + CSV.
Interfaces may change before v1.0.
Verification: the integrity claims are covered by deterministic offline tests; see docs/VERIFICATION.md for the reproducible run.

Missing a capability?

Want another framework, control mapping, export format (OSCAL, CSV shape), or a verification you don't see here? Open an issue or a PR — contributions welcome.

Compliance AIops

概览

PopNx MCP 的三大支柱

它能帮你做什么

安装

安装之前

它能做什么

基础检查i

作者与仓库一致

仍在维护

有许可证

端点有响应

使用 OAuth 登录

工具描述中没有隐藏指令

与“法律与政府数据”中的其他服务器比较i

常见问题

替代选择

Private Law Wiki

Agentum Entity Resolver

Contract Compass

作者的 README

Compliance AIops

Key features

What this tool does, and does not, decide

Tools (16 MCP tools)

Read / analysis (13)

Write / artifact (3 — no external mutation)

Frameworks & controls

Install

Quick start

As a Claude Code plugin

As an OpenClaw plugin

As a CLI or standalone MCP server

定期封存 (scheduled sealing)

Integrity & honest limits

Supported scope & limitations

Missing a capability?