OMORO Style Library
REMOTE · OMORO.IO
Search, compare, and blend structured visual aesthetics, palettes, and creative directions.
Available components
Last scanned (15 hours ago)
Scores higher than 57% of remote servers
Reachable. Last reached 23 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 Security57
- 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 17 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
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- 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 Usability77
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 2587 tokens (~152/item across 17 items; 17 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 Management37
- Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage94
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 80% of tool parameters carry a description.Partial
- 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 17 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 18 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.
- 23 Oct 26 +1
- Tool “get_started” rewrote its description, which is the text the model reads security
- Schema quality: 2259 → 2587 ▼ functional
- New tool “build_character” functional
- 20 Oct 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.
- 18 Oct 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.
- 16 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.
- 14 Oct 26 +3
- The server rewrote its instructions, which are the text every model session reads security
- The server changed its declared name: omoro → omoro-library security
- Tool coverage: 6% → 100% ▲ functional
- Tool “blend_styles” now declares an output schema ▲ functional
- Tool “build_ui_direction” now declares an output schema ▲ functional
- Tool “compare_styles” now declares an output schema ▲ functional
- Tool “find_palettes_by_color” now declares an output schema ▲ functional
- Tool “find_styles_by_attributes” now declares an output schema ▲ functional
- Tool “get_palette” now declares an output schema ▲ functional
- Tool “get_started” now declares an output schema ▲ functional
- Tool “get_style” now declares an output schema ▲ functional
- Tool “list_palettes” now declares an output schema ▲ functional
- Tool “list_styles” now declares an output schema ▲ functional
- Tool “list_ui_lab_options” now declares an output schema ▲ functional
- Tool “search_palettes” now declares an output schema ▲ functional
- Tool “search_styles” now declares an output schema ▲ functional
- Tool “suggest_style_directions” now declares an output schema ▲ functional
- Tool “suggest_ui_landing” now declares an output schema ▲ functional
- The server now declares the “prompts” capability functional
- First check of Schema quality: 100 functional
- New prompt “getting_started” functional
- 13 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 12 Oct 26 61
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 23 Oct 2026 · Probed https://omoro.io/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=omoro.io | CN=WE1,O=Google Trust Services,C=US | 20 Sept 2026 | 19 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | bef2abd0108cefa313b7b82d2f6e509f |
| SANs: omoro.io | ||||||
| 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 omoro.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 38690, 57355 | 8, 8 | Verified |
| omoro.io. | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://omoro.io/api/mcp | Verified | 200 | |
| http (plaintext) | http://omoro.io/api/mcp | HTTPS enforced | 301 | https://omoro.io/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 →
blend_styles ~114
Build an authentic multi-style blend from two to five Omoro styles. The first two styles anchor the visual direction; added styles are treated as influence layers. Returns defining rendering techniques, visible contribution requirements, fidelity checks, palette and three coordinated mockup prompts: one hero and two distinct supporting applications, presented as a large hero left and two stacked applications right.
| Name | Type | Req | Description |
|---|---|---|---|
| mix | number | – | Percentage led by the second primary style. |
| styles | array | yes | Two to five style slugs. The first two are the primary pair. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | yes | – |
No examples provided.
build_character ~321
Build an original character brief grounded in Omoro styles. Returns an Omoro Characters-compatible JSON file and a detailed image prompt; it does not generate images or save anything to an account. Import the JSON at omoro.io/characters to keep editing there.
| Name | Type | Req | Description |
|---|---|---|---|
| appearance_notes | string | – | Distinctive physical features and overall presence. |
| concept | string | yes | The character idea, personality, story or brief. Include what makes them distinct. |
| gender | string | – | – |
| hairstyle | string | – | Optional signature hairstyle. Describe the exact silhouette and unusual construction, such as sculptural coils arranged as a crown, braided loops, asymmetry, or an unexpected shape. Make it personal… |
| kind | string | – | Choose creature for a non-human or hybrid design. |
| name | string | – | Character name, if chosen. |
| output | string | – | A single portrait or four-view reference sheet. |
| palette | array | – | Optional exact client colors. Otherwise the documented Omoro style palette is used. |
| render | string | – | – |
| role | string | – | Their role or place in the story. |
| setting | string | – | Optional scene or environment. |
| signature_item | string | – | A memorable accessory or visual identifier. |
| species | string | – | Species or ancestry, especially for original creatures and hybrids. |
| style_slugs | array | yes | One or two Omoro style slugs, with the lead style first. Find styles with search_styles or list_styles. |
| wardrobe | string | – | Clothing, silhouette and materials. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | yes | – |
No examples provided.
build_style_guide_output ~140
Create a separate Omoro-designed style guide, palette/type sheet, or application brief for one style or a user-selected blend. Its visual system is grounded in each style's documented rendering techniques, palette, typography, and composition. This does not change blend_styles' established hero plus two supporting mockups.
| Name | Type | Req | Description |
|---|---|---|---|
| brand_palette | array | – | Optional client-supplied colors, clearly kept separate from documented style palettes. |
| format | string | yes | – |
| style_slugs | array | yes | One to five Omoro style slugs in influence order. The first style leads the composition. |
| use_case | string | – | Optional application or project context. |
| Name | Type | Req | Description |
|---|---|---|---|
| artifactType | string | yes | – |
| blendTreatment | object|null | yes | – |
| canvas | object | yes | – |
| format | string | yes | – |
| presentationInstructions | array | yes | – |
| sections | array | yes | – |
| sourceStyles | array | yes | – |
| theme | object | yes | – |
| title | string | yes | – |
| visualSystems | array | yes | – |
No examples provided.
build_ui_direction ~188
Build a concrete UI Lab direction brief from a product archetype, visual language, Omoro style and optional palette. Returns layout geometry, palette roles, typography/material guidance, keep/avoid rules and a paste-ready prompt.
| Name | Type | Req | Description |
|---|---|---|---|
| clientBrief | string | – | Optional client direction or project brief to incorporate into the prompt. |
| language | string | yes | UI Lab visual language key, for example technical, swiss, industrial or cinematic. |
| palette | string | – | Optional Omoro palette slug. Use search_palettes or list_palettes first. |
| product | string | yes | UI Lab product key, for example creative, commerce, analytics or developer. |
| promptMode | string | – | Prompt emphasis: Omoro system, client brief, or a synthesis of both. Defaults to synthesis when clientBrief is supplied. |
| style | string | yes | Omoro style slug. Use search_styles or list_styles first. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | yes | – |
No examples provided.
compare_styles ~64
Put two styles side by side: their attribute profiles with the gap on each axis, their palettes, and their documented periods. Use it to explain how two visual languages actually differ.
| Name | Type | Req | Description |
|---|---|---|---|
| a | string | yes | First style slug. |
| b | string | yes | Second style slug. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | yes | – |
No examples provided.
find_palettes_by_color ~70
Rank palettes by their closest swatch to a supplied hex colour. Use when a user has a brand colour or image-derived hex and needs compatible Omoro palettes.
| Name | Type | Req | Description |
|---|---|---|---|
| hex | string | yes | A six-digit hex colour, e.g. "#FF6422". |
| limit | integer | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | yes | – |
No examples provided.
find_styles_by_attributes ~263
Rank styles by how closely they sit to a target visual position. Give only the axes you care about; the rest are ignored rather than assumed. Each axis runs -1 to 1. This answers questions prose cannot, such as which styles are simultaneously minimal, cool, geometric and digital.
| Name | Type | Req | Description |
|---|---|---|---|
| analog_digital | number | – | Target position on the analog_digital axis, -1 to 1. |
| expressive_restrained | number | – | Target position on the expressive_restrained axis, -1 to 1. |
| futuristic_nostalgic | number | – | Target position on the futuristic_nostalgic axis, -1 to 1. |
| light_dark | number | – | Target position on the light_dark axis, -1 to 1. |
| limit | integer | – | – |
| minimal_maximal | number | – | Target position on the minimal_maximal axis, -1 to 1. |
| organic_geometric | number | – | Target position on the organic_geometric axis, -1 to 1. |
| structured_chaotic | number | – | Target position on the structured_chaotic axis, -1 to 1. |
| warm_cool | number | – | Target position on the warm_cool axis, -1 to 1. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | yes | – |
No examples provided.
get_palette ~53
Retrieve one named Omoro palette by slug, including its parent style, mood and five named hex swatches.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | Palette slug, e.g. "soft-club" or "raw-concrete". |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | yes | – |
No examples provided.
get_started ~38
Show the Omoro MCP welcome guide, including how to search styles and palettes, build UI directions, and create an original character with the character builder.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | yes | – |
No examples provided.
get_style ~81
The full record for one style: palette with named swatches, the eight-axis attribute profile, typography pairing, documented period and origin, visual markers, related styles, a canonical hero image, and the page's labelled visual gallery.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | The style's slug, e.g. "bauhaus". Get one from list_styles or search_styles. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | yes | – |
No examples provided.
list_palettes ~82
List Omoro's named colour palettes. Optionally narrow to a parent style. Each result includes a palette name, mood, parent style and five named hex swatches.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| offset | integer | – | – |
| style | string | – | Parent style slug, e.g. "brutalism" or "cyberpunk". |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | yes | – |
No examples provided.
list_styles ~79
List documented aesthetic styles. Optionally narrow by mood group or category. Returns the short listing: slug, name, url, group, a one-line summary and the five palette hex codes.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | – |
| group | string | – | Mood group to filter by. |
| limit | integer | – | – |
| offset | integer | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | yes | – |
No examples provided.
list_ui_lab_options ~41
List the product archetypes and visual languages supported by Omoro UI Lab. Use this before building a direction when you need to choose the right interface structure.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | yes | – |
No examples provided.
search_palettes ~57
Free-text search across palette names, parent styles and mood descriptions. Use this for queries such as "quiet warm studio" or "nightclub neon".
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| query | string | yes | Words to look for. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | yes | – |
No examples provided.
search_styles ~79
Free-text search across style names and summaries. Use when you know roughly what you are looking for but not the slug. For finding styles by visual character rather than by name, find_styles_by_attributes is the better tool.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| query | string | yes | Words to look for, e.g. "darkroom film grain". |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | yes | – |
No examples provided.
suggest_style_directions ~299
Return three distinct, Omoro-grounded brand routes for a user. First translate only supported personal taste signals into numeric taste_axes, include the exact known palette and known brand_context, then call this tool. Each route includes an automatically selected style blend, signature visuals, positioning and message framework, and voice guidance. Use Omoro for the page frame only; let each blend's defining features lead its route. Present all three as choices and do not invent missing brand facts or collapse the options into one generic style.
| Name | Type | Req | Description |
|---|---|---|---|
| avoid_styles | array | – | Style slugs the user or brand has rejected or already overuses. |
| brand_context | object | – | Known, user-provided brand facts Muse may use for positioning and messaging. Omit unknown fields; the tool will leave them as open inputs. |
| brand_palette | array | – | Exact brand colors as six-digit hex codes. When supplied, all three directions must stay within these colors. |
| taste_axes | object | yes | Infer only axes supported by the user's known context. Each is -1 to 1. Poles: minimal_maximal (- minimal, + maximal); analog_digital (- analog, + digital); expressive_restrained (- restrained, + exp… |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | yes | – |
No examples provided.
suggest_ui_landing ~106
Suggest the simplest Omoro landing-page or WebGL direction for a user's goal. Returns a recommended layout, an optional interactive scene, and a few calibration questions before building.
| Name | Type | Req | Description |
|---|---|---|---|
| audience | string | – | Who the page is for. |
| feeling | string | – | The desired feeling or visual language. |
| goal | string | yes | What the landing page needs to accomplish, in plain language. |
| needsInteraction | boolean | – | Whether the visual should respond to scroll, pointer or drag. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | yes | – |
No examples provided.
How do I install the OMORO Style Library MCP server?
OMORO Style Library is a hosted endpoint at https://omoro.io/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 · omoro.io
claude mcp add --transport http io-omoro-style-library 'https://omoro.io/api/mcp'
What is the OMORO Style Library MCP server?
OMORO Style Library is an MCP server listed in the public MCP registry as io.omoro/style-library. Search, compare, and blend structured visual aesthetics, palettes, and creative directions. This page covers its hosted endpoint (https://omoro.io/api/mcp).
Is the OMORO Style Library MCP server safe to use?
OMORO Style Library 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 OMORO Style Library MCP server expose?
OMORO Style Library exposes 17 tools: get_started, list_styles, get_style, search_styles, find_styles_by_attributes, and 12 more. Their descriptions and schemas cost roughly 2,075 tokens of context every time the server is loaded.
Does the OMORO Style Library MCP server require authentication?
No. We connected to OMORO Style Library without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the OMORO Style Library MCP server still maintained?
OMORO Style Library is still listed as active in the MCP registry. We last reached this channel on 23 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.