Tinify image tools
NPM · @TINIFY-DEV/MCP
Compress, resize, crop, and convert images with the Tinify.dev API from any MCP client.
Available components
Last scanned (9 hours ago)
Scores higher than 89% 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 Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 30 of 94 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to Stianlars1/tinify-mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 93 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability69
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 902 tokens (~180/item across 5 items; 5 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 Management83
- Stability observed for 25 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage98
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 92% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 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
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 →
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.
- 7 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 6 Nov 26 −3
- Stability: pass → 0.80 functional
- 31 Oct 26 0
- Stability: 0.97 → pass security
- 30 Oct 26 +1
- Security disclosure: unverified → fail ▼ functional
- 29 Oct 26 −1
- Security disclosure: fail → unverified ▼ functional
- Stability: pass → 0.93 functional
- 24 Oct 26 −5
- CVE-2023-54404 affects this package: high ▼ security
- Known CVEs: pass → fail ▼ security
- 19 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 18 Oct 26 0
- Security disclosure: fail → unverified ▼ functional
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 7 Nov 2026 · Analysed npm/@tinify-dev/mcp@0.1.7
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 | Stianlars1/tinify-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/Stianlars1/tinify-mcp/.github/workflows/release.yml@refs/tags/v0.1.7 |
| Rekor log index | 2344231404 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:a46441f2826b726c838a5458f2d07b04024354b2a0bb8baf05db89e55693808c68892963fed2989b571f53c59bcb41ed7f5be8a24f56d5ec7df555155 |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 94 packages
| Packages resolved | 94 |
|---|---|
| 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 →
compress_image Compress image ~216
Compress a PNG, JPEG, WebP, or AVIF image with Tinify.dev and write the smaller file next to the original (or to output_path). The API never returns more bytes than it received; when it cannot shrink the file the tool says so honestly (optimized: false) instead of pretending.
| Name | Type | Req | Description |
|---|---|---|---|
| output_path | string | – | Absolute path to write the result. Default: <name>.min.<ext> next to the input. The source image is never overwritten unless output_path points at it AND overwrite is true. |
| overwrite | boolean | – | Allow replacing an existing file at the output path. Default false. |
| path | string | yes | Absolute path to the image (png, jpg, jpeg, webp, avif; max 40 MB). |
| quality_mode | string | – | balanced (default), best_quality, or lossless. lossless is rejected for JPEG inputs. |
| target_size_kb | integer | – | Aim for a result at or below this many kilobytes (beta; server rollout). |
| Name | Type | Req | Description |
|---|---|---|---|
| change_percent | number | yes | Byte change in percent; negative means smaller. |
| height | number|null | yes | – |
| optimized | boolean|null | yes | false when the API could not shrink the file and returned the original bytes; null when the concept does not apply (resize/crop). |
| original_bytes | number | yes | Input size in bytes. |
| output_path | string|null | yes | Where the result was written, or null when nothing was written. |
| request_id | string | yes | Quote this when contacting support. |
| result_bytes | number | yes | Result size in bytes. |
| saved_bytes | number | yes | original_bytes - result_bytes. |
| width | number|null | yes | – |
| wrote | boolean | yes | Whether a file was written. |
No examples provided.
convert_image Convert image format ~184
Convert an image to AVIF, WebP, JPEG, or PNG with Tinify.dev (beta endpoint; may not be enabled on every account yet). Writes <name>.min.<new-ext> next to the original unless output_path is given. Converting to the same format is rejected by the API (same_format_conversion).
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | yes | Target format. |
| output_path | string | – | Absolute path to write the result. Default: <name>.min.<ext> next to the input. The source image is never overwritten unless output_path points at it AND overwrite is true. |
| overwrite | boolean | – | Allow replacing an existing file at the output path. Default false. |
| path | string | yes | Absolute path to the image (png, jpg, jpeg, webp, avif; max 40 MB). |
| quality_mode | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| change_percent | number | yes | Byte change in percent; negative means smaller. |
| height | number|null | yes | – |
| optimized | boolean|null | yes | false when the API could not shrink the file and returned the original bytes; null when the concept does not apply (resize/crop). |
| original_bytes | number | yes | Input size in bytes. |
| output_path | string|null | yes | Where the result was written, or null when nothing was written. |
| request_id | string | yes | Quote this when contacting support. |
| result_bytes | number | yes | Result size in bytes. |
| saved_bytes | number | yes | original_bytes - result_bytes. |
| width | number|null | yes | – |
| wrote | boolean | yes | Whether a file was written. |
No examples provided.
crop_image Crop image ~196
Crop a PNG, JPEG, WebP, or AVIF image with Tinify.dev to the given rectangle and write the result next to the original (or to output_path). The source image is never overwritten silently.
| Name | Type | Req | Description |
|---|---|---|---|
| height | integer | yes | Crop height in pixels. |
| output_path | string | – | Absolute path to write the result. Default: <name>.min.<ext> next to the input. The source image is never overwritten unless output_path points at it AND overwrite is true. |
| overwrite | boolean | – | Allow replacing an existing file at the output path. Default false. |
| path | string | yes | Absolute path to the image (png, jpg, jpeg, webp, avif; max 40 MB). |
| width | integer | yes | Crop width in pixels. |
| x | integer | yes | Left edge of the crop rectangle in pixels. |
| y | integer | yes | Top edge of the crop rectangle in pixels. |
| Name | Type | Req | Description |
|---|---|---|---|
| change_percent | number | yes | Byte change in percent; negative means smaller. |
| height | number|null | yes | – |
| optimized | boolean|null | yes | false when the API could not shrink the file and returned the original bytes; null when the concept does not apply (resize/crop). |
| original_bytes | number | yes | Input size in bytes. |
| output_path | string|null | yes | Where the result was written, or null when nothing was written. |
| request_id | string | yes | Quote this when contacting support. |
| result_bytes | number | yes | Result size in bytes. |
| saved_bytes | number | yes | original_bytes - result_bytes. |
| width | number|null | yes | – |
| wrote | boolean | yes | Whether a file was written. |
No examples provided.
get_usage Get account usage ~32
Show the Tinify.dev account's current billing-period usage: plan, period, operations included, used, and remaining.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| included | number | yes | – |
| period_end | string | yes | – |
| period_start | string | yes | – |
| plan | string | yes | – |
| remaining | number | yes | – |
| request_id | string | yes | – |
| reserved | number | yes | – |
| used | number | yes | – |
No examples provided.
resize_image Resize image ~213
Resize a PNG, JPEG, WebP, or AVIF image with Tinify.dev by width, height, or scale, and write the result next to the original (or to output_path). At least one of width, height, or scale is required. The source image is never overwritten silently.
| Name | Type | Req | Description |
|---|---|---|---|
| height | integer | – | Target height in pixels. |
| keep_aspect_ratio | boolean | – | – |
| output_path | string | – | Absolute path to write the result. Default: <name>.min.<ext> next to the input. The source image is never overwritten unless output_path points at it AND overwrite is true. |
| overwrite | boolean | – | Allow replacing an existing file at the output path. Default false. |
| path | string | yes | Absolute path to the image (png, jpg, jpeg, webp, avif; max 40 MB). |
| scale | number | – | Scale factor, e.g. 0.5 halves both dimensions. |
| width | integer | – | Target width in pixels. |
| Name | Type | Req | Description |
|---|---|---|---|
| change_percent | number | yes | Byte change in percent; negative means smaller. |
| height | number|null | yes | – |
| optimized | boolean|null | yes | false when the API could not shrink the file and returned the original bytes; null when the concept does not apply (resize/crop). |
| original_bytes | number | yes | Input size in bytes. |
| output_path | string|null | yes | Where the result was written, or null when nothing was written. |
| request_id | string | yes | Quote this when contacting support. |
| result_bytes | number | yes | Result size in bytes. |
| saved_bytes | number | yes | original_bytes - result_bytes. |
| width | number|null | yes | – |
| wrote | boolean | yes | Whether a file was written. |
No examples provided.
How do I install the Tinify image tools MCP server?
Tinify image tools runs locally as an npm package, launched with npx -y @tinify-dev/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 · @tinify-dev/mcp
claude mcp add dev-tinify-mcp -- npx -y @tinify-dev/mcp
What is the Tinify image tools MCP server?
Tinify image tools is an MCP server listed in the public MCP registry as dev.tinify/mcp. Compress, resize, crop, and convert images with the Tinify.dev API from any MCP client. This page covers its npm package (@tinify-dev/mcp).
Is the Tinify image tools MCP server safe to use?
Tinify image tools scores 86 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 7 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 Tinify image tools MCP server expose?
Tinify image tools exposes 5 tools: compress_image, resize_image, crop_image, convert_image, get_usage. Their descriptions and schemas cost roughly 841 tokens of context every time the server is loaded.
Is the Tinify image tools MCP server still maintained?
Tinify image tools is still listed as active in the MCP registry. We last reached this channel on 7 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 Tinify image tools MCP server under?
Tinify image tools declares the MIT 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 Tinify image tools MCP server?
VerifyMCP ran 16 checks on Tinify image tools, 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.