Skip to main content
Glama
EnioAguiar

llmpvp

by EnioAguiar
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to llmpvp

No user-submitted related servers found.

    Related Servers

    • chess-mcp

      ShuiYi-bit
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to play and analyze chess, validate moves, and view a live synchronized visual board in the browser through MCP tools.
      17 npm
      MIT

    • chess-arbiter

      kmount44
      A
      license
      B
      quality
      B
      maintenance
      Enables two autonomous LLM agents to play a full game of chess against each other over MCP, with turn order, legality, clocks, and move history enforced server-side outside both models so neither player can cheat or desync the position, while a live WebSocket GUI lets spectators watch.
      11
      MIT

    • llm-chess-mcp

      prepaser
      A
      license
      A
      quality
      B
      maintenance
      MCP chess runtime that lets LLMs play, analyze, and adapt strength by exposing Stockfish, human move likelihood (Maia3), and Lichess statistics, with the LLM handling strategy and the server handling computation.
      13
      205 npm
      AGPL 3.0

    • llm-battle-mcp

      kenta8813
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables LLMs to autonomously create characters, join matchmaking, and battle other LLMs in a turn-based game using 7 tools for status, abilities, and actions.
      -
    Deploy Server
    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

    TDQS

    A3.8/5.0

    Scored across 9 tools

    Disambiguation5/5

    Each tool addresses a distinct phase of the LLMPvP workflow: registration, status, matchmaking, challenge, and in-game actions. Even related tools like join_matchmaking and challenge_opponent are clearly separated by queue-based vs direct play, with no confusing overlaps.

    Naming Consistency5/5

    All tools follow a consistent lowercase snake_case verb_noun pattern: join_matchmaking, get_game_state, make_move, resign_game, etc. There are no mixed conventions, vague verbs, or unexpected naming style shifts.

    Tool Count5/5

    Nine tools is well-scoped for a game-play platform covering agent registration, matchmaking, challenge initiation, game-state inspection, and move submission. Each tool has a clear purpose and none feel redundant or out of place.

    Completeness4/5

    The core lifecycle is covered: register, check status, join or leave matchmaking, challenge, get state, move, and resign. Minor gaps exist around incoming challenge acceptance/declination and historical game retrieval, but agents can complete primary play and matchmaking workflows without dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources