Skip to main content
Glama

Related Servers

Alternatives to maxtoken

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables read-only viewing of 0G Router account credits and usage across multiple accounts through MCP, exposing status, balances, and model pricing without triggering inference or payments.
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Exposes three MCP tools that let Claude Desktop, Cursor, Claude Code, and Cline query an account's current balance in USD, retrieve token and cost usage statistics for the last N days, and list supported models with per-million-token pricing. Answers questions like "How much have I spent in the last 30 days?" by calling those tools directly from any MCP-compatible client.
      3
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables users to query AI provider quotas and balances inside MCP clients, returning a summary table or per-platform details while isolating failures and keeping API tokens out of configuration.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Lets a coding agent inspect its own account's subscription limit windows, usage, and cost history, and decide whether to pause and sleep until a limit resets rather than failing mid-task. Supports multiple accounts and providers such as Claude Code and Codex.
      MIT

    TDQS

    B3.3/5.0

    Scored across 2 tools

    Disambiguation4/5

    The two tools have mostly distinct purposes: one focuses on utilization/burn-rate analytics, while the other focuses on real-time balance and quota status. However, both report used quota, remaining ratio, and reset timing, so an agent could occasionally confuse which tool to use for quota-related questions.

    Naming Consistency4/5

    Both names follow a verb_noun pattern and are readable, but they use different verbs (get_ vs query_) for similar read operations. This is a minor inconsistency rather than a serious problem.

    Tool Count3/5

    Two tools is thin for a monitoring server, even if the domain is narrow. The surface feels minimal and may require agents to infer too much from only two operations.

    Completeness4/5

    The tools cover the core monitoring needs: utilization metrics and real-time balance/quota status across GLM and Kimi plans. Minor gaps remain, such as account listing or historical trend queries, but core workflows are covered.