Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Muro Paint Colors

REMOTE · MCP.USEMURO.COM · 2 COMPONENTS

Real paint colours from 35 brands, free; paint a room photo with a Muro account.

0 this week 79 Trust /100

Last scanned (8 hours ago)

Scores higher than 78% of remote servers

Reachable. Last reached 6 Nov 2026.

Category Design and Media

Trust breakdown (7 categories)

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
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • HTTPS enforcement could not be verified: the plaintext port answered with HTTP 500, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
  • 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
Schema Quality & AI Usability66
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1702 tokens (~212/item across 8 items; 8 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 Management100
  • No destabilizing schema changes in the last 30 days.Pass
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 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
What we tested

Checks we ran (12)

  • TLS certificate
  • Authorization
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 500, which proves neither a plaintext path nor enforcement.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 29 Oct 26 0
    • Stability: 0.97 → pass security
  • 28 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

  • 26 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

  • 24 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

  • 22 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

  • 20 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 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 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

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 6 Nov 2026 · Probed https://mcp.usemuro.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=usemuro.com CN=WE1,O=Google Trust Services,C=US 29 Sept 2026 28 Dec 2026 ECDSA 256 ECDSA-SHA256 d5647d848b6707a5136d43982f7b2d07
SANs: usemuro.com, mcp.usemuro.com, *.mcp.usemuro.com
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 mcp.usemuro.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
usemuro.com. No DS 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://mcp.usemuro.com/mcp Verified 200
http (plaintext) http://mcp.usemuro.com/mcp Inconclusive 500
MCP tools · 8 exposed · ~1,461 tokens

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 →

Tool Tokens
find_equivalents ~259

Find the closest colours in OTHER brands to a given paint colour or hex value, e.g. "Behr equivalent of Farrow & Ball Hague Blue" or "which Benjamin Moore is closest to #D1CBC1". Give either brand + name_or_code, or hex. Distance is CIEDE2000 ΔE with a verdict: under 1 practically identical, under 2 very close, under 3.5 close, otherwise similar (nothing above ΔE 6 is returned). By default returns the single best match per brand, closest first; pass brands to restrict the search (with one brand you get several options from it). Always pass on the caveat that on-wall results depend on base, sheen and tinting.

NameTypeReqDescription
brandstring–Brand of the source colour (with name_or_code)
brandsarray–Only search these brands, e.g. ["Behr", "Sherwin-Williams"]
hexstring–Source colour as hex, e.g. "#3D4E57" (instead of brand + name_or_code)
limitinteger–Maximum results (default 8)
name_or_codestring–Name or code of the source colour

No output schema declared.

No examples provided.

get_credits ~46

Paid tools only. Show the Muro credit balance and plan of the connected account. Painting costs 1 credit per colour in Standard, 2 in HD and 3 in Ultra.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_paint_color ~158

Look up one paint colour by brand and exact name or code, e.g. brand "Sherwin-Williams" + "SW 7029" or "Agreeable Gray"; brand "Farrow & Ball" + "Hague Blue" or "30". Case, spacing and accents are ignored. A brand sold in several markets (Dulux UK/PL, Sikkens NL/DE/IT, Beckers SE/PL) may return one match per market. If nothing matches exactly, returns close suggestions instead.

NameTypeReqDescription
brandstringyesBrand name, e.g. "Behr", "Benjamin Moore", "Śnieżka"
name_or_codestringyesExact colour name or manufacturer code

No output schema declared.

No examples provided.

get_visualization ~159

Paid tools. Fetch the colours of a visualize_room job that were not ready yet, by job_id and project_id. Waits up to about 25 seconds. Costs nothing extra.

NameTypeReqDescription
countrystring–Where the user buys paint, e.g. "PL", "DE", "US": brands sold there come first in the shopping list
job_idstringyesjob_id from visualize_room
match_brandsarray–Only list paints from these brands, e.g. ["Dulux", "Śnieżka"]
matchesinteger–Paints to list per colour (default 5, 0 = no shopping list)
project_idstringyesproject_id from visualize_room

No output schema declared.

No examples provided.

list_brands ~87

List the paint brands in the database with their number of colours and a brand page url. With country (ISO code like "DE", "PL", "US", "GB" or a name like "Germany"), returns the brands sold there in order of local relevance.

NameTypeReqDescription
countrystring–Country code or name, e.g. "US", "DE", "Poland"

No output schema declared.

No examples provided.

relight_room ~103

Paid (1 credit). Relight a finished interior visualization as day, evening or night, with lamps on or off, keeping the wall colour. Needs project_id and the color_key returned by visualize_room.

NameTypeReqDescription
color_keystringyescolor_key of the painted result, e.g. "c1"
lampsboolean–Lamps on
project_idstringyesproject_id from visualize_room
timestringyesTime of day

No output schema declared.

No examples provided.

search_paint_colors ~203

Find paint colours by name or code across all brands, e.g. "Hague Blue", "SW 7029", "agreeable gray", "grün". Matching ignores case and accents ("sniezny" finds "Śnieżny") and every word may be a prefix. Optionally restrict to one brand. Returns name, brand, code, hex, LRV (light reflectance, 0 = black, 100 = white; lrv_source says whether it is the brand's own figure or our estimate from the hex), collection and the colour page url. To match a hex value or a colour from another brand, use find_equivalents instead.

NameTypeReqDescription
brandstring–Brand name, e.g. "Benjamin Moore", "Farrow & Ball", "Dulux"
limitinteger–Maximum results (default 10)
querystringyesColour name or code, or part of it

No output schema declared.

No examples provided.

visualize_room ~446

Paid (Muro credits, needs a Muro API key). Repaint the walls in a photo of a room, facade or roof in 1 to 12 colours at once and return one image per colour. Give the photo as image_url (a public link) or image_base64. Give each colour as brand + name_or_code from the catalogue (e.g. "Farrow & Ball" + "Hague Blue") or as hex. Without a photo it paints Muro’s sample room (or facade, roof). Every colour comes with a shopping list: the closest real paints from several brands with ΔE and a verdict; pass country to put brands sold there first. RAL works as brand "RAL" + "9005" or just "RAL 9005". Waits up to about 45 seconds; if some colours are still being painted, it returns a job_id for get_visualization. Tell the user the cost before calling: 1 credit per colour in standard quality.

NameTypeReqDescription
colorsarrayyes1 to 12 colours; each one is a separate painted image
countrystring–Where the user buys paint, e.g. "PL", "DE", "US": brands sold there come first in the shopping list
image_base64string–The photo as base64 or a data: URL, instead of image_url
image_urlstring–Public link to the photo (JPEG, PNG or WebP, up to 12 MB). Leave out both image fields to paint Muro's sample room
match_brandsarray–Only list paints from these brands, e.g. ["Dulux", "Śnieżka"]
matchesinteger–Paints to list per colour (default 5, 0 = no shopping list)
paint_ceilingboolean–Interiors only: paint the ceiling too
qualitystring–standard ≈1K (1 credit per colour), hd ≈2K (2), ultra ≈4K (3; plan permitting)
surfacestring–What is in the photo

No output schema declared.

No examples provided.

Install

How do I install the Muro Paint Colors MCP server?

Muro Paint Colors is a hosted endpoint at https://mcp.usemuro.com/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 · mcp.usemuro.com

# add to Claude Code
claude mcp add --transport http com-usemuro-paint-colors 'https://mcp.usemuro.com/mcp'
Common questions

What is the Muro Paint Colors MCP server?

Muro Paint Colors is an MCP server listed in the public MCP registry as com.usemuro/paint-colors. Real paint colours from 35 brands, free; paint a room photo with a Muro account. This page covers its hosted endpoint (https://mcp.usemuro.com/mcp).

Is the Muro Paint Colors MCP server safe to use?

Muro Paint Colors scores 79 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 Muro Paint Colors MCP server expose?

Muro Paint Colors exposes 8 tools: search_paint_colors, get_paint_color, find_equivalents, list_brands, get_credits, and 3 more. Their descriptions and schemas cost roughly 1,461 tokens of context every time the server is loaded.

Does the Muro Paint Colors MCP server require authentication?

No. We connected to Muro Paint Colors without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Muro Paint Colors MCP server still maintained?

Muro Paint Colors is still listed as active in the MCP registry. We last reached this channel on 6 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the Muro Paint Colors MCP server?

VerifyMCP ran 12 checks on Muro Paint Colors, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Muro Paint Colors: HTTPS. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.