AI Separations
REMOTE · WWW.AISEPARATIONS.COM
Turn artwork into press-ready color separations for screen printing and DTF: plates and halftones.
Available components
Last scanned (12 hours ago)
Scores higher than 57% of remote servers
Reachable. Last reached 18 Oct 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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- 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 Usability65
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 985 tokens (~197/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 Management27
- Stability observed for 8 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 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
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
- 17 Oct 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.
- 15 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.
- 13 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.
- 11 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- 10 Oct 26 63
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 18 Oct 2026 · Probed https://www.aiseparations.com/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=www.aiseparations.com | CN=YR2,O=Let's Encrypt,C=US | 15 Oct 2026 | 13 Jan 2027 | RSA 2048 | SHA256-RSA | 518eba4a7397611326bda8ca534d4d74d1a |
| SANs: www.aiseparations.com | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of www.aiseparations.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| aiseparations.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://www.aiseparations.com/api/mcp | Verified | 200 | |
| http (plaintext) | http://www.aiseparations.com/api/mcp | HTTPS enforced | 308 | https://www.aiseparations.com/api/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 →
buy_credits Buy a credit pack (hosted checkout) ~137
Start a purchase of an AI Separations credit pack for the user and return a Stripe Checkout link. Packs: credits_sample ($19, 25 separations), credits_shop ($99, 200), credits_studio ($349, 1,000). Credits never expire; 1 credit = 1 full separation via separate_image. Requires the user's email: the API key is emailed there after payment. Nothing is charged by this tool — the user pays on the returned link.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | The buyer's email — receipt and API key go here | |
| pack | string | – | Which credit pack (default credits_sample) |
No output schema declared.
No examples provided.
check_credits Check credit balance ~37
Check the remaining separation credits on an AI Separations API key. Free.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | – | The API key to check |
No output schema declared.
No examples provided.
estimate_screens Estimate screens (free) ~211
FREE, no key needed. Analyze artwork for screen printing: how many spot-color screens it needs, the detected ink colors (with named ink matches), whether it's flat/vector or photographic, and whether screen printing or DTF is the better process. Use this first on any logo or design.
| Name | Type | Req | Description |
|---|---|---|---|
| garment | string | – | Shirt the art prints on: "dark" (black, default), "light" (white), a color name (Navy, Royal, Red, Maroon, Forest, Gold, Heather Grey, Charcoal, ...) or a hex like "#1f2a44". The separation is solved… |
| image_b64 | string | – | Base64 (or data URL) of the artwork — alternative to image_url |
| image_url | string | – | Public http(s) URL of the artwork (PNG/JPG, max 12 MB) |
| underbase | boolean | – | Print a white underbase (default: on for shirts darker than mid-grey) |
No output schema declared.
No examples provided.
get_pricing Pricing & plans ~39
AI Separations pricing: free first separation, API credit packs, monthly plans, and the $179 one-time desktop app — with direct purchase links.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
separate_image Run a full color separation ~404
Run the real separation engine on artwork: detected spot inks, one grayscale film-positive plate per ink (halftoned, dot-gain compensated, white underbase on dark garments) plus a composite print preview. With no key: free small preview. With free_email: ONE full separation per email address, plates delivered by email, no watermark. With api_key: metered (1 credit), plates emailed to deliver_email.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | – | AI Separations API key (metered, 1 credit) |
| colors | integer | – | Force this many inks (omit = auto-detect) |
| deliver_email | string | – | Where to email the full-resolution plates zip (defaults to free_email) |
| free_email | string | – | Email for the one-per-email FREE full separation — plates are sent there |
| garment | string | – | Shirt the art prints on: "dark" (black, default), "light" (white), a color name (Navy, Royal, Red, Maroon, Forest, Gold, Heather Grey, Charcoal, ...) or a hex like "#1f2a44". The separation is solved… |
| image_b64 | string | – | Base64 (or data URL) of the artwork — alternative to image_url |
| image_url | string | – | Public http(s) URL of the artwork (PNG/JPG, max 12 MB) |
| mode | string | – | index = one ink per square pixel, no halftone; gray = one screen (black ink on light shirts, white on dark); sim = simulated process (default), spot = solid spot colors for flat logos, cmyk = 4-color… |
| palette | array | – | Exact ink hex codes to separate to (optional) |
| underbase | boolean | – | Print a white underbase (default: on for shirts darker than mid-grey) |
No output schema declared.
No examples provided.
How do I install the AI Separations MCP server?
AI Separations is a hosted endpoint at https://www.aiseparations.com/api/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 · www.aiseparations.com
claude mcp add --transport http com-aiseparations-color-separations 'https://www.aiseparations.com/api/mcp'
What is the AI Separations MCP server?
AI Separations is an MCP server listed in the public MCP registry as com.aiseparations/color-separations. Turn artwork into press-ready color separations for screen printing and DTF: plates and halftones. This page covers its hosted endpoint (https://www.aiseparations.com/api/mcp).
Is the AI Separations MCP server safe to use?
AI Separations scores 67 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 AI Separations MCP server expose?
AI Separations exposes 5 tools: estimate_screens, separate_image, check_credits, buy_credits, get_pricing. Their descriptions and schemas cost roughly 828 tokens of context every time the server is loaded.
Does the AI Separations MCP server require authentication?
No. We connected to AI Separations without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the AI Separations MCP server still maintained?
AI Separations is still listed as active in the MCP registry. We last reached this channel on 18 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.