compliance-checks vs com.oceanalt/aml
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). com.oceanalt/aml is an MCP server published by oceanalt.com. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-10-25. 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
| Marketplace |  com.oceanalt/aml | |
|---|---|---|
| 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.7.6 Downloads/month (npm): 1 082 Downloads/week (npm): 314 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
| npm registry (MCP servers) | Not listed | Listed Version: 0.7.6 Downloads/month (npm): 1 082 Downloads/week (npm): 314 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
| Fact | compliance-checks | com.oceanalt/aml |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | No figure on GitHub | 0 |
| Forks (GitHub) (differs) | No figure on GitHub | 0 |
| Last release (differs) | Not published | 2026-10-20 |
| Where it runs (differs) | Installs as a plugin bundle | Remote server or your machine |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence (differs) | Not stated | MIT |
| Repository (differs) | github.com/cyberagentic/compliance-checks | github.com/oceanalt666/oceanalt-aml-mcp |
| Changes in the last 7 days (differs) | 0 | 7 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 15 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
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.
com.oceanalt/aml
Pre-payment checks for AI agents: sanctions and AML screening of payees, payment pages and requests.
How to run each
compliance-checks As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-community
/plugin install compliance-checks@claude-communitycom.oceanalt/aml As a remote MCP server
claude mcp add --transport http aml https://oceanalt.com/api/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only com.oceanalt/aml has a remote endpoint we check. How we check endpoints
Tools each declares
Neither the marketplaces of compliance-checks nor its endpoint list any tools, so we do not compare tools.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: compliance-checks · What it can do: com.oceanalt/aml · 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. Package data comes from the public npm registry (registry.npmjs.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.