Skip to main content
Glama
gralliry

opencode-balance-mcp

by gralliry
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to opencode-balance-mcp

No user-submitted related servers found.

    Related Servers

    • Apitaco MCP Server by myapitaco

      Apitaco MCP Serverofficial

      myapitaco
      A
      license
      Not graded
      quality
      B
      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.
      MIT

    • claude-usage

      drmuzikbpn
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables Claude Code sessions to check account rate-limit headroom, local token spend, and live session status, with read-only MCP tools for limits, summaries, token usage, and session listing.
      MIT

    • GitHub Copilot Usage MCP

      lucasliet
      A
      license
      A
      quality
      F
      maintenance
      An MCP server that retrieves current GitHub Copilot usage data, including quotas, limits, and usage statistics. It allows AI agents to monitor premium interaction status and detailed account usage via raw or formatted summaries.
      3
      10 npm
      MIT
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    A4.4/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools query distinct resources: one for Go subscription quota and one for Zen prepaid balance. Their descriptions clearly differentiate the data returned (usage percentages vs. balance in USD units), making confusion unlikely.

    Naming Consistency5/5

    Both tool names follow the exact same pattern: 'query_' prefix followed by the resource type ('go_usage' and 'zen_balance'). This is fully consistent and predictable.

    Tool Count4/5

    With only two tools, the surface is minimal, but the server's scope is narrowly defined as querying two distinct balance types. The count feels appropriate given the focused purpose, though slightly thin if broadenability was expected.

    Completeness4/5

    The server covers the two core balance query operations for its domain. Missing a combined query or historical data are minor gaps that agents can work around, but the essential read operations are present.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources