Skip to main content
Glama

Codewars

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Server Details

Codewars 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
45.6% over 39 days
Last Tested
Transport
Streamable HTTP
URL
Repository
pipeworx-io/mcp-codewars
GitHub Stars
0

TDQS

A3.7/5.0

Scored across 35 tools

Disambiguation3/5

Individual descriptions are verbose and actively steer selection, but the set has genuine overlap: ask_pipeworx vs ask_pipeworx_beta (explicitly identical right now) vs ask_pipeworx_grounded vs deep_research all do routed lookups, and discover_tools vs suggest_questions both answer 'what can I do'. The four Codewars tools are distinct, but the polymarket cluster (edges/arbitrage/bet_research/fill_risk/tracker/spread) and the discovery/meta cluster create real misselection risk.

Naming Consistency3/5

Everything is snake_case, which is a baseline win, but the semantic conventions are mixed: verb_noun (compare_entities, resolve_entity, validate_claim), bare nouns (kata, user, recall, forget), and noun_verb (ai_visibility_check). Namespacing is also uneven — polymarket_* and ask_pipeworx_* are prefixed while entity_profile/recent_changes are not, and the Codewars tools use a different vocabulary entirely.

Tool Count2/5

35 tools is heavy for what is essentially a data-gateway surface, and the count is inflated by near-duplicates (three ask_pipeworx variants, two AI-visibility tools) plus unrelated domains glued together (memory, subscriptions, polymarket, Codewars, llms.txt generation). Only 4 of the 35 tools relate to the server's stated Codewars purpose, so most of the count is not earning its place in scope.

Completeness3/5

The Pipeworx-side surface is broad and largely self-consistent (memory CRUD, subscription lifecycle, entity resolution, research, market tooling), but judged against the Codewars domain implied by the server name it is thin: kata lookup, user profile, authored and completed kata exist, yet there is no kata search/filter, no solutions retrieval, and no leaderboard/clan exploration, leaving obvious dead ends for a Codewars-focused agent.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 2 tool updates
    • Changedbet_research2 fields changed
      • changedInput schema / examples
        Previous 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"
+  }
+]
      • changedInput schema / properties / market / description
        Previous 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."
    • Changedpolymarket_kalshi_spread1 field changed
      • changedInput schema / examples
        Previous value: -[
-  {
-    "topic": "fed"
-  },
-  {
-    "topic": "btc"
-  }
-]New value: +[
+  {
+    "topic": "fed"
+  },
+  {
+    "topic": "btc"
+  },
+  {
+    "topic": "bitcoin"
+  },
+  {
+    "topic": "fed rate decision"
+  }
+]
  2. 2 tool updates
    • Changedbet_research2 fields changed
      • changedInput schema / examples
        Previous 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"
+  }
+]
      • changedInput schema / properties / market / description
        Previous 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."
    • Changedpolymarket_kalshi_spread1 field changed
      • changedInput schema / properties / topic / description
        Previous 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

Related MCP Servers

Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources