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.

Tinify image tools

NPM · @TINIFY-DEV/MCP · SCANNED SEP 21

Compress, resize, crop, and convert images with the Tinify.dev API from any MCP client.

Available components

0 this week 91 Trust /100
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
  • 31 of 97 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 46 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
Install

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

# add to Claude Code
claude mcp add dev-tinify-mcp -- npx -y @tinify-dev/mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "dev-tinify-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@tinify-dev/mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "dev-tinify-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@tinify-dev/mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add dev-tinify-mcp -- npx -y @tinify-dev/mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dev-tinify-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@tinify-dev/mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add dev-tinify-mcp --command npx --arg -y --arg @tinify-dev/mcp
# ~/.hermes/config.yaml
mcp_servers:
  dev-tinify-mcp:
    command: "npx"
    args: ["-y", "@tinify-dev/mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "dev-tinify-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@tinify-dev/mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add dev-tinify-mcp -t stdio -c npx -a -y @tinify-dev/mcp
// mcp.json
{
  "mcpServers": {
    "dev-tinify-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@tinify-dev/mcp"
      ]
    }
  }
}
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.

  • 21 Sept 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.

  • 20 Sept 26 −3
    • Security disclosure: unverified → fail functional
    • Stability: pass → 0.80 functional
  • 19 Sept 26 0
    • Stability: 0.97 → pass security
    • Security disclosure: fail → unverified functional
  • 18 Sept 26 +1

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

  • 17 Sept 26 0
    • Security disclosure: unverified → fail functional
  • 16 Sept 26 +1
    • Security disclosure: fail → unverified functional
  • 14 Sept 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.

  • 13 Sept 26 −3
    • Stability: pass → 0.80 functional
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 Sept 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 https://slsa.dev/provenance/v1
Subject digest sha512:a46441f2826b726c838a5458f2d07b04024354b2a0bb8baf05db89e55693808c68892963fed2989b571f53c59bcb41ed7f5be8a24f56d5ec7df555155

Background: How many MCP packages publish verified provenance →

Dependencies 97 packages
Packages resolved 97
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 5 exposed · ~841 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
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.

NameTypeReqDescription
output_pathstringAbsolute 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.
overwritebooleanAllow replacing an existing file at the output path. Default false.
pathstringyesAbsolute path to the image (png, jpg, jpeg, webp, avif; max 40 MB).
quality_modestringbalanced (default), best_quality, or lossless. lossless is rejected for JPEG inputs.
target_size_kbintegerAim for a result at or below this many kilobytes (beta; server rollout).
NameTypeReqDescription
change_percentnumberyesByte change in percent; negative means smaller.
heightnumber|nullyes
optimizedboolean|nullyesfalse when the API could not shrink the file and returned the original bytes; null when the concept does not apply (resize/crop).
original_bytesnumberyesInput size in bytes.
output_pathstring|nullyesWhere the result was written, or null when nothing was written.
request_idstringyesQuote this when contacting support.
result_bytesnumberyesResult size in bytes.
saved_bytesnumberyesoriginal_bytes - result_bytes.
widthnumber|nullyes
wrotebooleanyesWhether a file was written.

No examples provided.

convert_image ~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).

NameTypeReqDescription
formatstringyesTarget format.
output_pathstringAbsolute 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.
overwritebooleanAllow replacing an existing file at the output path. Default false.
pathstringyesAbsolute path to the image (png, jpg, jpeg, webp, avif; max 40 MB).
quality_modestring
NameTypeReqDescription
change_percentnumberyesByte change in percent; negative means smaller.
heightnumber|nullyes
optimizedboolean|nullyesfalse when the API could not shrink the file and returned the original bytes; null when the concept does not apply (resize/crop).
original_bytesnumberyesInput size in bytes.
output_pathstring|nullyesWhere the result was written, or null when nothing was written.
request_idstringyesQuote this when contacting support.
result_bytesnumberyesResult size in bytes.
saved_bytesnumberyesoriginal_bytes - result_bytes.
widthnumber|nullyes
wrotebooleanyesWhether a file was written.

No examples provided.

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.

NameTypeReqDescription
heightintegeryesCrop height in pixels.
output_pathstringAbsolute 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.
overwritebooleanAllow replacing an existing file at the output path. Default false.
pathstringyesAbsolute path to the image (png, jpg, jpeg, webp, avif; max 40 MB).
widthintegeryesCrop width in pixels.
xintegeryesLeft edge of the crop rectangle in pixels.
yintegeryesTop edge of the crop rectangle in pixels.
NameTypeReqDescription
change_percentnumberyesByte change in percent; negative means smaller.
heightnumber|nullyes
optimizedboolean|nullyesfalse when the API could not shrink the file and returned the original bytes; null when the concept does not apply (resize/crop).
original_bytesnumberyesInput size in bytes.
output_pathstring|nullyesWhere the result was written, or null when nothing was written.
request_idstringyesQuote this when contacting support.
result_bytesnumberyesResult size in bytes.
saved_bytesnumberyesoriginal_bytes - result_bytes.
widthnumber|nullyes
wrotebooleanyesWhether a file was written.

No examples provided.

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

NameTypeReqDescription
includednumberyes
period_endstringyes
period_startstringyes
planstringyes
remainingnumberyes
request_idstringyes
reservednumberyes
usednumberyes

No examples provided.

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.

NameTypeReqDescription
heightintegerTarget height in pixels.
keep_aspect_ratioboolean
output_pathstringAbsolute 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.
overwritebooleanAllow replacing an existing file at the output path. Default false.
pathstringyesAbsolute path to the image (png, jpg, jpeg, webp, avif; max 40 MB).
scalenumberScale factor, e.g. 0.5 halves both dimensions.
widthintegerTarget width in pixels.
NameTypeReqDescription
change_percentnumberyesByte change in percent; negative means smaller.
heightnumber|nullyes
optimizedboolean|nullyesfalse when the API could not shrink the file and returned the original bytes; null when the concept does not apply (resize/crop).
original_bytesnumberyesInput size in bytes.
output_pathstring|nullyesWhere the result was written, or null when nothing was written.
request_idstringyesQuote this when contacting support.
result_bytesnumberyesResult size in bytes.
saved_bytesnumberyesoriginal_bytes - result_bytes.
widthnumber|nullyes
wrotebooleanyesWhether a file was written.

No examples provided.

Common questions

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 91 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 September 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 21 September 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.