Unmerge
REMOTE · UNMERGE.APP
Split a flat image into separate transparent PNG layers. Pay with Unmerge credits.
Available components
Last scanned (20 hours ago)
Scores higher than 84% of remote servers
Reachable. Last reached 4 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 Security89
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token. See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability76
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 436 tokens (~109/item across 4 items; 4 tools + 0 resources), lean.Pass
- 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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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
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.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 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 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 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 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- 26 Oct 26 77
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 4 Nov 2026 · Probed https://unmerge.app/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=unmerge.app | CN=WE1,O=Google Trust Services,C=US | 11 Oct 2026 | 9 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 3c28381aae4d7d613304018a757e1ba |
| SANs: unmerge.app, *.unmerge.app | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of unmerge.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| unmerge.app. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer
Bearer| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000 |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Protected resource metadata
| Retrieved | No |
|---|---|
| Problem | no_resource_metadata |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://unmerge.app/mcp | Verified | 200 | |
| http (plaintext) | http://unmerge.app/mcp | HTTPS enforced | 301 | https://unmerge.app/mcp |
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 →
get_credits Credits left ~24
Credits available on this Unmerge account. One credit is one layer returned.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_layers Get the layers of a split ~75
Status of a split. When ready, returns every layer with its name, position and a PNG download URL valid for one hour. Free.
| Name | Type | Req | Description |
|---|---|---|---|
| project_id | string | yes | The id returned by split_into_layers. |
| wait_seconds | integer | – | How long to wait for the result before returning, 0 to 50 seconds. |
No output schema declared.
No examples provided.
split_into_layers Split an image into layers ~195
Split a flat image (PNG, JPG or WebP) into named transparent layers, with the hidden parts behind objects filled in. Costs 1 credit per layer returned (at most 17); the account needs at least 5 credits to start. Pass the image as a public https URL or as base64. Waits up to 50 seconds; if it is still processing, call get_layers later.
| Name | Type | Req | Description |
|---|---|---|---|
| image_base64 | string | – | The image as base64, with or without a data: prefix. Use when there is no URL. |
| image_url | string | – | Public https URL of the image. |
| prompt | string | – | Optional: what to separate, in plain words, e.g. "the cat, the sofa and the background". Leave empty to let the model decide. |
| wait_seconds | integer | – | How long to wait for the result before returning, 0 to 50 seconds. |
No output schema declared.
No examples provided.
unlock_layers Unlock layers ~58
For a split with status needs_credits: pay the extra credits owed (shown as credits.owed) so the layer files become available. Charges once even if called again.
| Name | Type | Req | Description |
|---|---|---|---|
| project_id | string | yes | The id returned by split_into_layers. |
No output schema declared.
No examples provided.
How do I install the Unmerge MCP server?
Unmerge is a hosted endpoint at https://unmerge.app/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 · unmerge.app
claude mcp add --transport http app-unmerge-unmerge 'https://unmerge.app/mcp'
What is the Unmerge MCP server?
Unmerge is an MCP server listed in the public MCP registry as app.unmerge/unmerge. Split a flat image into separate transparent PNG layers. Pay with Unmerge credits. This page covers its hosted endpoint (https://unmerge.app/mcp).
Is the Unmerge MCP server safe to use?
Unmerge scores 81 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 Unmerge MCP server expose?
Unmerge exposes 4 tools: split_into_layers, get_layers, unlock_layers, get_credits. Their descriptions and schemas cost roughly 352 tokens of context every time the server is loaded.
Does the Unmerge MCP server require authentication?
Yes. Unmerge 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 Unmerge MCP server still maintained?
Unmerge is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.