Skip to main content
Glama
scrapertweeter3-prog

mcp-flatratemath

by scrapertweeter3-prog
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to mcp-flatratemath

No user-submitted related servers found.

    Related Servers

    • cloudprice-mcp

      Albaker-Group
      A
      license
      A
      quality
      A
      maintenance
      MCP server that lets Claude (or any MCP-compatible client) compare on-demand compute + storage pricing across AWS, Azure, and GCP in real time.
      14
      66 PyPI
      1
      MIT

    • UsageWall

      agenciabakucl-coder
      A
      license
      Not graded
      quality
      D
      maintenance
      Live LLM pricing as an MCP server. Ask Claude or any MCP client 'how much does this prompt cost?' and get real numbers from a hand-checked pricing table for every major LLM.
      MIT

    • Agent Bazaar

      TombStoneDash
      A
      license
      Not graded
      quality
      C
      maintenance
      Per-call billing and metering proxy for MCP tool servers. Providers set pricing via the open MCP Billing Spec (MIT), consumers pay through Stripe Connect with signed receipts and SLA monitoring.
      MIT

    • mcp-first-server

      JGPAS
      A
      license
      A
      quality
      B
      maintenance
      MCP server exposing quote and live cryptocurrency price tools, with both local (stdio) and cloud-deployed (HTTP) transports.
      2
      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

    B3.4/5.0

    Scored across 2 tools

    Disambiguation4/5

    The two tools have mostly distinct purposes: cost_per_request prices one payment lane, while compare_lanes ranks up to three lanes side by side. There is some inherent overlap because compare_lanes presumably repeats the single-lane calculation, but the boundary between single-lane pricing and multi-lane comparison is clear enough for an agent.

    Naming Consistency3/5

    Both names use snake_case, but the convention is mixed: compare_lanes follows a verb_noun pattern, while cost_per_request is a noun phrase. The meanings remain readable, but the set is not fully consistent.

    Tool Count3/5

    Two tools is thin for a standalone pricing server, though the domain is narrow enough that a single-lane calculator plus a comparison tool covers the main need. It sits at the borderline of being under-scoped.

    Completeness4/5

    The surface covers pricing one lane and comparing up to three lanes, which addresses the core flat-rate math use case. Minor gaps might include scenario/sensitivity analysis or saving/exporting results, but agents can work around those limitations.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive

    Resources