Skip to main content
Glama
sebazai

faceit-mcp

by sebazai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to faceit-mcp

No user-submitted related servers found.

    Related Servers

    • faceit-mcp

      justinbchau
      F
      license
      A
      quality
      B
      maintenance
      Enables Claude to query FACEIT CS2 stats including player profiles, lifetime stats, match history, and detailed per-match statistics via the FACEIT Data API.
      5
      -

    • copamind-mcp

      Phemassa
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables interaction with the CopaMind platform via MCP, exposing read-only and write tools for querying match predictions, Monte Carlo simulations, team rankings, and RAG-based explanations, all while maintaining full traceability and reproducibility.
      1
      MIT

    • NBA MCP Server

      SergioCastro02
      A
      license
      A
      quality
      B
      maintenance
      Enables MCP-compatible LLM clients to access live NBA data, including stats, standings, rosters, scores, and box scores via callable tools.
      9
      MIT

    • Relay

      adarshp14
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to access a unified catalog of tools from various APIs (OpenAPI, GraphQL, MCP, Google Discovery) through the MCP protocol.
      MIT

    • fotmob-mcp

      MoRocety
      F
      license
      A
      quality
      B
      maintenance
      Enables querying FotMob football data including matches, match details, teams, leagues, players, and search through MCP-compatible LLM clients.
      6
      -
    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.6/5.0

    Scored across 64 tools

    Disambiguation4/5

    Tools are largely distinct by entity (game, championship, hub, etc.) and action (get, search), with clear descriptions. Some overlap exists among ranking and leaderboard tools, but they are well-differentiated by parameters and context.

    Naming Consistency5/5

    All tools follow a consistent pattern of 'faceit_verb_noun' (e.g., getPlayer, searchHubs). No mixing of casing styles or redundant prefixes. This makes the tool surface predictable.

    Tool Count2/5

    64 tools is excessive for even a broad platform. While the FACEIT API covers many entities, the tool count overwhelms agents, with many niche tools (e.g., getChampionshipGroupRanking vs getLeaderboard) that could be combined.

    Completeness3/5

    The read-only coverage is fairly comprehensive across major entities (players, teams, matches, tournaments, hubs, championships), but there are notable gaps: no write operations, limited filtering on lists, and some missing endpoints like league season listing or live match data.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources