Skip to main content
Glama
lappi

ttw-mcp

by lappi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to ttw-mcp

No user-submitted related servers found.

    Related Servers

    • rttf-mcp

      lappi
      A
      license
      A
      quality
      B
      maintenance
      Enables querying table tennis ratings, players, tournaments, and halls from rttf.ru, with respect for robots.txt restrictions.
      5
      MIT

    • chess-results

      odrobnik
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents and terminal users to search players and tournaments, read tournament pages as structured data, and retrieve Austrian championship leagues without login. Also supports checking and, after confirmation, entering team match reports against club rosters and the public results site.
      MIT

    • RZD Tickets MCP

      ex3lite
      A
      license
      Not graded
      quality
      D
      maintenance
      Read-only MCP server that queries Russian Railways (ticket.rzd.ru) for train schedules, car types, prices, and seat availability. It provides official RZD links for manual booking but does not log in, book, or pay.
      31 npm
      2
      MIT

    • Chess.com MCP Server

      pab1it0
      A
      license
      B
      quality
      C
      maintenance
      Provides access to Chess.com player data, game records, and public information through standardized MCP interfaces, allowing AI assistants to search and analyze chess information.
      10
      90
      MIT

    • Fonbet MCP

      bratz121
      F
      license
      Not graded
      quality
      D
      maintenance
      MCP server for reading Fonbet sports events and odds, enabling search for events, retrieval of odds, and value-bet checking via natural language.
      -
    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

    A4.3/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool has a clearly distinct role: search vs. detail for both tournaments and players, plus a dedicated head-to-head endpoint. There is no overlap or ambiguity between the two search tools and their corresponding getter tools.

    Naming Consistency5/5

    All tool names follow the same snake_case verb_noun pattern: search_tournaments, get_tournament, search_players, get_player, get_head_to_head. The naming is uniform and predictable.

    Tool Count5/5

    Five tools is well-scoped for a read-only tournament and player statistics server: two search endpoints, two detail endpoints, and one head-to-head endpoint. Each tool covers a distinct need without bloat.

    Completeness5/5

    The tool surface covers the core read-only domain: finding tournaments, inspecting tournament results, searching players, viewing detailed player histories, and comparing two players. Documented source limitations such as missing tournament match lists are explicitly handled via player profiles, so no critical workflow dead-ends.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources