mcpcost
Related Servers
Alternatives to mcpcost
- AlicenseAqualityBmaintenanceMonitor MCP server health, uptime, response times, and Azure DevOps pipeline status1412 npm1MIT
- AlicenseNot gradedqualityDmaintenanceProvides tools to count tokens, estimate API costs, optimize prompts, and compare AI model pricing for multiple LLMs.59 npmMIT
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables agents to look up and search servers from the official MCP registry, probe any server live for availability, protocol, auth, tools and context-token cost, and retrieve registry-wide statistics. Also supplies a CLI and GitHub Action that measure how many tokens your own configured servers' tool definitions consume against a budget.MIT
- AlicenseBqualityFmaintenanceTrack LLM token costs across Claude, GPT and Gemini. MCP server + CLI with optimization hints and $ savings estimates.89 npm1MIT
- AlicenseNot gradedqualityDmaintenanceLive 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
- AlicenseNot gradedqualityDmaintenanceMCP server for deterministic, zero-dependency context-window math, enabling token estimation, text truncation, and budget reporting without a tokenizer.MIT
- AlicenseNot gradedqualityDmaintenanceDiagnoses MCP server token costs, finds duplicates, grades efficiency, and generates optimization reports.47 npm1MIT
- AlicenseNot gradedqualityAmaintenanceEnables auditing MCP servers' tools by their estimated context token cost, ranking verbose names, descriptions, and schemas before they consume the agent window. Can run as an MCP tool so agents can budget their own context.1MIT
TDQS
Scored across 6 tools
Each tool targets a distinct axis of the domain: registry lookup by name, discovery/ranking by query, side-by-side comparison, whole-registry aggregates, single-server live measurement, and whole-config measurement. The descriptions explicitly cross-reference the right alternative for each edge case (unknown name -> measure_server, no name -> search_servers), leaving essentially no room for misselection.
Five of six names follow a clear verb_noun pattern (lookup_server, search_servers, compare_servers, measure_config, measure_server) with consistent snake_case. registry_summary breaks the pattern as noun_noun, a minor deviation that is still readable and unambiguous.
Six tools is well within the sweet spot, and each earns its place: three read-only board tools, one aggregate, and two measurement tools split sensibly by scope (single server vs. config file). No redundant or filler tools.
The surface covers discovery, detail, comparison, aggregate baselines, and live measurement of both individual servers and full configs, including graceful handling of auth failures and timeouts. Minor gap: no per-tool token breakdown within a server, only totals, so an agent cannot see which tool in a server is expensive.