npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@complyedge/mcp

v0.2.3

Published

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, GPAI, GDPR, HIPAA, SOX, PCI DSS, COPPA. Runs with npx: no Python, no API key, no network call. Sett

Readme

@complyedge/mcp

npm version npm downloads license

Offline checks of prompts and answers against the bundled TrustLint rule set (63 YAML rules: EU AI Act Article 5 and Article 50, and more), with the article citation when a rule fires. It checks this prompt or output; it does not classify your system.

Each line is an alternative; pick the one you need.

npx -y @complyedge/mcp                               # this MCP server (Node)
claude mcp add complyedge -- npx -y @complyedge/mcp  # add it to Claude Code
pip install 'complyedge[mcp]'                        # the same tools as a Python MCP server: complyedge-mcp
pip install complyedge                               # Python SDK for hosted checks, no MCP server
pip install trustlint                                # offline linter CLI, no MCP server

Run offline TrustLint checks from any MCP host with Node.js:

{
  "complyedge": {
    "command": "npx",
    "args": ["-y", "@complyedge/mcp"]
  }
}

Tools

The server exposes three read-only tools.

| Tool | Returns | Notes | |---|---|---| | check_compliance | PASS / FAIL with cited findings | Checks already-produced text. Optional jurisdiction (where the end user is): EU, US, GLOBAL. GLOBAL rules always run | | scan_prompt | SAFE / RISK_DETECTED | Checks a candidate prompt before it is sent to a model | | list_rules | Rule inventory | Discovery only: does not evaluate text |

Optional: hosted sandbox with your API key

Set COMPLYEDGE_API_KEY in the server's environment and a fourth tool appears. Without it the tool is not listed and the server stays fully offline.

| Tool | Returns | Notes | |---|---|---| | sandbox_check | BLOCKED with rule ID and article citation, or ALLOWED; an allowed check also lists any rules that matched and model review cleared (cleared_by_model_review; model review runs on paid plans only, a free plan never gets a model call) | Hosted enforcement in sandbox mode (POST /v1/sandbox/check): your tenant's real rules and settings, the same verdict as production, and nothing recorded: no audit entry, no usage, and no count against your plan's daily limit (sandbox calls have their own caps: 60 a minute, 1,000 a day). One network call per check. Never evidence. An EU account's key is ce_eu_ and calls eu.api.complyedge.io; a US account's key is ce_ and calls api.complyedge.io. The region is your account's, chosen when you sign up and create your first API key. COMPLYEDGE_API_URL picks a host and does not change the account's region. To change the region later, use Request a region change in the dashboard. |

Rotating the key: mint the new one with Rotate key on the dashboard's API Key page (it asks first), update COMPLYEDGE_API_KEY (or the Authorization: Bearer header on the hosted server) and restart the client, then click Revoke previous key in the reveal. Both keys work until you revoke, so nothing has to go dark in between.

Limitations and honest scope

  • Tier-1 regex matching over a bundled YAML rule set. It does not evaluate Rego, and it is not the hosted check path. Use @complyedge/sdk for POST /v1/check and the audit record (timestamp, keyed text hash, event_id, and the rule IDs and citations when a rule fires; see https://complyedge.io/docs/audit-reconciliation.html).
  • Findings are rule matches, not legal advice, not a legal opinion, and not a regulatory classification of an AI system.
  • The corpus is bundled at build time. It is current as of the release you install, not a live regulatory feed.
  • Read-only and local. No tool writes, sends, or persists anything; the three offline tools make no network calls and need no API key. sandbox_check is the one exception, exists only when you set COMPLYEDGE_API_KEY, and the hosted sandbox it calls records nothing.

Links