# OMORO Style Library (remote · omoro.io)

Search, compare, and blend structured visual aesthetics, palettes, and creative directions.

- Trust score: 68/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-23

## Components

- remote · `omoro.io`: 68/100 (this document), [markdown](https://verifymcp.io/servers/io-omoro-style-library/api-mcp.md), [page](https://verifymcp.io/servers/io-omoro-style-library/api-mcp)

## Channel facts

- Endpoint: `https://omoro.io/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.6.2`

## 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-10-23.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - 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.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 77/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 37/100
  - Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 94/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 80% 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.
  - We read all 17 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 18 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http io-omoro-style-library 'https://omoro.io/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "io-omoro-style-library": {
      "url": "https://omoro.io/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "io-omoro-style-library": {
      "type": "http",
      "url": "https://omoro.io/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.io-omoro-style-library]
url = "https://omoro.io/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-omoro-style-library": {
      "type": "remote",
      "url": "https://omoro.io/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add io-omoro-style-library --url 'https://omoro.io/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-omoro-style-library:
    url: "https://omoro.io/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "io-omoro-style-library": {
      "Transport": "http",
      "Url": "https://omoro.io/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add io-omoro-style-library -t streamable-http -u 'https://omoro.io/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "io-omoro-style-library": {
      "type": "http",
      "url": "https://omoro.io/api/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-10-23 (score 68, +1)

- [security] Tool “get_started” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 2259 → 2587
- [functional] New tool “build_character”

### 2026-10-20 (score 67, +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.

### 2026-10-18 (score 66, +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.

### 2026-10-16 (score 65, +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.

### 2026-10-14 (score 64, +3)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] The server changed its declared name: omoro → omoro-library
- [functional improvement] Tool coverage: 6% → 100%
- [functional improvement] Tool “blend_styles” now declares an output schema
- [functional improvement] Tool “build_ui_direction” now declares an output schema
- [functional improvement] Tool “compare_styles” now declares an output schema
- [functional improvement] Tool “find_palettes_by_color” now declares an output schema
- [functional improvement] Tool “find_styles_by_attributes” now declares an output schema
- [functional improvement] Tool “get_palette” now declares an output schema
- [functional improvement] Tool “get_started” now declares an output schema
- [functional improvement] Tool “get_style” now declares an output schema
- [functional improvement] Tool “list_palettes” now declares an output schema
- [functional improvement] Tool “list_styles” now declares an output schema
- [functional improvement] Tool “list_ui_lab_options” now declares an output schema
- [functional improvement] Tool “search_palettes” now declares an output schema
- [functional improvement] Tool “search_styles” now declares an output schema
- [functional improvement] Tool “suggest_style_directions” now declares an output schema
- [functional improvement] 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”

### 2026-10-13 (score 61, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-12 (score 61)

First indexed and scored.

## MCP tools (17)

### `get_started` (~38 tokens)

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.

Output parameters:

- `data`

### `list_styles` (~79 tokens)

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.

Input parameters:

- `category` (string)
- `group` (string): Mood group to filter by.
- `limit` (integer)
- `offset` (integer)

Output parameters:

- `data`

### `get_style` (~81 tokens)

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.

Input parameters:

- `slug` (string, required): The style's slug, e.g. "bauhaus". Get one from list_styles or search_styles.

Output parameters:

- `data`

### `search_styles` (~79 tokens)

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.

Input parameters:

- `limit` (integer)
- `query` (string, required): Words to look for, e.g. "darkroom film grain".

Output parameters:

- `data`

### `find_styles_by_attributes` (~263 tokens)

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.

Input parameters:

- `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.

Output parameters:

- `data`

### `suggest_style_directions` (~299 tokens)

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.

Input parameters:

- `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, required): 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…

Output parameters:

- `data`

### `compare_styles` (~64 tokens)

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.

Input parameters:

- `a` (string, required): First style slug.
- `b` (string, required): Second style slug.

Output parameters:

- `data`

### `build_style_guide_output` (~140 tokens)

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.

Input parameters:

- `brand_palette` (array): Optional client-supplied colors, clearly kept separate from documented style palettes.
- `format` (string, required)
- `style_slugs` (array, required): One to five Omoro style slugs in influence order. The first style leads the composition.
- `use_case` (string): Optional application or project context.

Output parameters:

- `artifactType` (string)
- `blendTreatment` (object|null)
- `canvas` (object)
- `format` (string)
- `presentationInstructions` (array)
- `sections` (array)
- `sourceStyles` (array)
- `theme` (object)
- `title` (string)
- `visualSystems` (array)

### `build_character` (~321 tokens)

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.

Input parameters:

- `appearance_notes` (string): Distinctive physical features and overall presence.
- `concept` (string, required): 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, required): 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.

Output parameters:

- `data`

### `blend_styles` (~114 tokens)

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.

Input parameters:

- `mix` (number): Percentage led by the second primary style.
- `styles` (array, required): Two to five style slugs. The first two are the primary pair.

Output parameters:

- `data`

### `list_palettes` (~82 tokens)

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.

Input parameters:

- `limit` (integer)
- `offset` (integer)
- `style` (string): Parent style slug, e.g. "brutalism" or "cyberpunk".

Output parameters:

- `data`

### `get_palette` (~53 tokens)

Retrieve one named Omoro palette by slug, including its parent style, mood and five named hex swatches.

Input parameters:

- `slug` (string, required): Palette slug, e.g. "soft-club" or "raw-concrete".

Output parameters:

- `data`

### `search_palettes` (~57 tokens)

Free-text search across palette names, parent styles and mood descriptions. Use this for queries such as "quiet warm studio" or "nightclub neon".

Input parameters:

- `limit` (integer)
- `query` (string, required): Words to look for.

Output parameters:

- `data`

### `find_palettes_by_color` (~70 tokens)

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.

Input parameters:

- `hex` (string, required): A six-digit hex colour, e.g. "#FF6422".
- `limit` (integer)

Output parameters:

- `data`

### `list_ui_lab_options` (~41 tokens)

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.

Output parameters:

- `data`

### `build_ui_direction` (~188 tokens)

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.

Input parameters:

- `clientBrief` (string): Optional client direction or project brief to incorporate into the prompt.
- `language` (string, required): 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, required): 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, required): Omoro style slug. Use search_styles or list_styles first.

Output parameters:

- `data`

### `suggest_ui_landing` (~106 tokens)

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.

Input parameters:

- `audience` (string): Who the page is for.
- `feeling` (string): The desired feeling or visual language.
- `goal` (string, required): What the landing page needs to accomplish, in plain language.
- `needsInteraction` (boolean): Whether the visual should respond to scroll, pointer or drag.

Output parameters:

- `data`

## Diagnostics

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

## Score history

- 2026-10-23: 68
- 2026-10-22: 67
- 2026-10-21: 67
- 2026-10-20: 67
- 2026-10-19: 66
- 2026-10-18: 66
- 2026-10-17: 65
- 2026-10-16: 65
- 2026-10-15: 64
- 2026-10-14: 64
- 2026-10-13: 61
- 2026-10-12: 61

## Common questions

### 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.

## Links

- Remote endpoint: https://omoro.io/api/mcp
- Website: https://omoro.io/mcp-usage
- Changelog RSS feed: https://verifymcp.io/servers/io-omoro-style-library/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-omoro-style-library/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/io-omoro-style-library/api-mcp