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.

Kompressr

NPM · @KOMPRESSR/MCP-SERVER · 2 COMPONENTS

Upload, optimize and manage files, wait for processing, and generate private delivery links.

+3 this week 84 Trust /100

Last scanned (22 hours ago)

Scores higher than 82% of npm servers

Category Documents and Files

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 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 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to kompressrcdn/clients). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 10 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability64
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 706 tokens (~70/item across 10 items; 10 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management53
  • Stability observed for 16 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage76
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 28% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 10 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
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.

  • 2 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

  • 31 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

  • 29 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

  • 27 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

  • 25 Oct 26 +16
    • Malware scan: unverified → pass ▲ security
  • 24 Oct 26 −4
    • Malware scan: pass → unverified ▼ security
    • Provenance: fail → pass ▲ security
    • The attested source repository moved: kompressrcdn/clients security
    • Package version: 2.0.2 → 2.0.3 functional
  • 21 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 19 Oct 26 67

    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 4 Nov 2026 · Analysed npm/@kompressr/mcp-server@2.0.3

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo kompressrcdn/clients
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/kompressrcdn/clients/.github/workflows/publish.yml@refs/heads/main
Rekor log index 3440723541
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:f84d91a7ce1279aeaeb741bee5ccb58ba8f1f751e5804b9daecb775d989659d814f7a929531ef69731a91716333400f93f027d1bb58b3771e7e3dfe26

Background: How many MCP packages publish verified provenance →

Dependencies 93 packages
Packages resolved 93
Stale 30
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 10 exposed · ~706 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
bulk_delete_assets ~54

Permanently delete 1–100 explicit asset IDs. Inspect each result: a successful HTTP request can contain failed items. Scoped keys require delete permission. No query-based deletion or undo.

NameTypeReqDescription
asset_idsarrayyes–

No output schema declared.

No examples provided.

delete_asset ~62

Permanently delete one explicit asset ID. Irreversible; no restore or cancellation. Scoped keys need explicit delete permission. Acceptance starts background cleanup; cached/offline copies may remain.

NameTypeReqDescription
asset_id–yesPositive numeric asset ID; not a URL or external customer ID

No output schema declared.

No examples provided.

generate_private_url ~63

Generate a fresh expiring URL after private upload processing and application access checks. Scoped keys only sign their own identity private uploads. Expiry does not delete the asset.

NameTypeReqDescription
asset_id–yes–
expires_ininteger––
variantstring––

No output schema declared.

No examples provided.

get_asset_deletion_status ~54

Inspect processing/deletion state and storage credits for an asset ID. File removal completion does not certify that all caches have cleared.

NameTypeReqDescription
asset_id–yesPositive numeric asset ID; not a URL or external customer ID

No output schema declared.

No examples provided.

get_asset_status ~42

Inspect processing status and delivery information. Scoped keys only read uploads owned by their identity. A URL is ready only for active processed assets.

NameTypeReqDescription
asset_id–yes–

No output schema declared.

No examples provided.

list_assets ~93

List uploaded files in the configured project, with pagination and processing/deletion filters. A scoped key lists only its identity uploads. KOMPRESSR_PROJECT_ID is required.

NameTypeReqDescription
dataobject––
deletion_statusstring––
external_idstring––
limitinteger––
pageinteger––
statusstring––
visibilitystring––

No output schema declared.

No examples provided.

register ~68

Create an account and send a verification email. The 30-day free trial includes 100 image uploads total, shared across API, SDKs, MCP and dashboard. This allowance does not renew monthly. Cannot replace an already configured runtime.

NameTypeReqDescription
emailstringyes–
passwordstringyes–

No output schema declared.

No examples provided.

upload_asset ~167

Upload a supported image, video, PDF, font or text asset. Acceptance is not readiness: wait for processed before sharing. Project-user scoped upload keys restrict uploads to their identity. The 30-day free trial includes 100 image uploads total, shared across API, SDKs, MCP and dashboard. This allowance does not renew monthly.

NameTypeReqDescription
dataobject–At most five scalar fields; UTF-8/encoded size limits apply
file_pathstring–Local file path; provide exactly one file source
file_urlstring–HTTP(S) file downloaded on the MCP machine, then uploaded
private_url_expires_ininteger––
qualitystring–Video quality only; availability depends on the plan
visibilitystring––

No output schema declared.

No examples provided.

verify_email ~33

Verify an email token and save credentials locally. Refuses to replace an already configured runtime.

NameTypeReqDescription
tokenstringyes–

No output schema declared.

No examples provided.

wait_for_asset ~70

Wait within a bounded time budget for an active upload to process. A timeout preserves the asset ID; resume rather than reupload. Private uploads need generate_private_url after readiness.

NameTypeReqDescription
asset_id–yesPositive numeric asset ID; not a URL or external customer ID
timeout_msinteger––

No output schema declared.

No examples provided.

Install

How do I install the Kompressr MCP server?

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

npm · @kompressr/mcp-server

# add to Claude Code
claude mcp add com-kompressr-kompressr -- npx -y @kompressr/mcp-server
Common questions

What is the Kompressr MCP server?

Kompressr is an MCP server listed in the public MCP registry as com.kompressr/kompressr. Upload, optimize and manage files, wait for processing, and generate private delivery links. This page covers its npm package (@kompressr/mcp-server).

Is the Kompressr MCP server safe to use?

Kompressr scores 84 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Kompressr MCP server expose?

Kompressr exposes 10 tools: register, verify_email, upload_asset, get_asset_status, list_assets, and 5 more. Their descriptions and schemas cost roughly 706 tokens of context every time the server is loaded.

Is the Kompressr MCP server still maintained?

Kompressr is still listed as active in the MCP registry. We last reached this channel on 4 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 Kompressr MCP server under?

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