io.github.crabcrop/crabcrop
NPM · @CRABCROP/MCP
Sign and explain crabcrop image URLs, fetch processed-image metadata, and purge cached results.
Available components
Last scanned (6 hours ago)
Scores higher than 32% of npm servers
Category Design and Media
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 Security75
- No malware found by supply-chain analysis.Pass
- Known CVEs were checked across the 0 of 1 dependencies we could resolve, so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- Dependency health was assessed across the 0 of 1 dependencies we could resolve, so this covers what we could see, not the whole tree. 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 10 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability73
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 649 tokens (~162/item across 4 items; 4 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 Management37
- Stability observed for 11 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 Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "purge_result" implies "purge" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
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.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Oct 26 +2
- Stability: unverified → 0.07 ▲ functional
- Security disclosure: fail → pass ▲ functional
- 26 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 25 Oct 26 43
First indexed and scored.
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 npm/@crabcrop/mcp@0.1.0
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 | Partial |
The dependency tree was only partially resolved, so these counts may be incomplete.
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 →
explain_url ~75
Parse a crabcrop URL back into its pieces: the signature kind, each operation segment with a plain-language explanation, exp: rendered as a UTC instant with an expired verdict, and the source. Malformed segments and unknown filters are reported as errors.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | The full crabcrop URL or bare path. |
No output schema declared.
No examples provided.
fetch_meta ~100
Fetch the crabcrop meta JSON for a URL (the processed result's width, height, format, byte size, quality, and placeholder data on request). The URL must already be signed if the server requires signatures. For safety the URL's origin must match CRABCROP_BASE: this tool will not fetch arbitrary URLs.
| Name | Type | Req | Description |
|---|---|---|---|
| placeholders | boolean | – | Also request placeholder data (default false). |
| url | string | yes | The full crabcrop URL. |
No output schema declared.
No examples provided.
purge_result ~202
Evict a cached result from a crabcrop server. The path is the cached URL's remainder after its signature (operations and source; a preset URL works as-is, the server expands it). Requires the signing secret (argument or CRABCROP_SECRET). Returns how many entries were removed. For safety the request only goes to the configured CRABCROP_BASE origin (a base argument must match it) and paths with dot segments are refused: this tool will not POST to arbitrary endpoints.
| Name | Type | Req | Description |
|---|---|---|---|
| base | string | – | crabcrop endpoint origin. Defaults to CRABCROP_BASE; its origin must match CRABCROP_BASE. |
| path | string | yes | Remainder of the cached URL, e.g. "300x200/https://example.com/a.jpg". |
| secret | string | – | Signing secret. Defaults to CRABCROP_SECRET. Sensitive, deprecated: prefer the CRABCROP_SECRET environment variable; a per-call secret is kept in client transcripts. |
No output schema declared.
No examples provided.
sign_url ~272
Build and sign a crabcrop URL from an operation string and a source. Returns the full URL. Uses CRABCROP_BASE / CRABCROP_SECRET from the environment unless base/secret arguments override them; with no secret the URL carries the literal `unsafe` signature segment. Prefer the environment for the secret: per-call secret arguments are deprecated.
| Name | Type | Req | Description |
|---|---|---|---|
| base | string | – | crabcrop endpoint origin. Defaults to CRABCROP_BASE. |
| expires | number | – | Optional unix-seconds expiry, emitted as an exp: segment. |
| keyId | string | – | Optional key ID stamped on the signature segment (`<key-id>:<tag>`) for servers running a secret rotation; they verify a keyed segment against the named key only. |
| operations | string | yes | Operation string, e.g. "crop:1200x630:smart/filters:format(webp)"; may be empty and may contain preset: references. |
| secret | string | – | Signing secret. Defaults to CRABCROP_SECRET; omit for unsafe URLs. Sensitive, deprecated: prefer the CRABCROP_SECRET environment variable; a per-call secret is kept in client transcripts. |
| source | string | yes | Source locator: an http(s) URL, s3://bucket/key, gs://bucket/key, or file:// path. |
No output schema declared.
No examples provided.
How do I install the io.github.crabcrop/crabcrop MCP server?
io.github.crabcrop/crabcrop runs locally as an npm package, launched with npx -y @crabcrop/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 · @crabcrop/mcp
claude mcp add crabcrop-crabcrop -- npx -y @crabcrop/mcp
What is the io.github.crabcrop/crabcrop MCP server?
io.github.crabcrop/crabcrop is an MCP server listed in the public MCP registry as io.github.crabcrop/crabcrop. Sign and explain crabcrop image URLs, fetch processed-image metadata, and purge cached results. This page covers its npm package (@crabcrop/mcp).
Is the io.github.crabcrop/crabcrop MCP server safe to use?
io.github.crabcrop/crabcrop scores 64 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 io.github.crabcrop/crabcrop MCP server expose?
io.github.crabcrop/crabcrop exposes 4 tools: sign_url, explain_url, fetch_meta, purge_result. Their descriptions and schemas cost roughly 649 tokens of context every time the server is loaded.
Is the io.github.crabcrop/crabcrop MCP server still maintained?
io.github.crabcrop/crabcrop is still listed as active in the MCP registry. We last reached this channel on 5 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 io.github.crabcrop/crabcrop MCP server under?
io.github.crabcrop/crabcrop declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.