Skip to main content
Glama
LarryAtGU

Tank Fight MCP

by LarryAtGU
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to Tank Fight MCP

No user-submitted related servers found.

    Related Servers

    • jev-studio

      utk2103
      A
      license
      A
      quality
      A
      maintenance
      Serves TypeSafe's Jev ruleset to MCP hosts as a prompt and instruction tool, enabling agents to experiment with Jev's natural-language decision capabilities.
      1
      38 PyPI
      16
      MIT

    • 17-0 MCP Server

      Rocniubi
      A
      license
      A
      quality
      C
      maintenance
      Exposes the canonical 17-0 knowledge surface including game rules, roster constraints, and entry points for the NFL roster strategy game to MCP-compatible AI clients.
      2
      MIT

    • mcpstub

      jovial-liu
      A
      license
      Not graded
      quality
      B
      maintenance
      Serves deterministic MCP protocol fixtures generated from tool contracts, enabling testing of MCP clients, gateways, and agent harnesses without live credentials or external services.
      MIT

    • 20-0 MCP Server

      rocnubie
      A
      license
      A
      quality
      C
      maintenance
      Read-only MCP server exposing the 20-0 NFL perfect season game knowledge surface, including game modes, roster picks, scenarios, FAQ, and official links to AI clients.
      2
      MIT

    • swagger-mcp

      emreycolakoglu
      A
      license
      A
      quality
      D
      maintenance
      A read-only MCP server for navigating OpenAPI / Swagger specifications, enabling agents to search endpoints, retrieve parameters and schemas, and inspect authentication without loading the full spec into context.
      9
      14 npm
      MIT
    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.7/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool has a distinct purpose: listing sections, getting a section, searching the spec, resolving level semantics, retrieving maze layouts, and listing open questions. No overlaps or ambiguity.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern (list_, get_, search_, resolve_, open_), making the API predictable and easy to navigate.

    Tool Count5/5

    Six tools is well-scoped for a specification server, covering all necessary access patterns without unnecessary redundancy or bloat.

    Completeness5/5

    The tool set fully covers the domain: discovering, retrieving, searching, interpreting, and visualizing spec details, plus handling open questions. No obvious gaps.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources