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.
Warning

Malware flagged

A supply-chain scanner flagged a high-severity malware risk in this package. Treat it as unsafe to install until the finding is cleared. See Supply Chain Security in the trust breakdown.

Crumple

NPM · CRUMPLELAB

Audit AI coding agent setups and deployed apps for leaked keys, open data and risky config.

Available components

−8 this week 63 Trust /100

Last scanned (19 hours ago)

Scores higher than 32% of npm servers

Category Security

Trust breakdown (7 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 → Why this is hard to score →

Supply Chain Security55
  • Malware check failed: a supply-chain vendor flagged a high-severity malware risk. See how to fix → Fail
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
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 1 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability74
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 415 tokens (~138/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management43
  • Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (16)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

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.

  • 19 Nov 26 −12
    • Malware scan: pass → fail ▼ security
    • Malware indicator (automated code analysis): high ▼ security
    • Schema quality: pass → fail ▼ functional
    • Package version: 0.3.4 → 0.3.5 functional
  • 18 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 17 Nov 26 −11
    • Malware scan: pass → unverified ▼ security
    • Stability: unverified → 0.30 ▲ functional
    • Package version: 0.3.2 → 0.3.4 functional
  • 8 Nov 26 71

    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 21 Nov 2026 · Analysed npm/crumplelab@0.3.5

Provenance No attestation

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

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 3 exposed · ~415 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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
crumple_scan ~171

Audit an AI coding agent setup (Claude Code, Codex, Gemini CLI, Cursor, MCP config, hooks, CLAUDE.md/AGENTS.md, .env exposure) the way an attacker would. Local and instant: no key, no Docker, nothing leaves the machine. Returns a 0-100 Safe Setup score and findings, each with why it matters and the fix. With `cves: true` it also checks the MCP servers it finds (npx/uvx packages) against published vulnerabilities on osv.dev, sending only package names and versions.

NameTypeReqDescription
cvesboolean–Also check MCP server packages against osv.dev (goes online; sends only package names and versions).
pathstring–Project folder to scan. Defaults to the server's working directory.

No output schema declared.

No examples provided.

crumple_site ~194

Grade a deployed web app (built with Lovable, Bolt, v0, Replit, Emergent or by hand) A to F for what a stranger can use against it: secret keys shipped in its JavaScript, a Supabase service_role key in the browser, public source maps, no Content-Security-Policy. Each finding has a plain-English reason, what the owner must do by hand (like revoking a key), and a fix `prompt` to apply in the app's code. Call it again after fixing: `change` lists what got fixed. Reads only what the site serves to every visitor. Database checks (which Supabase tables or Firebase data anyone can read) need the owner, so tell them to run `npx crumplelab site <url> --mine` themselves.

NameTypeReqDescription
urlstringyesThe app's address, for example myapp.lovable.app

No output schema declared.

No examples provided.

crumple_traps ~50

The traps Crumple's crash test runs: each modelled on a real attack (poisoned issues, evil MCP servers, secret exfiltration, destructive commands), with its risk.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Install

How do I install the Crumple MCP server?

Crumple runs locally as an npm package, launched with npx -y crumplelab mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · crumplelab

# add to Claude Code
claude mcp add priberry-data-crumplelab -- npx -y crumplelab mcp
Common questions

What is the Crumple MCP server?

Crumple is an MCP server listed in the public MCP registry as io.github.priberry-data/crumplelab. Audit AI coding agent setups and deployed apps for leaked keys, open data and risky config. This page covers its npm package (crumplelab).

Is the Crumple MCP server safe to use?

Crumple scores 63 out of 100 on VerifyMCP. A supply-chain scanner flagged a possible malware risk on one channel of this server. We found no known CVEs affecting it as of 21 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Crumple MCP server expose?

Crumple exposes 3 tools: crumple_scan, crumple_site, crumple_traps. Their descriptions and schemas cost roughly 415 tokens of context every time the server is loaded.

Is the Crumple MCP server still maintained?

Crumple is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the Crumple MCP server under?

Crumple declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

What did VerifyMCP test on the Crumple MCP server?

VerifyMCP ran 16 checks on Crumple, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.