compliance-aiops
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| COMPLIANCE_AIOPS_MASTER_PASSWORD | No | Password to unlock the signing key (optional). |
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| generate_evidence_bundleA | [WRITE][risk=medium] Assemble + hash-chain-seal an evidence bundle for a framework. One-call happy path: coverage + approval trail + exceptions + sealed evidence records → a bundle .json under ~/.compliance-aiops/bundles/. Reads audit DBs and writes a local artifact only; touches no external system. Args: framework: hipaa / pci_dss / soc2 / gdpr / iso27001 / djcp_l3. period_start / period_end: ISO timestamps bounding the reporting period. out_path: Where to write the bundle (default: the bundle dir). sign: If True and a signing key is stored, attach an HMAC signature. period: Convenience relative window (e.g. "7d", "last-7-days") used only when period_start / period_end are not supplied. |
| bundle_schedule_hintA | [READ] Ready-to-paste cron line + command for periodic sealed-bundle generation. WRITES NOTHING and starts no daemon — it only composes and validates the
crontab line and the exact non-interactive Args: framework: hipaa / pci_dss / soc2 / gdpr / iso27001 / djcp_l3. cron: A standard 5-field cron expression (default: 02:00 every Monday). period: Relative window each run should cover (e.g. "7d", "last-7-days"). sign: If True, include --sign in the composed command. |
| sign_bundleA | [WRITE][risk=medium] Attach an HMAC signature over a bundle's seal (uses stored key). Requires a signing key in the encrypted store ('compliance-aiops secret set signing-key'). Medium risk because it reads the encrypted secret store. Args: bundle_path: Path to a bundle .json. |
| export_bundleA | [WRITE][risk=medium] Render a bundle to markdown / csv / json. Args: bundle_path: Path to a bundle .json. fmt: "markdown", "csv", or "json". out_path: Output path (default: alongside the bundle). |
| list_bundlesA | [READ] Previously generated bundles + their chain head and metadata. |
| list_frameworksA | [READ] Supported compliance frameworks (HIPAA / PCI-DSS / SOC 2 / GDPR) + control counts. |
| coverage_summaryB | [READ] Per-control coverage for a framework over a period (are we covered?). Args: framework: hipaa / pci_dss / soc2 / gdpr. since / until: ISO timestamps bounding the reporting period. |
| control_evidenceA | [READ] Evidence rows for ONE control + population size + reproducible query. Args: framework: hipaa / pci_dss / soc2 / gdpr. control_id: e.g. "164.312(b)", "10.2", "CC8.1", "Art.30". since / until: ISO timestamps bounding the period. sample_size: Number of representative evidence rows to include.
|
| gap_analysisB | [READ] Controls with no/weak evidence, each with an honest reason + remediation. States the design-vs-operating caveat: audit trails evidence operating effectiveness strongly and control design/configuration only partially. Args: framework: hipaa / pci_dss / soc2 / gdpr. since / until: ISO timestamps bounding the period. |
| list_audit_sourcesA | [READ] List sibling audit DBs (~/.-aiops/audit.db) + readability/row counts. Call this first to see which governed AIops tools' trails are available as compliance evidence. |
| query_audit_eventsA | [READ] Cross-tool audit event query — the workhorse. Args: source: Restrict to one source tool (e.g. nutanix-aiops). skill / tool / status / risk_level: Field filters. approved: True = only ops with an approver; False = only ops without one. selector: Evidence class filter — audit_trail / attribution / change / enforcement / exception. since / until: ISO timestamps bounding the period. limit: Max rows to return. Returns |
| activity_timelineA | [READ] Op counts bucketed by hour/day — monitoring-continuity evidence. Args: since / until: ISO timestamps bounding the period. bucket: "hour" or "day". |
| verify_source_chainA | [READ] Chain head for a source's current events + row-id gap detection. Record the returned chainHead out-of-band; re-run later to detect changes. Row-id gaps may indicate deleted audit rows. Args: source: Source tool name (from list_audit_sources). since / until: ISO timestamps bounding the range. |
| verify_bundleA | [READ] Verify a sealed evidence bundle: chain integrity, seal head, signature. Args: bundle_path: Path to a bundle .json produced by generate_evidence_bundle. |
| approval_reportA | [READ] High-risk write ops with approver + rationale (the change-approval trail). The who/what/when/why/approval artifact for SOC 2 CC8.1, PCI 7-8, HIPAA §312(a). Args: since / until: ISO timestamps bounding the period. high_only: True = only high/critical-risk writes (default); False = all writes. |
| exceptions_reportA | [READ] Denied / error / budget-exceeded ops — enforcement + anomaly evidence. Denials prove the governance controls actually block, not rubber-stamp. Args: since / until: ISO timestamps bounding the period. |
| undo_listA | [READ] List recorded, not-yet-applied undo tokens (most recent first). Each entry names the original tool, the inverse tool that Returns {"undos": [...], "returned": N, "limit": L, "truncated": bool}.
Each entry carries Args: limit: Max rows to return (default 50, capped at 500). target: Unused (undo state is host-local); accepted for CLI uniformity. |
| undo_applyA | [WRITE][risk=medium] Apply a recorded undo by dispatching its inverse tool. The inverse runs through its own governed tool, so its real risk tier is recorded there. Pass dry_run=True to preview the inverse call without executing it. A token can only be applied once. Args:
undo_id: The undoId from undo_list (or an |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/AIops-tools/Compliance-AIops'
If you have feedback or need assistance with the MCP directory API, please join our Discord server