Compliance AIops

Name: Compliance AIops
Author: AIops-tools

by AIops-toolsversion 0.15.0i★ –iRuns on your computer

Registry nameio.github.AIops-tools/compliance-aiops

Install

Overview

Description from the maker (original English)

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

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: stdio
Category: Law & government data

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
The registry lists no key to fill in.

You need

PyPIPython’s uv installed (for the uvx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

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

Run this in your terminal

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

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

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

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

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

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account AIops-tools, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Law & government datai

More stars than 0% of the other 1731 servers in this category
Published to the registry more recently than 73% of the other 1731 servers in this category
Basic checks equal to or better than 100% of the other 1731 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Compliance AIops safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.15.0) reached the registry 8 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv) on your computer.

What can I use instead?

In the same category: Agentum Entity Resolver, Contract Compass, Agent Data Tools: Company, compliance and checks

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Agentum Entity Resolver

by Algiras

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

Runs in the cloudUpdated today

Install

Contract Compass

by sallim-app

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

Runs in the cloudUpdated today

Install

Agent Data Tools: Company, compliance and checks

by Nutshell2000

38 tools: OFAC sanctions, counterparty checks, company, domain, email. 25 free calls.

Runs in the cloudUpdated today

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

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

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Law & government datai

Common questions

Alternatives

Agentum Entity Resolver

Contract Compass

Agent Data Tools: Company, compliance and checks

README from the maker

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?