TinyPNG MCP by usefulapi
io.usefulapi/tinypngusefulapi.iostreamable-httpv1.27.4Scanned
Compress, resize and convert images with TinyPNG by URL, and check this month's compression count.
4 tools: 2 change things and 2 only read.
- Reads private data · 1
- Reads text others write · 4
- Can send data out · 1
- No findings
The remote endpoint did not answer the last look. Remote posture
Anlyon alternative
2 of these tools change something. Run those as governed actions.
Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.
Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.
Import an OpenAPI spec →What the TinyPNG MCP by usefulapi can do
The TinyPNG MCP by usefulapi is published by usefulapi.io, a domain the MCP Registry verified. It has 4 tools. It can create or change data (2 tools: tinypng_compress_image and tinypng_transform_image), but cannot delete data. 2 tools only read.
1 tool reads private data (tinypng_get_usage); 4 tools bring in text other people can write (tinypng_compress_image, tinypng_transform_image, tinypng_download_image and 1 more); 1 tool can send data out of your system (tinypng_compress_image). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Last scanned Oct 25, 2026, version 1.27.4.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
4 tools
Changes things 2Claude Code: ask
tinypng_compress_imageWRITE (uses quota): ask TinyPNG (Tinify) to fetch a public image by URL and compress it (JPEG, PNG, WebP, AVIF or JPEG XL).Reads text others writeCan send data outNo findings
Why it is in this group
- The description's first verb is "write": a word for a change.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
Description, as the server wrote it WRITE (uses quota): ask TinyPNG (Tinify) to fetch a public image by URL and compress it (JPEG, PNG, WebP, AVIF or JPEG XL). Returns the output_url (Tinify's Location address of the compressed image), the compressed size and type, the savings when the input size is known, and the Compression-Count header (compressions used this month). The image is stored by Tinify for about 48 hours; output_url needs your API key, so use tinypng_download_image to get the bytes and tinypng_transform_image to resize, convert or keep metadata. Each compression counts against the monthly quota of your Tinify API key (the free plan includes 500 per month); resizing and converting count one extra compression each. POST /shrink.
Annotations the server declares
- title: Compress an image from a URL
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
tinypng_transform_imageWRITE (uses quota): apply a resize, a format conversion and/or metadata preservation to an image compressed earlier (the output_url from tinypng_compress_image, valid about 48 hour…Reads text others writeNo findings
Why it is in this group
- The description's first verb is "write": a word for a change.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it WRITE (uses quota): apply a resize, a format conversion and/or metadata preservation to an image compressed earlier (the output_url from tinypng_compress_image, valid about 48 hours). Returns the resulting type, byte size, width, height and Compression-Count; the image itself is returned too when include_image is true and it is under 1 MB. Resize: method scale (give width OR height), or fit / cover / thumb (give width AND height); images are never scaled up. Convert: one or more of image/webp, image/jpeg, image/png, image/avif, image/jxl (several = the smallest is returned) or */* (the smallest of WebP, JPEG, PNG); converting a transparent image to JPEG needs a background colour. Preserve: copyright, creation, location (location is JPEG only) keeps that metadata, which makes the file slightly larger. Each call is a fresh request: resize and convert each count one extra compression on your monthly Tinify quota, preserve is free. Tinify returns the bytes only (no new URL), so only include_image gives you the transformed file, and only when it is under 1 MB. POST /output/{id}.
Annotations the server declares
- title: Resize, convert or keep metadata of a compressed image
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
Only reads 2Show 2 read-only tools
tinypng_download_imageFetch the compressed image of an earlier tinypng_compress_image (its output_url, valid about 48 hours) and return it as an image with its type, byte size, width and height.Reads text others writeNo findings
Why it is in this group
- The description's first verb is "fetch": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- untrusted-inputThe description's first sentence says "fetch" and "url": it reads web pages, which anyone can write.
Description, as the server wrote it Fetch the compressed image of an earlier tinypng_compress_image (its output_url, valid about 48 hours) and return it as an image with its type, byte size, width and height. Images over 1 MB are described but not returned inline. Downloading does not use extra compression quota. GET /output/{id}.
Annotations the server declares
- title: Download a compressed image
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true
tinypng_get_usageHow many compressions your Tinify API key has used this calendar month (the Compression-Count header), and whether the key is valid.Reads private dataReads text others writeNo findings
Why it is in this group
- The name "tinypng_get_usage" says "get": a word for reading.
What it can reach
- private-dataThe description's first sentence says "calendar": it reads calendars.
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it How many compressions your Tinify API key has used this calendar month (the Compression-Count header), and whether the key is valid. The check sends an empty request that Tinify refuses, so nothing is compressed and no quota is used. Compare with your Tinify plan (the free plan includes 500 per month). POST /shrink with no body.
Annotations the server declares
- title: Get compression usage this month
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
4 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 1 outbound tool breaks every one.
- Reads private data1
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write4
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out1
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
{
"permissions": {
"deny": [
"mcp__tinypng__tinypng_compress_image"
]
}
}Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:38 UTC, unchanged since Oct 29, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- no
- HTTP status of an anonymous initialize
- not observed
- tools/list served without credentials
- no
- Tools that change things, listed without credentials
- 0
- Protocol version
- not observed
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
The probe stopped: The server redirected a POST to a different request.
Posture changes
- Oct 29, 2026
- Reachable: yes to no
- HTTP status of an anonymous initialize: 200 to none
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 2 to 0
- Protocol version: 2025-06-18 to none
- RFC 9728 protected resource metadata: https://tinypng.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
- Authorization servers: https://tinypng.usefulapi.io to none
- Dynamic client registration: yes to not observed
- Client ID metadata documents: no to not observed
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
PostureRemote posture changed. Reachable: yes -> no; HTTP status of an anonymous initialize: 200 -> none; tools/list served without credentials: yes -> no (and 6 more).View diff
- Reachable: yes to no
- HTTP status of an anonymous initialize: 200 to none
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 2 to 0
- Protocol version: 2025-06-18 to none
- RFC 9728 protected resource metadata: https://tinypng.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
- Authorization servers: https://tinypng.usefulapi.io to none
- Dynamic client registration: yes to not observed
- Client ID metadata documents: no to not observed
Install
Pinned to version 1.27.4. Values in angle brackets are yours to fill in.
claude mcp add --transport http tinypng https://tinypng.usefulapi.io/mcpclaude mcp add --transport http tinypng https://tinypng.usefulapi.io/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__tinypng__tinypng_download_image",
"mcp__tinypng__tinypng_get_usage"
],
"ask": [
"mcp__tinypng__tinypng_compress_image",
"mcp__tinypng__tinypng_transform_image"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as tinypng. Review it before you use it.
Capability tags behind 4 rules
- mcp__tinypng__tinypng_compress_image untrusted-input, outbound
- mcp__tinypng__tinypng_transform_image untrusted-input
- mcp__tinypng__tinypng_download_image untrusted-input
- mcp__tinypng__tinypng_get_usage private-data, untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.usefulapi/tinypng/verify?hash=2561d33bc9d4a3e6f6bb3e8389ed0a9c991b48ee3a679da0ada2f868cf44d78e" | jq -e '.changed == false'Pinned hash 2561d33bc9d4, from Oct 25, 2026, 23:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.usefulapi/tinypng/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.usefulapi/tinypng)Source: MCP Registry · repository. Synced Nov 18, 2026, 11:19 UTC.
TinyPNG MCP by usefulapi: questions and answers
Answered from the scan above, not from the publisher's description.
Is the TinyPNG MCP by usefulapi safe?
- No scan can promise that. What its definitions show: 4 tools, 2 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the TinyPNG MCP by usefulapi delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the TinyPNG MCP by usefulapi do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the TinyPNG MCP by usefulapi have?
- 4 tools: 2 write, 2 read. tinypng_compress_image, tinypng_transform_image, tinypng_download_image and tinypng_get_usage.
Does the TinyPNG MCP by usefulapi need sign-in or OAuth?
- Its remote endpoint did not answer the last anonymous look.
Does the TinyPNG MCP by usefulapi send data to outside services?
- 1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): tinypng_compress_image.
Has the TinyPNG MCP by usefulapi changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Oct 25, 2026.