Skip to main content
Glama
wzkzd666

wuwa-mcp

by wzkzd666

Related Servers

Alternatives to wuwa-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to search and access Arknights game data including operator information, enemy intelligence, skills, talents, and attributes through PRTS.wiki integration. Provides fuzzy search functionality for operators and enemies with clean Markdown output.
      9
      MIT
    • F
      license
      Not graded
      quality
      A
      maintenance
      Enables querying the Purupuru universe codex programmatically, including characters, locations, Jani variants, and Wuxing elements, with anti-hallucination validation and fuzzy search.
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      Provides read-only access to HoYoLAB and HoYoWiki APIs, enabling search and retrieval of posts, wiki entries, and article content converted to Markdown.
      2
      AGPL 3.0
    • A
      license
      A
      quality
      A
      maintenance
      Arknights PRTS Wiki MCP Server — queries the PRTS Wiki API for full-text search and article extraction, and serves auto-synced operator archives, voice lines, and story/event scripts from game data. Designed for fan-creation AI agents that need accurate lore, character profiles, and in-character dialogue references.
      9
      10
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Provides read-only Arknights intelligence over MCP, enabling structured queries about stages, enemies, operators, and modules with region tagging and evidence-backed analysis. It uses versioned SQLite snapshots and never fetches upstream data at query time.
      4
      13
      Apache 2.0

    TDQS

    B3.4/5.0

    Scored across 3 tools

    Disambiguation3/5

    get_character_info and get_character_profile both fetch character data by name, and the distinction (skills/guides vs profile/archive) is not immediately obvious from the names. get_artifact_info is clearly distinct, but the two character tools have overlapping boundaries that could cause misselection.

    Naming Consistency5/5

    All three tools follow the same get_<entity>_<type> snake_case pattern (get_artifact_info, get_character_info, get_character_profile). The convention is predictable and easy to parse.

    Tool Count3/5

    Three retrieval tools is thin for a game data server that likely has many entity types and would benefit from list/search operations. It covers only the most basic lookups, making the surface feel under-scoped.

    Completeness2/5

    There is no way to list or search for valid character or artifact names, so agents are stuck unless the user already knows exact Chinese names. Other game data (e.g. weapons) is absent, representing significant gaps for the domain.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues