Skip to main content
Glama
xunji-private-mcp

xunji-private-mcp

by Vdk1639

Related Servers

Alternatives to xunji-private-mcp

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      B
      maintenance
      Enables clients to read diary entries, nutrients, water, exercise, measurements, goals, recipes, and saved meals; search foods and serving sizes; estimate nutrition and edible weight from images; and make explicitly requested diary/account updates with idempotency and read-back safeguards. Supports local stdio connections and an OAuth-secured HTTPS gateway with separate read/write grants and local approval for sensitive operations.
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      Exposes an operator's own Xunji (训记) training history — daily sessions, per-movement history, official plans, and aggregate stats — to ChatGPT and other MCP clients as compact read-first tools, protected by OAuth 2.1 on Cloudflare Workers so the Xunji API key never leaves the Worker. Writes are opt-in, off by default, and require explicit confirmation, and nothing can be deleted.
      MIT
    • A
      license
      C
      quality
      C
      maintenance
      Enables authorized clients to search and read titles, people, feeds, reviews, and account data for a single configured account, and to perform permitted writes such as managing watchlists, custom lists, reviews, comments, posts, and profile settings over local stdio or authenticated HTTP.
      89
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables reading Fitbod training history, generating workouts via Fitbod's engine, configuring workout programs, and tracking body composition over time.
      4
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP clients to operate training records, nutrition lookup, body-metric tracking, and web search through standard stdio tools.
      1
      MIT

    TDQS

    A3.6/5.0

    Scored across 12 tools

    Disambiguation4/5

    The four food tools are distinguishable by lifecycle stage (catalog search vs. record read vs. record write vs. custom-food creation), and the training/plan/body-metric/template tools each target a distinct resource. The main risk is the shared `upsert_*` verb family across four unrelated domains and the search vs. query split for food reads, which an agent could momentarily confuse.

    Naming Consistency4/5

    All twelve names are snake_case verb_noun (search_official_food, upsert_training, list_official_plans, query_body_metrics), so the pattern is predictable. Minor deviation: read operations use three different verbs (search, query, get, list), which slightly weakens predictability but remains readable.

    Tool Count5/5

    Twelve tools is squarely in the well-scoped range and each tool maps to a concrete resource-action pair (six read, six write). No tool looks redundant or like filler.

    Completeness4/5

    Coverage spans the full domain: food search/records/custom foods, body metrics, trainings, official plans, and agent templates, with read and write in every mutable area. Minor gaps exist — there is no explicit delete for food records or body metrics (only upsert), and plans are read-only, though that may be intentional.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues