Remote MCP · Endpoint

Muro Paint Colors MCP server

No. Muro Paint Colors answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mcp.usemuro.com/mcp

The last check completed an MCP handshake.

Registry name
com.usemuro/paint-colors
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
212 ms
Tools exposed
8 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Real paint colours from 35 brands, free; paint a room photo with a Muro account.
Listing
From the official MCP registry (active).
Recent checks of Muro Paint Colors
CheckedResultHandshake
1 hour agoHandshake completed212 ms
10 days agoHandshake completed260 ms
10 days agoHandshake completed299 ms
11 days agoHandshake completed343 ms
12 days agoHandshake completed291 ms
14 days agoHandshake completed195 ms
14 days agoHandshake completed283 ms
15 days agoHandshake completed199 ms
17 days agoHandshake completed200 ms
19 days agoHandshake completed251 ms
21 days agoHandshake completed346 ms
24 days agoHandshake completed209 ms
26 days agoHandshake completed193 ms
28 days agoHandshake completed302 ms

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

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 Muro Paint Colors and makes no claim about it beyond what these checks measured.