Kompressr
MCPB · KOMPRESSR-2.0.3.MCPB · 2 COMPONENTS
Upload, optimize and manage files, wait for processing, and generate private delivery links.
Available components
Last scanned (8 hours ago)
Scores higher than 84% of MCPB servers
Category Documents and Files
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 Security23
- No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
- Known CVEs were checked across the 93 of 93 dependencies we could resolve, so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- 30 of 93 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 (MIT).Pass
- Actively maintained (last published 11 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 Management57
- Stability observed for 17 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
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.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 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 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 24 Oct 26 0
- Stability: 0.13 → unverified ▼ security
- 22 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
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 5 Nov 2026 · Analysed mcpb/https://github.com/kompressrcdn/clients/releases/download/mcp-server-v2.0.3/kompressr-2.0.3.mcpb
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | mcpb |
| Reason | No attestation published |
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 →
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 →
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.
| Name | Type | Req | Description |
|---|---|---|---|
| asset_ids | array | yes | – |
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.
| Name | Type | Req | Description |
|---|---|---|---|
| asset_id | – | yes | Positive 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.
| Name | Type | Req | Description |
|---|---|---|---|
| asset_id | – | yes | – |
| expires_in | integer | – | – |
| variant | string | – | – |
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.
| Name | Type | Req | Description |
|---|---|---|---|
| asset_id | – | yes | Positive 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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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.
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | – | – |
| deletion_status | string | – | – |
| external_id | string | – | – |
| limit | integer | – | – |
| page | integer | – | – |
| status | string | – | – |
| visibility | string | – | – |
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.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | – | |
| password | string | yes | – |
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.
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | – | At most five scalar fields; UTF-8/encoded size limits apply |
| file_path | string | – | Local file path; provide exactly one file source |
| file_url | string | – | HTTP(S) file downloaded on the MCP machine, then uploaded |
| private_url_expires_in | integer | – | – |
| quality | string | – | Video quality only; availability depends on the plan |
| visibility | string | – | – |
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.
| Name | Type | Req | Description |
|---|---|---|---|
| token | string | yes | – |
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.
| Name | Type | Req | Description |
|---|---|---|---|
| asset_id | – | yes | Positive numeric asset ID; not a URL or external customer ID |
| timeout_ms | integer | – | – |
No output schema declared.
No examples provided.
How do I install the Kompressr MCP server?
Kompressr ships as an MCPB bundle, a single file you download and open in an MCP host that supports MCPB bundles, such as Claude Desktop. The host reads the launch command from the bundle's own manifest, so there is no command to copy. Before opening it, check the file's SHA-256 matches the one the MCP registry declares for it, 207031d72bbe2b3cc5c8373024bdb86c19841e92387c665bd9d7457100639f97; the commands to do that are on this page. If it does not match, do not open it.
mcpb · kompressr-2.0.3.mcpb
Download bundleCheck the download matches the SHA-256 the MCP registry declares before you open it. If it does not match, do not open the file.
SHA-256
207031d72bbe2b3cc5c8373024bdb86c19841e92387c665bd9d7457100639f97
macOS / Linux
echo "207031d72bbe2b3cc5c8373024bdb86c19841e92387c665bd9d7457100639f97 kompressr-2.0.3.mcpb" | shasum -a 256 -c
Windows (PowerShell)
(Get-FileHash -Algorithm SHA256 .\kompressr-2.0.3.mcpb).Hash -eq "207031d72bbe2b3cc5c8373024bdb86c19841e92387c665bd9d7457100639f97"
Run it in the folder you saved the bundle to, then open the file with an MCPB-capable host such as Claude Desktop.
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 MCPB bundle (https://github.com/kompressrcdn/clients/releases/download/mcp-server-v2.0.3/kompressr-2.0.3.mcpb).
Is the Kompressr MCP server safe to use?
Kompressr scores 52 out of 100 on VerifyMCP. 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 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.
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.