llmledger
Related Servers
Alternatives to llmledger
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceLive LLM API pricing: current token prices, model comparisons, cheapest-model lookups, and The LLM Price Index for 150+ models across 20+ providers, re-verified daily. No API key required.41MIT
- AlicenseNot gradedqualityBmaintenanceEnables assistants to access up-to-date LLM pricing, context windows, and model identifiers, with tools to estimate costs, find cheapest models, and check scheduled price changes.27 npmMIT

apipriceindex-mcpofficial
AlicenseAqualityAmaintenanceGives AI agents live, verified LLM API prices from apipriceindex.com, enabling cost estimation, model search, and price lookups with verification metadata.329 PyPIMIT- AlicenseNot gradedqualityDmaintenanceProvides live LLM pricing data from OpenRouter, enabling agents to search models, get pricing, estimate costs, and compare models.28 npmMIT

OptimToken MCPofficial
AlicenseNot gradedqualityAmaintenanceEnables AI assistants to fetch live, dated prices for LLM models and cloud compute instances across providers, compare and recommend models, and estimate monthly costs based on workload-specific token shapes and constraints.MIT- AlicenseAqualityBmaintenanceEnables MCP clients to query live OpenRouter LLM pricing and monthly price history back to 2023 without API keys. It supports finding the cheapest model for a job, estimating workload costs, tracking price changes, and comparing providers.532 PyPIMIT
TDQS
Scored across 10 tools
Several tools overlap in purpose: find_models, compare_models, and suggest_for_project all recommend models; estimate_cost, forecast_job, and local_or_cloud all report costs from different angles; estimate_time and forecast_job both cover timing. Descriptions help clarify boundaries, but an agent could still misselect among them.
All names use snake_case, but conventions are mixed: most are verb_noun (find_models, estimate_cost), while others are noun phrases or adjectives (price_history, not_yet_priced, local_or_cloud). The set is readable but does not follow a predictable verb-first pattern.
With 10 tools, the set is well within the ideal 3-15 range for a specialized LLM pricing and forecasting server. Each tool addresses a distinct facet of the domain, and the count does not feel bloated or thin.
The surface covers model discovery, comparison, cost/time estimation, price history, predictive signals, project suggestions, run logging, job forecasting, and local-vs-cloud analysis. Minor gaps exist, such as direct model lookup by name or a full catalogue enumeration, but core workflows are covered.