Add CSOAI-ORG/eu-ai-act-compliance-mcp to the GitHub MCP Registry (curation request)

[CSOAI-ORG]

Curation request: CSOAI-ORG/eu-ai-act-compliance-mcp

Server name: eu-ai-act-compliance-mcp
Org: CSOAI-ORG (Council of AI)
Type: Remote MCP server (also published on PyPI)

What it does

EU AI Act measurement corpus — 417 frozen provisions (113 Articles, provision-level granularity), signed GSPC crosswalk, article-level tools. Every response cites the frozen provision. Measurement, not certification.

Registry evidence

• Published in the official MCP OSS registry: io.github.CSOAI-ORG/* (a2a-governance-bridge-mcp, eu-ai-act-compliance-mcp and 30 version-rows live)
• PyPI: https://pypi.org/project/eu-ai-act-compliance-mcp/
• Glama: https://glama.ai/mcp/servers/CSOAI-ORG/eu-ai-act-compliance-mcp
• Tested server: npx -y eu-ai-act-compliance-mcp (or pip install eu-ai-act-compliance-mcp)
• Endpoint: https://councilof.ai/mcp (Streamable HTTP, MCP initialize verified 200)

Why it fits

The GitHub MCP Registry lists servers useful to developers building with agents. An EU AI Act compliance measurement server (417 frozen provisions, deterministic predicates, no LLM-as-judge, Ed25519-signed outputs) is directly useful to GitHub Copilot/agent developers shipping AI features in the EU.

Per the registry's onboarding: this is a remote server with a published server.json in the OSS registry and a working MCP initialize. Happy to provide test transcripts or a demo video if useful.

CC: CSOAI-ORG

[CAOShurong]

I performed a read-only curation check against the repository, PyPI, the official registry API, and the advertised remote endpoint.

• The official registry already has an active latest entry for io.github.CSOAI-ORG/eu-ai-act-compliance-mcp at version 1.8.15, published 2026-08-19. The current registry record is a PyPI/stdio package entry; it has no remotes entry.
• PyPI also reports 1.8.15 as the latest release, while the repository's current server.json still declares version 1.8.14. The source manifest therefore lags the package/registry metadata.
• The issue's advertised remote endpoint https://councilof.ai/mcp (with and without a trailing slash) returned HTTP 405 to an unauthenticated MCP initialize POST using the standard JSON and protocol-version headers. I could not reproduce the claimed 200 from the current public endpoint; this may be an endpoint, authentication, or deployment change rather than proof that the server is permanently unavailable.

Based on the current registry API, no new registry addition appears necessary: the server is already listed and active. The useful follow-up would be to update this issue with the current registry/version evidence, reconcile server.json 1.8.14 vs PyPI/registry 1.8.15, and clarify whether the remote URL is intended to be registered (it is not part of the current registry record). I would avoid treating the README's “initialize verified 200” claim as current until the endpoint and authentication requirements are reproducibly documented.