# Imagelato Image Processing (remote · mcp.imagelato.com)

Set up image processing templates and check batch results, projects and webhooks.

- Trust score: 92/100 (high trust)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `mcp.imagelato.com`: 92/100 (this document), [markdown](https://verifymcp.io/servers/com-imagelato-imagelato/mcp.md), [page](https://verifymcp.io/servers/com-imagelato-imagelato/mcp)

## Channel facts

- Endpoint: `https://mcp.imagelato.com/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `0.1.1`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 92/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server supports Client ID Metadata Documents, the current MCP client-registration mechanism.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 71/100
  - 67% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 3044 tokens (~152/item across 20 items; 14 tools + 6 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 16 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).
  - Supports UI / widget rendering.

## Install

### How do I install the Imagelato Image Processing MCP server?

Imagelato Image Processing is a hosted endpoint at https://mcp.imagelato.com/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.

### Claude

```bash
claude mcp add --transport http com-imagelato-imagelato 'https://mcp.imagelato.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-imagelato-imagelato": {
      "url": "https://mcp.imagelato.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-imagelato-imagelato": {
      "type": "http",
      "url": "https://mcp.imagelato.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-imagelato-imagelato]
url = "https://mcp.imagelato.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-imagelato-imagelato": {
      "type": "remote",
      "url": "https://mcp.imagelato.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-imagelato-imagelato --url 'https://mcp.imagelato.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-imagelato-imagelato:
    url: "https://mcp.imagelato.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-imagelato-imagelato": {
      "Transport": "http",
      "Url": "https://mcp.imagelato.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-imagelato-imagelato -t streamable-http -u 'https://mcp.imagelato.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-imagelato-imagelato": {
      "type": "http",
      "url": "https://mcp.imagelato.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 92, +1)

- [security] Stability: 0.97 → pass

### 2026-11-04 (score 91, −1)

- [functional] Stability: pass → 0.97

### 2026-10-25 (score 92, +1)

- [security] Stability: 0.97 → pass

### 2026-10-23 (score 91, +1)

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

### 2026-10-21 (score 90, +1)

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

### 2026-10-19 (score 89, +1)

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

### 2026-10-18 (score 88, 0)

- [security] Tool “add_project” rewrote its description, which is the text the model reads
- [security] Tool “add_template” rewrote its description, which is the text the model reads
- [security] Tool “delete_batch” rewrote its description, which is the text the model reads
- [security] Tool “get_batch” rewrote its description, which is the text the model reads
- [security] Tool “get_project” rewrote its description, which is the text the model reads
- [security] Tool “get_template” rewrote its description, which is the text the model reads
- [security] Tool “list_batches” rewrote its description, which is the text the model reads
- [security] Tool “list_projects” rewrote its description, which is the text the model reads
- [security] Tool “list_team_members” rewrote its description, which is the text the model reads
- [security] Tool “list_templates” rewrote its description, which is the text the model reads
- [security] Tool “list_webhook_subscriptions” rewrote its description, which is the text the model reads
- [security] Tool “open_imagelato” rewrote its description, which is the text the model reads
- [security] Tool “show_project_overview” rewrote its description, which is the text the model reads
- [security] Tool “update_template” rewrote its description, which is the text the model reads

### 2026-10-17 (score 88, +1)

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

## MCP tools (14)

### `list_projects` (~101 tokens)

List your image projects

Use this when the user wants to list image projects accessible to the connected Imagelato account and retrieve identifiers for subsequent project operations. Returns each project's id and name, 25 per page by default. Not for a project's processed images.

Input parameters:

- `cursor` (string): The nextCursor of the previous page with the same filters; absent for the first page
- `limit` (integer): Results per page, from 1 to 100; defaults to 25

Output parameters:

- `hasMore` (boolean)
- `items` (array)
- `nextCursor`: Cursor for the next page; null on the last page
- `total` (integer): Matching records across all pages

### `get_project` (~76 tokens)

Get image project details

Use this when the user wants to read metadata for one Imagelato image project selected by its exact name or identifier. Returns its id, name, logo URL and created and edited times, or not-found. Not for a quick look at its latest processed images.

Input parameters:

- `projectIdOrName` (string, required): Exact project id or name

Output parameters:

- `project`
- `status` (string)

### `add_project` (~77 tokens)

Create an image project

Use this when the user wants to create one Imagelato image project to group processed batches and resize presets. Returns the new project's id, name and creation time and fires the project.created webhook. Each call creates another project. Not for adding a resize preset.

Input parameters:

- `name` (string, required): Project name, from 1 to 120 characters

Output parameters:

- `project` (object)
- `status` (string)

### `list_batches` (~127 tokens)

List processed image batches

Use this when the user wants to list existing processed-image batch metadata in Imagelato, optionally scoped to a project. Returns each batch's id, slug, output format and template id, 25 per page by default. Not for one batch's variant files and links.

Input parameters:

- `cursor` (string): The nextCursor of the previous page with the same filters; absent for the first page
- `limit` (integer): Results per page, from 1 to 100; defaults to 25
- `projectId` (string): Only batches in this project; every project when absent

Output parameters:

- `hasMore` (boolean)
- `items` (array)
- `nextCursor`: Cursor for the next page; null on the last page
- `total` (integer): Matching records across all pages

### `get_batch` (~83 tokens)

Get a processed image and its variants

Use this when the user wants to read the output metadata and first-party file links for one existing Imagelato processed-image batch. Returns the batch's project, template, main URL, formats and sizes plus up to 20 variants with format, size and first-party URL. Not for resizing or converting a new image.

Input parameters:

- `batchId` (string, required): Exact batch id

Output parameters:

- `batch`: Allowlisted batch metadata; asset URLs are kept only on https://www.imagelato.com/images/. Null when not found.
- `status` (string)

### `delete_batch` (~88 tokens)

Delete a processed image batch

Use this when the user wants to permanently delete one Imagelato processed-image batch and its associated files. Returns the deleted batch's id, slug and project. Its original, main output and every resized or converted file are erased and the batch.deleted webhook fires, with no undo. Not for removing a resize preset.

Input parameters:

- `batchId` (string, required): Exact batch id to permanently delete; obtain it

Output parameters:

- `batch`
- `status` (string)

### `list_templates` (~126 tokens)

List resize presets

Use this when the user wants to list existing Imagelato resize and format presets, optionally scoped to one project. Returns each template's id, name, project, output formats and pixel widths, 25 per page by default. Not for the images processed with them.

Input parameters:

- `cursor` (string): The nextCursor of the previous page with the same filters; absent for the first page
- `limit` (integer): Results per page, from 1 to 100; defaults to 25
- `projectId` (string): Only presets in this project; every project when absent

Output parameters:

- `hasMore` (boolean)
- `items` (array)
- `nextCursor`: Cursor for the next page; null on the last page
- `total` (integer): Matching records across all pages

### `get_template` (~69 tokens)

Get a resize preset

Use this when the user wants to read one Imagelato resize preset selected by its exact name or identifier. Returns its project, output formats, pixel widths and created and edited times, or not-found. Not for changing it.

Input parameters:

- `templateIdOrName` (string, required): Exact template id or name

Output parameters:

- `status` (string)
- `template`

### `add_template` (~182 tokens)

Create a resize preset

Use this when the user wants to create one Imagelato preset that specifies widths and formats for future image processing. Returns the new template; formats default to jpg and webp and widths to 512, 256, 128 and 64 pixels. Each call creates another preset and emits template.created to configured webhooks; it does not process an image. Not for editing a preset.

Input parameters:

- `formats` (array): Output formats, one to five of jpg, png, webp, gif or svg; defaults to jpg and webp
- `name` (string, required): Template name, from 1 to 120 characters
- `projectId` (string, required): Exact project id
- `sizes` (array): Output widths in pixels, one to ten strings from 1 to 9999; defaults to 512, 256, 128 and 64

Output parameters:

- `status` (string)
- `template`

### `update_template` (~158 tokens)

Change a resize preset

Use this when the user wants to update selected name, output-format or width fields on one existing Imagelato resize preset. Returns the updated template after replacing only the fields given, and fires the template.updated webhook; it cannot move the preset to another project. Not for creating a preset.

Input parameters:

- `formats` (array): New output formats, one to five of jpg, png, webp, gif or svg; replaces the current list
- `name` (string): New preset name, from 1 to 120 characters
- `sizes` (array): New output widths in pixels, one to ten strings from 1 to 9999; replaces the current list
- `templateIdOrName` (string, required): Exact template id or name

Output parameters:

- `status` (string)
- `template`

### `list_webhook_subscriptions` (~139 tokens)

Check webhook delivery health

Use this when the user wants to read Imagelato webhook subscription configuration and consecutive delivery-failure counts. Returns each endpoint's origin, subscribed events, active flag and consecutive failures, 25 per page by default; an endpoint is disabled after 20 failures in a row. Not for adding or editing a webhook.

Input parameters:

- `cursor` (string): The nextCursor of the previous page with the same filters; absent for the first page
- `limit` (integer): Results per page, from 1 to 100; defaults to 25
- `projectId` (string): Only webhooks of this project; every project when absent

Output parameters:

- `hasMore` (boolean)
- `items` (array)
- `nextCursor`: Cursor for the next page; null on the last page
- `total` (integer): Matching records across all pages

### `list_team_members` (~111 tokens)

List team members and roles

Use this when the user wants to list the display names and assigned roles of members in the connected Imagelato organization. Returns each member's display name and roles, 25 per page by default (no emails, phone numbers or user ids). Not for inviting or removing members.

Input parameters:

- `cursor` (string): The nextCursor of the previous page with the same filters; absent for the first page
- `limit` (integer): Results per page, from 1 to 100; defaults to 25

Output parameters:

- `hasMore` (boolean)
- `items` (array)
- `nextCursor`: Cursor for the next page; null on the last page
- `total` (integer): Matching records across all pages

### `show_project_overview` (~94 tokens)

Show image project overview

Use this when the user wants to render a read-only overview of one Imagelato project with up to eight recent processed-image batches. Returns a card with the project's name, logo and dates plus its 8 most recently processed batches with format, size and first-party links. Not for every batch in the project.

Input parameters:

- `projectIdOrName` (string, required): Exact project id or name, at most 200 characters

Output parameters:

- `batchCount` (integer)
- `batchCountIsLowerBound` (boolean)
- `batches` (array)
- `project`

### `open_imagelato` (~66 tokens)

Imagelato Image Optimization

Use this when the user wants to open the Imagelato project-selection sidebar when the user requests an interactive browser for projects, processed batches and presets. Returns up to 100 projects to start from (no ownership data or credentials). Not for uploading, processing or generating images.

Output parameters:

- `items` (array)
- `truncated` (boolean)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-imagelato-imagelato/mcp#diagnostics

## Score history

- 2026-11-05: 92
- 2026-11-04: 91
- 2026-11-03: 92
- 2026-11-02: 92
- 2026-11-01: 92
- 2026-10-31: 92
- 2026-10-30: 92
- 2026-10-29: 92
- 2026-10-28: 92
- 2026-10-27: 92
- 2026-10-26: 92
- 2026-10-25: 92
- 2026-10-24: 91
- 2026-10-23: 91
- 2026-10-22: 90
- 2026-10-21: 90
- 2026-10-20: 89
- 2026-10-19: 89
- 2026-10-18: 88
- 2026-10-17: 88
- 2026-10-16: 87
- 2026-10-15: 87
- 2026-10-14: 86
- 2026-10-13: 86
- 2026-10-12: 86
- 2026-10-10: 85
- 2026-10-07: 83
- 2026-10-06: 83
- 2026-10-04: 82
- 2026-10-03: 81

## Common questions

### What is the Imagelato Image Processing MCP server?

Imagelato Image Processing is an MCP server listed in the public MCP registry as com.imagelato/imagelato. Set up image processing templates and check batch results, projects and webhooks. This page covers its hosted endpoint (https://mcp.imagelato.com/mcp).

### Is the Imagelato Image Processing MCP server safe to use?

Imagelato Image Processing scores 92 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 Imagelato Image Processing MCP server expose?

Imagelato Image Processing exposes 14 tools: list_projects, get_project, add_project, list_batches, get_batch, and 9 more. Their descriptions and schemas cost roughly 1,497 tokens of context every time the server is loaded.

### Does the Imagelato Image Processing MCP server require authentication?

Yes. Imagelato Image Processing asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the Imagelato Image Processing MCP server still maintained?

Imagelato Image Processing 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 did VerifyMCP test on the Imagelato Image Processing MCP server?

VerifyMCP ran 14 checks on Imagelato Image Processing, covering TLS certificate, Authorization, HTTPS, HSTS header and 10 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://mcp.imagelato.com/mcp
- Website: https://www.imagelato.com/developers/#claude-mcp
- Changelog RSS feed: https://verifymcp.io/servers/com-imagelato-imagelato/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-imagelato-imagelato/mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-imagelato-imagelato/mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-imagelato-imagelato/mcp