Ext Ops Panel
Open dashboard
Comparison

compliance-checks vs ContinueOps Public MCP

compliance-checks is a plugin bundle for AI coding tools published by cyberagentic. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). ContinueOps Public MCP is an MCP server published by continueops.com. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-15. 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-checksContinueOps Public MCP
Claude Code: claude-plugins-community Listed
Version: c5d5a7d
No figure published
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.2.0
No figure published
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-checks vs ContinueOps Public MCP
Factcompliance-checksContinueOps Public MCP
Marketplaces that list it11
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleRemote server (tjcjvxibsrxizwuajypz.supabase.co/functions/v1/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
LicenceNot statedNot stated
Repository (differs)github.com/cyberagentic/compliance-checksNot stated
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 27 h ago

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-checks

In its own words, on Claude Code: claude-plugins-community:

EU regulatory compliance checks for businesses. Assess whether your organisation is affected by NIS-2, classify AI systems under the EU AI Act, check GDPR compliance before introducing new applications, review technical security measures (TOMs), and audit data processing agreements. Each check asks a few targeted questions and produces a structured report with a clear risk rating and actionable next steps.

ContinueOps Public MCP

In its own words, on Official MCP Registry:

BC/DR & compliance tools: DORA, NIS2, NIST CSF, GDPR, SOC 2, CMMC, CAF, ISO 27001, FCA/PRA.

How to run each

compliance-checks As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install compliance-checks@claude-community

ContinueOps Public MCP As a remote MCP server

Claude Code
claude mcp add --transport http continueops-public https://tjcjvxibsrxizwuajypz.supabase.co/functions/v1/mcp

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

Only ContinueOps Public MCP 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-checks · What it can do: ContinueOps Public MCP · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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