Ext Ops Panel
Open dashboard
Comparison

gia-eu-ai-act-compliance vs Compliance Auditor MCP

gia-eu-ai-act-compliance is a plugin bundle for AI coding tools published by knowledgepa3. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). Compliance Auditor MCP is an MCP server published by firasmosbehi. 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
Marketplacegia-eu-ai-act-complianceCompliance Auditor MCP
Claude Code: claude-plugins-community Listed
Version: 1.0.0
Forks (GitHub): 0
Stars (GitHub): 1
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.1.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

gia-eu-ai-act-compliance vs Compliance Auditor MCP
Factgia-eu-ai-act-complianceCompliance Auditor MCP
Marketplaces that list it11
Stars (GitHub) (differs)1No figure on GitHub
Forks (GitHub) (differs)0No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleRemote server (frayess-mosbehi--compliance-auditor-mcp.apify.actor/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)1Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/knowledgepa3/gia-eu-ai-actgithub.com/firasmosbehi/compliance-auditor-mcp
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 42 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

gia-eu-ai-act-compliance

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

Classify any AI system under the EU AI Act (Regulation 2024/1689). Screens all 8 prohibited practices (Article 5), classifies high-risk systems across all 8 Annex III categories, calculates penalty exposure (up to 7% global turnover), and generates structured compliance reports. Built for compliance officers, CISOs, DPOs, and legal teams preparing for the August 2, 2026 enforcement deadline. Powered by GIA (Governance Intelligence Automation) — the open governance framework for AI agents.

Compliance Auditor MCP

In its own words, on Official MCP Registry:

City hiring-compliance MCP server with regulation search and full audit risk scoring.

How to run each

gia-eu-ai-act-compliance As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install gia-eu-ai-act-compliance@claude-community

Compliance Auditor MCP As a remote MCP server

Claude Code
claude mcp add --transport http compliance-auditor https://frayess-mosbehi--compliance-auditor-mcp.apify.actor/mcp --header "Authorization: Bearer <YOUR_APIFY_TOKEN>"

Requires: Authorization header

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

Only Compliance Auditor 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: gia-eu-ai-act-compliance · What it can do: Compliance Auditor 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