Ext Ops Panel
Open dashboard
Comparison

Compliance AIops vs ISMS Copilot

Compliance AIops is an MCP server published by AIops-tools. Marketplaces we read that list it: 1 (Official MCP Registry). ISMS Copilot is an MCP server published by tristanroth1. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-08. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
MarketplaceCompliance AIopsISMS Copilot
Official MCP Registry Listed
Version: 0.15.0
Downloads/month (PyPI): 914
Downloads/week (PyPI): 152
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Listed
Version: 0.3.2
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

Compliance AIops vs ISMS Copilot
FactCompliance AIopsISMS Copilot
Marketplaces that list it11
Stars (GitHub)00
Forks (GitHub)00
Last release (differs)2026-10-30 (better)2026-10-26 (worse)
Where it runs (differs)On your machine (compliance-aiops)Remote server (account.ismscopilot.com/v1/account/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
LicenceNot statedNot stated
Repository (differs)github.com/aiops-tools/compliance-aiopsgithub.com/better-isms/ismscopilot-plugin
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkStatus out of date: last check 47 h ago returned HTTP 401

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

Compliance AIops

In its own words, on Official MCP Registry:

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

ISMS Copilot

In its own words, on Official MCP Registry:

The compliance specialist your AI calls: ISO 27001, SOC 2, GDPR, NIS 2, DORA and more.

How to run each

Compliance AIops As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio compliance-aiops -- uvx compliance-aiops

ISMS Copilot As a remote MCP server

Claude Code
claude mcp add --transport http ismscopilot-account https://account.ismscopilot.com/v1/account/mcp

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only ISMS Copilot has a remote endpoint we check. How we check endpoints

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

Neither one's marketplaces publish the settings it asks for.

What it can do: Compliance AIops · What it can do: ISMS Copilot · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built