Remote MCP · Endpoint

OMORO Style Library MCP server

No. OMORO Style Library answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://omoro.io/api/mcp

The last check completed an MCP handshake.

Registry name
io.omoro/style-library
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
122 ms
Tools exposed
19 tools
Uptime, last 30 days
100% from 16 checks
Described by its publisher as
Search, compare, and blend structured visual aesthetics, palettes, and creative directions.
Listing
From the official MCP registry (active).
Recent checks of OMORO Style Library
CheckedResultHandshake
1 hour agoHandshake completed122 ms
12 hours agoHandshake completed341 ms
1 day agoHandshake completed123 ms
2 days agoHandshake completed83 ms
4 days agoHandshake completed114 ms
4 days agoHandshake completed100 ms
5 days agoHandshake completed153 ms
6 days agoHandshake completed131 ms
8 days agoHandshake completed120 ms
11 days agoHandshake completed208 ms
13 days agoHandshake completed115 ms
16 days agoHandshake completed169 ms
18 days agoHandshake completed156 ms
20 days agoHandshake completed140 ms
22 days agoHandshake completed119 ms
24 days agoHandshake completed117 ms

The last 16 checks. Full history is kept for 30 days; the all-time counter stands at 16 responding of 16.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with OMORO Style Library and makes no claim about it beyond what these checks measured.