Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

ComplyEdge TrustLint

NPM · @COMPLYEDGE/MCP · 2 COMPONENTS · SCANNED AUG 17

Check prompts against ComplyEdge TrustLint offline rules with article-cited findings.

Available components

npm · @complyedge/mcp 70 pypi · complyedge 40
70 Trust /100
Trust breakdown (6 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score →

Supply Chain Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 30 of 99 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
  • Clear OSI-approved license (Apache-2.0).Pass
  • Actively maintained (last published 0 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability81
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 149 tokens (~49/item across 3 items; 3 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

npm · @complyedge/mcp

# add to Claude Code
claude mcp add complyedge-complyedge -- npx -y @complyedge/mcp
# add to Codex CLI
codex mcp add complyedge-complyedge -- npx -y @complyedge/mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "complyedge-complyedge": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@complyedge/mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add complyedge-complyedge --command npx --arg -y --arg @complyedge/mcp
# ~/.hermes/config.yaml
mcp_servers:
  complyedge-complyedge:
    command: "npx"
    args: ["-y", "@complyedge/mcp"]
// mcp.json
{
  "mcpServers": {
    "complyedge-complyedge": {
      "command": "npx",
      "args": [
        "-y",
        "@complyedge/mcp"
      ]
    }
  }
}
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 16 Aug 26 70

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 17 Aug 2026 · Analysed npm/@complyedge/mcp@0.1.1

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm
Dependencies 99 packages
Packages resolved 99
Stale 30
Tree resolution Complete
MCP tools · 3 exposed · ~149 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.

Tool Tokens
check_compliance ~59

Check already-produced text against the offline TrustLint corpus. Returns PASS or FAIL with cited findings. No network call or API key is required.

NameTypeReqDescription
jurisdictionstring–Optional corpus scope.
textstringyesNon-empty text to evaluate.

No output schema declared.

No examples provided.

list_rules ~40

List offline TrustLint rules. This discovers rule coverage; it does not evaluate text or return a compliance verdict.

NameTypeReqDescription
jurisdictionstring–Optional corpus scope.

No output schema declared.

No examples provided.

scan_prompt ~50

Scan a candidate prompt before generation against the offline TrustLint corpus. Returns SAFE or RISK_DETECTED. No network call or API key is required.

NameTypeReqDescription
promptstringyesNon-empty prompt to evaluate.

No output schema declared.

No examples provided.