Skip to main content
Glama
firstshout

claude-cost-mcp

by firstshout
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to claude-cost-mcp

No user-submitted related servers found.

    Related Servers

    • contextburn

      arsentev-ai
      A
      license
      B
      quality
      C
      maintenance
      Lets a coding agent inspect its own run efficiency mid-session from local Claude Code transcripts, exposing the share of paid tokens that became model output versus context re-reading. Ships two stdio tools — one returning the shares as structured data and one returning the full cost-weighted report — with no network calls.
      2
      MIT

    • AI Impact MCP

      anchetadev
      F
      license
      A
      quality
      D
      maintenance
      Estimates the environmental footprint of your AI use — energy (kWh), miles driven, water used for cooling, and CO₂ — plus a prompt-efficiency score, working with any AI client by measuring token usage.
      9
      -

    • claudeusage

      syk8015
      A
      license
      A
      quality
      C
      maintenance
      Analyzes local Claude Code logs to measure subscription value, waste, and rate-limit usage, including chat share and current limits, without uploading data.
      4
      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.1/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool has a clear, distinct purpose: batch savings, caching break-even, provider comparison, cost estimation, and token estimation. No overlap between them.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun snake_case pattern (e.g., batch_savings, estimate_cost), making them predictable.

    Tool Count5/5

    Five tools is an appropriate size for a cost-estimation server, each covering a necessary aspect without being excessive or insufficient.

    Completeness4/5

    The tool set covers core cost estimation, token counting, batch savings, caching efficiency, and provider comparison. Minor gaps like historical usage tracking exist but are not essential for the stated purpose.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources