Skip to main content
Glama
Sign In
model-price-radar

model-price-radar

by alialtunar
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to model-price-radar

No user-submitted related servers found.

    Related Servers

    • or-pricer

      viperdriver2000
      F
      license
      Not graded
      quality
      B
      maintenance
      MCP server that provides OpenRouter model pricing data, enabling price lookups, trending/cheapest lists, and model searches without an API key.
      -
    • indextkn MCP server

      indextkn MCP serverofficial

      indextkn
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables agents to query live AI model pricing, compare providers, and calculate token workload costs from current published prices.
      MIT

    • llm-price-mcp

      under-stand
      A
      license
      A
      quality
      A
      maintenance
      Enables AI agents to list and compare LLM API prices per million tokens, rank the cheapest models by context and keyword, look up GPU rental rates per hour by provider, and estimate self-hosting cost per million tokens against API pricing. Pricing data comes from OpenRouter's public models endpoint plus a dated GPU price CSV, with source URLs and explicit notes when data is missing.
      5
      MIT

    • llm-oracle

      weiseer
      F
      license
      Not graded
      quality
      D
      maintenance
      Provides real-time LLM pricing and availability data as an MCP server, enabling AI agents to make optimal model routing decisions at inference time with cited pricing sources.
      -
    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

    A3.8/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool targets a distinct question: catalog search, workload cost estimation, per-model price history, market-wide price changes, and provider-level comparison. The descriptions clarify scope, especially between model_price_history (single model over time) and price_changes (market-wide since a month), so misselection is unlikely.

    Naming Consistency4/5

    All tool names use snake_case and are descriptive. Three follow a verb_noun pattern (find_models, estimate_cost, compare_providers) while two are noun phrases (model_price_history, price_changes), a minor deviation but still readable and predictable overall.

    Tool Count5/5

    Five tools is well-scoped for an LLM pricing radar: search, cost estimation, historical tracking, market change detection, and provider comparison. Each tool earns its place without redundancy or thin coverage.

    Completeness5/5

    The surface covers the core lifecycle of price discovery: finding models, estimating workload costs, tracking per-model price history, detecting market-wide changes, and comparing providers. No obvious dead ends exist for the stated domain of OpenRouter price monitoring.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources