Image Tools
REMOTE · BYONDR.CO
Resize, compress, convert, crop, rotate and watermark images, one at a time or in a zip.
Available components
Last scanned (5 hours ago)
Scores higher than 53% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Design and Media
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security66
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability53
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1632 tokens (~816/item across 2 items; 2 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 Management30
- Stability observed for 9 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
- 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 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (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 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.
- 2 Nov 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.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 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 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 27 Oct 26 64
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 · Probed https://byondr.co/image-tools/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=byondr.co | CN=YE1,O=Let's Encrypt,C=US | 14 Oct 2026 | 12 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 60d10f89a559e68ce71c51e702880b8d75a |
| SANs: *.byondr.co, byondr.co | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of byondr.co. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| co. | present | 7786 | 8 | Verified |
| byondr.co. | present | 2371 | 13 | Verified |
| byondr.co. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://byondr.co/image-tools/mcp | Verified | 200 | |
| http (plaintext) | http://byondr.co/image-tools/mcp | Inconclusive | 405 |
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 →
create_upload ~111
Get a one-hour signed upload URL for an image or a zip that is too large to send inline (over 3 MB; up to 100 MB here) or that already sits on disk. PUT the raw bytes to upload_url with a Content-Length header, then pass file_id to process_images. Free.
| Name | Type | Req | Description |
|---|---|---|---|
| bytes | integer | yes | Exact size of the file you will upload, in bytes (at most 100 MB) |
| filename | string | – | Original file name, used to name the output |
| Name | Type | Req | Description |
|---|---|---|---|
| expires_at | string | yes | – |
| file_id | string | yes | – |
| max_bytes | integer | yes | – |
| method | string | yes | – |
| upload_url | string | yes | – |
No examples provided.
process_images ~1,397
Resize, crop, rotate, flip, compress (to a file size with target_bytes), convert (jpeg, png, webp, avif), strip EXIF and GPS metadata from, and watermark (text, logo or both) one image or a zip of up to 50 images (up to 500 files per zip; files that are not supported images are skipped and listed). Crops are in pixels by default; for a zip of different sizes use crop_unit "percent" or crop_aspect, which are worked out per image. Give exactly one source: file_id (from create_upload), url (public https) or data_base64 (up to 3 MB inline; use create_upload, up to 100 MB, or url above that). One image in returns one image; a zip returns a zip. AVIF output is scaled down to fit 1,200 px on the longest side and WebP output to 36 megapixels. Returns a 24-hour download_url with the size and format of every output, and for each output the kinds of metadata found in the input and left in the output (location, date, camera, serial number, ...) and whether the colour profile was kept; kinds only, never the values. keep_date and keep_copyright write back the EXIF date taken and copyright after stripping. Large zips can take up to a minute; use a client timeout of at least 120 s. Free. Daily quotas are counted per caller in output megapixels; see start.md.
| Name | Type | Req | Description |
|---|---|---|---|
| background | string | – | JPEG only: colour under transparent areas, #rrggbb |
| crop_aspect | string | – | Instead of the four crop fields: the largest centered crop of this width:height ratio, per image |
| crop_height | number | – | Crop: height (px, or % of the height with crop_unit percent) |
| crop_left | number | – | Crop: left edge (px, or % of the width with crop_unit percent) |
| crop_top | number | – | Crop: top edge (px, or % of the height with crop_unit percent) |
| crop_unit | string | – | Unit of the four crop fields: px (whole pixels) or percent (0-100 of each image, so a zip of different sizes gets the same part of every image) |
| crop_width | number | – | Crop: width (px, or % of the width with crop_unit percent) |
| data_base64 | string | – | Base64 bytes of an image or zip, up to 3 MB decoded; use create_upload (up to 100 MB) or url above that |
| file_id | string | – | Image or zip file (up to 25 MB on this page) |
| filename | string | – | Name for the output when the source has none |
| fit | string | – | How to fit into width x height: scale-down never enlarges; cover fills and crops; pad adds borders |
| flip | string | – | Flip: h = horizontal, v = vertical, hv = both |
| format | string | – | Output format (keep turns HEIC into JPEG and GIF into PNG) |
| height | integer | – | Height in pixels |
| keep_copyright | boolean | – | With strip_metadata: keep the EXIF Copyright tag. XMP and IPTC rights are not kept |
| keep_date | boolean | – | With strip_metadata: keep the EXIF date taken (DateTimeOriginal and DateTimeDigitized, with their time zone and fraction of a second) so photos still sort by date. A date and time taken found only in… |
| max_side | integer | – | Instead of width and height: the longest side in pixels, per image, so portrait and landscape images both get it on their long edge. Never enlarges unless fit is contain |
| quality | integer | – | Quality 1-100 for JPEG, WebP and AVIF; lower is smaller. Ignored with target_bytes |
| resize_unit | string | – | Unit of width and height: px, or percent (1-1000) of each image's own size, so a zip of different sizes is scaled alike. Over 100 enlarges only with fit contain |
| rotate | number | – | Rotate clockwise (degrees) |
| strip_metadata | boolean | – | Remove EXIF, GPS location and camera data |
| target_bytes | integer | – | Instead of quality: the most bytes each output may have (10,000-50,000,000; 1 MB = 1,000,000), for upload forms with a size limit. Uses the highest quality from 45 to 92 that fits; if even 45 is too… |
| url | string | – | Or a public https URL of an image or zip |
| watermark_color | string | – | Watermark color, #rrggbb |
| watermark_image | string | – | Logo for the watermark, with or instead of watermark_text: a file_id from create_upload, a public https url, or data:image/png;base64,... (up to 1 MB inline; an inline image and logo share the 3 MB i… |
| watermark_image_size | number | – | Logo width, % of each image's width (2-50). Default 15 |
| watermark_opacity | number | – | Watermark opacity, 0.05 to 1 |
| watermark_position | string | – | Watermark position; custom places the centre of the text at watermark_x, watermark_y |
| watermark_size | number | – | Watermark font size: px (8-400, whole numbers) or, with watermark_size_unit percent, % of each image's width (0.5-20, giving 12-1000 px). Default 4% of the width |
| watermark_size_unit | string | – | Unit of watermark_size: px, or percent of each image's width (so a zip of different sizes gets the same relative size) |
| watermark_text | string | – | Watermark text |
| watermark_x | number | – | With watermark_position custom: the centre of the text, % of each image's width from the left (0-100) |
| watermark_y | number | – | With watermark_position custom: the centre of the text, % of each image's height from the top (0-100) |
| width | integer | – | Width in pixels |
| Name | Type | Req | Description |
|---|---|---|---|
| bytes | integer | yes | – |
| content_type | string | yes | – |
| download_url | string | yes | – |
| expires_at | string | yes | – |
| items | array | yes | – |
| kind | string | yes | – |
| megapixels | number | yes | – |
| skipped | array | yes | – |
No examples provided.
How do I install the Image Tools MCP server?
Image Tools is a hosted endpoint at https://byondr.co/image-tools/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · byondr.co
claude mcp add --transport http co-byondr-image-tools 'https://byondr.co/image-tools/mcp'
What is the Image Tools MCP server?
Image Tools is an MCP server listed in the public MCP registry as co.byondr/image-tools. Resize, compress, convert, crop, rotate and watermark images, one at a time or in a zip. This page covers its hosted endpoint (https://byondr.co/image-tools/mcp).
Is the Image Tools MCP server safe to use?
Image Tools scores 68 out of 100 on VerifyMCP. 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 Image Tools MCP server expose?
Image Tools exposes 2 tools: process_images, create_upload. Their descriptions and schemas cost roughly 1,508 tokens of context every time the server is loaded.
Does the Image Tools MCP server require authentication?
No. We connected to Image Tools without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Image Tools MCP server still maintained?
Image Tools 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.