Skip to main content
Glama

Server Details

Wger MCP — wraps wger Workout Manager REST API (free, no auth for read)

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-wger
GitHub Stars
0
Server Listing
mcp-wger

TDQS

A3.7/5.0

Scored across 35 tools

Disambiguation2/5

Several tools are near-duplicates in purpose: ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, deep_research, discover_tools and suggest_questions all answer 'route my question to data', and the beta variant is explicitly identical to the stable one. The polymarket family (arbitrage, edges, edge_tracker, fill_risk, kalshi_spread) and the entity cluster (entity_profile, compare_entities, recent_changes, resolve_entity, validate_claim) also overlap heavily. Descriptions try to steer with 'prefer X over Y' cues, but the option set itself remains confusing.

Naming Consistency3/5

All names are snake_case, which keeps it readable, but the verb style is inconsistent: verb_noun forms (ask_pipeworx, compare_entities, resolve_entity, validate_claim, list_exercises, get_exercise) sit alongside bare noun phrases (entity_profile, recent_changes, deep_research, pipeworx_trending, polymarket_edges). Not chaotic, but not a predictable pattern either.

Tool Count2/5

35 tools is heavy, and for a server named after the wger fitness database the vast majority of the surface (gateway routers, polymarket scanners, dependency/LLM audits, subscriptions, memory) is unrelated to that domain. Add genuine redundancy (ask_pipeworx/_beta/_grounded) and the count exceeds what each tool can justify.

Completeness3/5

The gateway side is broad (routing, entity resolution, comparison, memory, subscriptions, feedback, research), so most research workflows have a path. The wger side is read-only lookup only (list_exercises, get_exercise, list_equipment, list_muscles) with no workout/plan/logging operations, leaving notable gaps for the named domain.

Tool Schema Changelog

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

  1. 1 tool update
    • 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."
  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_spread2 fields changed
      • changedInput schema / examples
        Previous value: -[
        -  {
        -    "topic": "fed"
        -  },
        -  {
        -    "topic": "btc"
        -  }
        -]New value: +[
        +  {
        +    "topic": "fed"
        +  },
        +  {
        +    "topic": "btc"
        +  },
        +  {
        +    "topic": "bitcoin"
        +  },
        +  {
        +    "topic": "fed rate decision"
        +  }
        +]
      • 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

  • F
    license
    Not graded
    quality
    B
    maintenance
    MCP server that wraps wger fitness/nutrition management platform, providing 15 tools for exercise search, ingredient nutrition lookup, weight tracking, and more, accessible to any MCP-compatible AI agent.
    -
  • A
    license
    B
    quality
    C
    maintenance
    MCP server for the Hevy workout tracker API that allows reading and writing workouts, routines, exercise templates, and body measurements.
    22
    10 npm
    MIT
  • A
    license
    A
    quality
    B
    maintenance
    A read-only MCP server for the WHOOP API v2 that lets you query and analyze your own recovery, sleep, strain, cycles, and workout data. Note: currently a pre-alpha scaffold with stubbed internals.
    16
    1
    MIT
Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.