Color
Server Details
Color utilities MCP.
Glama couldn't complete the latest health check. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.
If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.
- Status
- Unhealthy
- Uptime
- 47.8% over 38 days
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- pipeworx-io/mcp-color
- GitHub Stars
- 0
- Server Listing
- mcp-color
TDQS
Scored across 34 tools
Several tools overlap heavily: ask_pipeworx, ask_pipeworx_beta (currently identical), ask_pipeworx_grounded, deep_research, and validate_claim all serve as general answer/research paths, while entity_profile, compare_entities, recent_changes, and resolve_entity also overlap on entity lookup. The detailed descriptions help, but the set still forces agents to guess which near-duplicate query path to use.
Tool names are consistently snake_case with no camelCase or punctuation deviations. However, patterns vary between verb-led commands (validate_claim, compare_entities, discover_tools) and noun/domain labels (entity_profile, polymarket_edges, deep_research), so predictability is good but not uniform.
34 tools is heavy and mixes unrelated domains—three color utilities, a large Pipeworx data gateway, memory, subscriptions, feedback, and Polymarket research—in one surface. The count is far beyond a well-scoped utility set and makes the server's apparent purpose hard to pin down.
If the domain is color, the three color tools (contrast, convert, nearest) omit common operations like palette generation, extraction, or accessibility simulation. If the domain is Pipeworx data access, the surface is broad but shallow with many read-only wrappers and no clear CRUD lifecycle across sources.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
1 tool update
- Changed
bet_research2 fields changed- changed
Input schema / examplesPrevious value: -[ - { - "market": "when-will-bitcoin-hit-150k" - }, - { - "market": "https://polymarket.com/event/when-will-bitcoin-hit-150k" - } -]New value: +[ + { + "market": "will-kristi-noem-win-the-2028-republican-presidential-nomination" + }, + { + "market": "https://polymarket.com/event/will-kristi-noem-win-the-2028-republican-presidential-nomination" + } +] - changed
Input schema / properties / market / descriptionPrevious value: -"Polymarket slug (\"when-will-bitcoin-hit-150k\"), full URL (\"https://polymarket.com/event/...\"), or question text (\"Will Bitcoin hit $150k?\"). Dated slugs stop resolving once they settle — Polymarket de-indexes resolved markets — so prefer an undated one."New value: +"Polymarket slug (\"will-kristi-noem-win-the-2028-republican-presidential-nomination\"), full URL (\"https://polymarket.com/event/...\"), or question text (\"Will Bitcoin hit $150k?\"). Dated slugs stop resolving once they settle — Polymarket de-indexes resolved markets — so prefer an undated one."
2 tool updates
- Changed
bet_research2 fields changed- changed
Input schema / examplesPrevious value: -[ - { - "market": "will-bitcoin-reach-100k-in-july-2026" - }, - { - "market": "https://polymarket.com/event/will-bitcoin-hit-150k-by-june-30-2026" - } -]New value: +[ + { + "market": "when-will-bitcoin-hit-150k" + }, + { + "market": "https://polymarket.com/event/when-will-bitcoin-hit-150k" + } +] - changed
Input schema / properties / market / descriptionPrevious value: -"Polymarket slug (\"will-bitcoin-hit-150k-by-june-30-2026\"), full URL (\"https://polymarket.com/event/...\"), or question text (\"Will Bitcoin hit $150k by June 30?\")"New value: +"Polymarket slug (\"when-will-bitcoin-hit-150k\"), full URL (\"https://polymarket.com/event/...\"), or question text (\"Will Bitcoin hit $150k?\"). Dated slugs stop resolving once they settle — Polymarket de-indexes resolved markets — so prefer an undated one."
- Changed
polymarket_kalshi_spread2 fields changed- changed
Input schema / examplesPrevious value: -[ - { - "topic": "fed" - }, - { - "topic": "btc" - } -]New value: +[ + { + "topic": "fed" + }, + { + "topic": "btc" + }, + { + "topic": "bitcoin" + }, + { + "topic": "fed rate decision" + } +] - changed
Input schema / properties / topic / descriptionPrevious value: -"Pre-mapped: fed | btc | cpi | gdp | sp500 | recession | next_pope | next_uk_pm | next_israel_pm | 2028_president"New value: +"Subject to compare. Canonical keys: fed | btc | eth | cpi | gdp | sp500 | recession | next_pope | next_uk_pm | next_israel_pm | 2028_president — but aliases and keywords resolve too (\"bitcoin\", \"fed rate decision\", \"ethereum\", \"inflation\", \"s&p 500\", \"us recession\", \"next pope\", \"2028 election\"). Check resolution.topic_matched_by in the response: \"exact\"/\"alias\" is a curated pairing, \"phrase\"/\"token\" is a keyword guess."
Related MCP Connectors
Color API MCP — wraps thecolorapi.com (free, no auth)
A complete color workflow over MCP: mix, convert, harmonize, measure, and remember palettes.
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceWraps thecolorapi.com to provide color data and information through MCP, with no authentication required.4 npmMIT
- AlicenseAqualityDmaintenanceA simple color utility MCP server for frontend developers. Convert, mix, adjust, and analyze colors right from your AI agents.1124 npmMIT
- AlicenseNot gradedqualityCmaintenanceMCP server that names hex colors using human-friendly color-name lists.3 npmMIT
- AlicenseNot gradedqualityDmaintenanceAn interactive color picker that renders as a UI inside MCP-compatible hosts like VS Code GitHub Copilot and Claude.1Apache 2.0
Glama MCP Gateway
Add one secure layer between your agents and this server.