Skip to main content
Glama
justinbchau

faceit-mcp

by justinbchau
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to faceit-mcp

No user-submitted related servers found.

    Related Servers

    • faceit-mcp

      sebazai
      A
      license
      A
      quality
      D
      maintenance
      Enables AI assistants to query the FACEIT platform for players, matches, hubs, and tournaments through typed MCP tools generated from the FACEIT Data API v4.
      64
      MIT

    • faceit-mcp

      tqakdev
      A
      license
      Not graded
      quality
      D
      maintenance
      Live CS2 FACEIT data for Claude — query player stats, match history, head-to-head comparisons, recent form, per-map breakdowns, and full match scoreboards for any public FACEIT player using natural language.
      1
      MIT

    • opendota-mcp

      yuxiang115
      A
      license
      B
      quality
      B
      maintenance
      Enables LLMs and agents to query Dota 2 matches, players, heroes, teams, and pro scene data through the OpenDota API, with numeric IDs resolved to localized names and readable labels.
      42
      MIT

    • Chess.com MCP Server

      Gelberm
      F
      license
      B
      quality
      D
      maintenance
      Provides tools to interact with the Chess.com Public API for fetching real-time player profiles and detailed game statistics. It enables LLMs to access information like player ratings, win/loss records, and current online status.
      2
      -
    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.1/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action: player lookup, player stats, match history, match stats, and match details. The descriptions clearly differentiate match stats (per-round/per-player numbers) from match details (general info), so an agent can reliably choose the right tool.

    Naming Consistency4/5

    All tools follow a faceit_<verb>_<noun> pattern with snake_case. The only deviation is 'find_player' using 'find' instead of 'get', but this is minor and the pattern remains predictable across the set.

    Tool Count5/5

    Five tools is well-scoped for a focused FACEIT CS2 stats server. Each tool covers a necessary lookup or retrieval step without redundancy, and the count is squarely in the ideal 3-15 range.

    Completeness5/5

    The tool surface covers the core read-only workflow: finding a player, retrieving their stats, listing match history, and then fetching both summary and detailed stats for a match. There are no obvious dead ends for typical use cases; the missing operations are not essential for this domain.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources