@complyedge/mcp
Offline MCP server for EU AI Act compliance checks. Three read-only tools over a bundled 63-rule corpus — Art. 5 prohibited practices, Art. 50 transparency, GDPR, HIPAA, SOX, PCI DSS, COPPA. Runs with npx: no Python, no API key, no network call.
No outside reports on file
@complyedge/mcp requires API keys or tokens; restrict its folder reach, network access, and credentials before installing.
Based on public adoption and transparency signals as of Oct 23, 2026. Our opinion, not a code audit or security guarantee.
What it can access
- Local filesNo local folder access notedLOW
- Command executionNo shell command runner notedLOW
- Network reachConnects to outside service APINOTED
- CredentialsRequires API key or tokenREVIEW
- Package sourcenpm (@complyedge/mcp)PUBLIC
Inferred from this listing’s public package details and description. Check the project’s source before installing.
Install
npx -y @complyedge/mcpEverything known
We found nothing about this project in the sources we read (last checked 2026-10-30). That does not mean it has no problems.
0 incidents · 0 advisories · 0 news articles · 0 community threads · checked 2026-10-30
Popularity grade: C (from public signals such as stars and downloads, not a code review). Graded 2026-10-24.
Sources we read: OSV, GitHub Advisory Database, CISA Known Exploited Vulnerabilities, 44 security news feeds and our incident library. Last checked 2026-10-30.
About @complyedge/mcp
@complyedge/mcp is an MCP server focused on Cloud & infrastructure: Offline MCP server for EU AI Act compliance checks. Three read-only tools over a bundled 63-rule corpus — Art. 5 prohibited practices, Art. 50 transparency, GDPR, HIPAA, SOX, PCI DSS, COPPA. Runs with npx: no Python, no API key, no network call.
It is published on npm as @complyedge/mcp and published on PyPI as complyedge and hosted on GitHub at complyedge/complyedge (4 GitHub stars, 34 weekly npm downloads, 120 PyPI downloads, last repository push on 2026-10-11). Based on its public metadata, its operational scope includes: requires api key or token.
Setup
Check these steps against the project’s own instructions before running anything.
Run @complyedge/mcp with --ignore-scripts in claude_desktop_config.json or .cursor/mcp.json:
{
"mcpServers": {
"mcp": {
"command": "npx",
"args": ["-y", "--ignore-scripts", "@complyedge/mcp"]
}
}
}
Why this grade
Signal-based grade (2/7 points): listed in several sources, public source code. This reflects adoption and transparency, not a code review.
Popularity and upkeep
- GitHub stars
- 4
- Weekly npm downloads
- 34
- PyPI downloads
- 120
- Listing last refreshed
- 2026-10-28
These are public popularity signals, not a maintenance check. Look at the repository’s commit history and open issues.
Risks to watch for
- Credential & token exposure: Requires API keys or secrets in configuration. Store credentials in environment variables with read-only or minimum required scopes and rotate them regularly.
- Dependency & version pinning: Distributed via npm (@complyedge/mcp). Pin an exact release version or commit SHA rather than floating tags so upstream updates are reviewed first.
How to lower the risk
Least-privilege permissions
- Give it access only to the specific folders, accounts or projects it needs, never your whole drive or admin account.
- Use a separate, limited API key or login just for this tool so you can switch it off without affecting anything else.
Network isolation
- Run it on a work computer or sandbox account, not one holding personal or company-sensitive data.
- If your IT team can, limit which websites and services it is allowed to contact.
Monitoring
- Check its activity history or logs weekly at first, and look at what it changed or sent.
- Turn on alerts for new logins or unusual usage on any account it connects to.
Red flags to watch for
- It asks for more access than its job requires, or prompts you to paste passwords.
- It suddenly updates with new owners, or starts contacting unfamiliar websites.
Questions
How do I install @complyedge/mcp?
Run npx -y @complyedge/mcp (or uvx complyedge) in your terminal, or add the server entry to your claude_desktop_config.json or .cursor/mcp.json as shown in the Setup section on this page. Full setup docs and environment variables are in github.com/complyedge/complyedge.
Are there security reports about @complyedge/mcp?
No reports found for this package in our research (last checked 2026-10-30). @complyedge/mcp currently holds Grade C (Moderate risk signals) based on public adoption and transparency signals. Key risk areas to watch include credential & token exposure:, dependency & version pinning:.
Is @complyedge/mcp actively maintained?
@complyedge/mcp has 4 GitHub stars and 34 weekly npm downloads, with its latest repository commit pushed on 2026-10-11. Our directory data was last refreshed on 2026-10-28. Check recent commit activity, release tags, and open issues at github.com/complyedge/complyedge before pinning it in production.
What are alternatives to @complyedge/mcp?
Compare @complyedge/mcp side by side with similar MCP servers in the Related tools section on this page, or browse all MCP servers on AgentArmorHQ.
Key facts
- Type
- App connector
- Publisher
- complyedge
- Source code
- github.com/complyedge/complyedge
- Install command
- npm install @complyedge/mcp
- Est. context load
- ~750 tokens / turn (~4 tool schemas, 0.38% of 200k context)
- Popularity
- 4 GitHub stars, 34 weekly npm downloads, 120 PyPI downloads
- Last updated
- 2026-10-28
- Last graded
- 2026-10-24
Community
Discussions for @complyedge/mcp
Ask questions or share configuration tips. Governed by our Community Rules & Terms.
No posts match this filter yet.
Be the first to ask a question or share a working tip.
Check before you install, in Claude
Your assistant answers Block, Review or No known issues for any package before it installs it.
Get this check inside Claude