OptimToken

io.github.OptimNow由 GitHub 账号 OptimNow 发布v0.4.2更新于 Oct 24, 2026

Compare LLM API and cloud compute pricing, estimate workload costs, pick a model within budget.

已验证Streamable HTTP可网页运行云端与基础设施金融AI 与机器学习

概览

AI 生成的概览

托管型 MCP 服务器,让助手查询最新的 LLM API 与云服务器价格、估算工作负载成本,并在预算内推荐模型。

可以做什么
  • 按价格、质量(ELO)、效率和能力浏览并筛选 LLM 目录
  • 在选定月用量下,将 2 至 4 个指定模型按 8 种用例画像逐一对比
  • 根据自填的 token 数量、缓存命中率和批处理资格估算单次请求与每月成本
  • 针对单一工作负载,在预算、最低 ELO、所需能力等约束下给出排名前三的推荐
  • 按区域和类别比较 AWS、Azure、GCP、DigitalOcean、OCI、OVH 和阿里云的 Linux 按需实例价格
适用场景
当你需要带日期和来源的价格、而不是模型凭记忆给出的数字时适用:例如测算 LLM 工作负载预算、在几个指定模型间取舍,或挑选云实例。所有工具均为只读查询,适合规划与对比场景。
运行要求
需要一个远程 streamable HTTP 端点,无需安装。请按原样添加托管 URL,包含 /mcp 路径且末尾不加斜杠,因为交互式组件仅对该形式渲染。无需任何凭据或环境变量。
安装前请注意
价格来自第三方目录;当主数据源不可达时会回退到 OpenRouter 或内嵌快照,较低层级提供的是未经校正的价格,使用前请查看 provenance 字段和提示信息。内嵌回退数据为手动刷新,可能过期。查询内容会发送到提供方服务器。

安装

在 SourceWeft 中

  1. 打开 控制台中的 OptimToken,将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Web executable,通过 Streamable HTTP。 远程服务在工作区中配置后即可从网页运行时运行。

交给智能体安装

把这段提示词粘贴到 Claude Code、Codex、Cursor 等智能体,或 SourceWeft 对话中。智能体会读取该服务器的安装指南,先向你展示发布者、端点和登录方式,经你同意后再把它添加到你的客户端。密钥不会写进任何命令。

阅读 https://sourceweft.com/mcp/io.github.OptimNow%2Fai-pricing-hub/install.md,并按其中说明把这个 MCP 服务器接入我的客户端。修改任何配置之前,先告诉我它的发布者、端点和登录方式,等我确认。不要把 API 密钥写进命令或我会提交的文件;问我密钥应从哪里获取。

查看智能体所依据的安装指南

其他 MCP 客户端

把它添加到你客户端的 mcpServers 配置中。

{
  "mcpServers": {
    "optimtoken": {
      "type": "http",
      "url": "https://optimtoken-mcp.optimnow.io/mcp"
    }
  }
}

README

OptimToken MCP

Built by OptimNow. Ask an AI assistant what a model or an instance actually costs, and get a dated, sourced figure instead of a number the model remembers from its training data.

[CI] [MCP Server] [ChatGPT Apps] [Node] [Prices] [License: MIT] [GitHub Stars]


Connect in 30 seconds

The server is hosted, so there is nothing to install.

https://optimtoken-mcp.optimnow.io/mcp

Paste it exactly as written, with /mcp and no trailing slash. The widgets render only for that form: the host checks a hash of the URL you entered.

ClientHow to add it
[Claude Code]claude mcp add --transport http optimtoken https://optimtoken-mcp.optimnow.io/mcp
[Claude.ai / Desktop]Settings → Connectors → Add custom connector, paste the URL above
[ChatGPT]Settings → Connectors → Add, paste the URL. Comparisons render as interactive widgets
[Cursor] [Windsurf] [VS Code]Add an HTTP MCP server entry pointing at the URL

Then just ask:

"We send 200k support tickets a month at about 1,500 input tokens each. Which model gives me the best quality per euro, and what would it cost?"


Why this exists

Model prices change weekly, and a language model's idea of them is frozen at its training cutoff. Ask one what Claude or GPT costs and you get a confident answer that was true some months ago, with no date attached and no way to tell. The same applies to cloud instance rates, which additionally vary by region in ways nobody memorises.

This server replaces recall with a lookup:

  • Live prices, not remembered ones. Every LLM figure comes from the OptimToken catalogue, which tracks 250+ models and refreshes daily.
  • Corrected prices. OptimToken keeps a committed price archive, a verified overrides table checked against vendor pricing pages, and an anomaly check that alarms on the half-price and double-price breaks upstream feeds occasionally publish. This server asks that catalogue rather than re-deriving prices itself.
  • Cost per request, not cost per million tokens. Price-per-token comparisons hide the thing you actually pay for. The tools apply your token shape, your cache hit rate and batch eligibility, and return a figure per request and per month.
  • Every answer carries its provenance. Which tier served it, and whether the prices were verified.

Tools

ToolWhat it answers
compare-llm-models"What is out there?" Browse and filter the catalogue on price, quality (Chatbot Arena ELO), efficiency and capabilities, with a self-hostability read from the licence.
recommend-llm-model"Just tell me which one." A ranked top 3 for one workload under your constraints (budget, minimum ELO, required capability, self-hostability), each with a per-constraint satisfied or violated breakdown as the evidence. Over-constrained queries return the nearest misses, labelled as such.
compare-models-side-by-side"How do these specific ones compare?" 2 to 4 named models across all 8 use case profiles at a chosen monthly volume, list and optimized cost for each.
estimate-llm-cost"What will this cost us per month?" Per-request and monthly cost for your own volume, token shape, cache hit rate and batch eligibility.
compare-compute-pricing"What should we run it on?" Compute instance rates across AWS, Azure, GCP, OCI, OVH, DigitalOcean and Alibaba, by region and category.

All five are read-only and take no credentials. Nothing you send is stored.

Use case profiles ship with realistic token shapes, so you do not have to invent them: Support Ticket, Knowledge Q&A, Meeting Summary, Marketing Content, Coding Task, Invoice Processing, Call Summary, Agent Workflow.


Where the numbers come from

optimtoken.optimnow.io is the single source of truth. When it cannot be reached, the server degrades in tiers rather than failing, and says which tier it used.

ToolTier 1Tier 2Tier 3
LLM toolsGET /api/llm-modelsOpenRouter directembedded snapshot
Compute toolGET /api/pricing?region=not availableembedded snapshot (137 rows)

Tiers 2 and 3 serve uncorrected prices, and that matters more than it sounds. An upstream feed once published a frontier model at half its real list price, which halves every monthly figure derived from it. So every response carries a provenance object with pricesVerified, and the lower tiers put a notice at the top of the answer. A fallback should never quietly downgrade correctness.

Tier 1 is accepted only when the catalogue reports that it is itself serving fresh upstream data. If the site is on its own fallback, it carries no corrections, and this server treats it accordingly.


Local development

Requires Node.js 24+.

bash
npm installnpm run dev              # Skybridge dev server + MCP inspector at localhost:3000npm test                 # schema conformance, serialisation precision, data sourcesnpm run build            # widgets + server

The static fallback catalogue is refreshed by hand, not on a schedule:

bash
npm run refresh-fallback

Because it is manual, check its dataAsOf before trusting a tier-3 response. An unrefreshed fallback ages silently.

text
ai-pricing-hub-mcp/├─ server/src/index.ts              # tool + widget registrations├─ server/src/lib/optimtoken-api.ts # the one base URL constant, fetch and timeout discipline├─ server/src/lib/                  # ranking, efficiency scoring, provenance, normalisation├─ server/src/data/                 # static fallback pricing + region maps└─ web/src/widgets/                 # React widgets rendered in the client

Built with Skybridge, deployed on Fly.io.


The rest of the family

OptimTokenThe web app. Same catalogue, full UI, an AI advisor and a public JSON API.
AI ROI CalculatorDoes the AI business case pay for itself. Same prices, plus harness costs and value modelling.
cloud-finops-skillsFinOps knowledge for AI agents: AWS, Azure, GCP, AI inference, SaaS.
finops-mcp-resourcesMCP servers, tutorials and client guides for cloud cost work.

License

Released under the MIT License.

Prices served by this server come from third-party sources and are provided as is, without warranty. Verify against vendor pricing pages before committing spend.


Questions about your own AI or cloud bill? Talk to OptimNow.

来源:README.md,提交 84296b5

工具

5

compare-llm-models

Compare LLM Models

Browse and filter the whole LLM catalogue and get back a ranked table: price, quality (ELO), efficiency and capabilities. Use this when the user wants to SEE THE FIELD — 'show me models under $1/1M', 'which providers have vision models', 'list open-weight models above ELO 1300'. For a single PICK under a budget use recommend-llm-model; to weigh 2-4 NAMED models against each other use compare-models-side-by-side. Prices come from optimtoken.optimnow.io where reachable; the response's `provenance` says which tier served them and whether they are vendor-verified. Filter by provider, price tier (category), openness, capability, price range, or minimum ELO score. Optionally enrich with business metrics for a use case. Price tier and openness are independent: a model can be Frontier-priced and open-weight at once. Reports both list-price cost and the optimized cost achievable with prompt caching and the batch API. Prices, costs and scores are final as returned: rounded and ranked server-side, and dated by `provenance`. The text block is a numbered table of the same figures.

输入参数limitminElocategoryopennessprovidercapabilityvolumePresetmaxInputPriceuseCasePresetmaxOutputPrice

estimate-llm-cost

Estimate LLM Cost

Cost a workload with EXACT numbers the caller supplies: arbitrary token counts per request and any monthly volume, not just the 10k/100k/1m presets the other cost tools use. Use this for 'about 800 in and 200 out, 4 million calls a month', or to price one named model across every use-case profile. To compare 2-4 named models like for like at a preset volume, use compare-models-side-by-side instead. Provide a model name to get detailed cost breakdowns, or compare costs across all use case presets. Each figure comes twice: list price, and the optimized price achievable with prompt caching and the batch API. Cost figures are final as returned: rounded server-side and dated by `provenance`, with the lever behind each saving, or the reason there is none, named in the text.

输入参数modelNamemonthlyVolumeuseCasePresetcustomInputTokenscustomOutputTokens

compare-models-side-by-side

Compare Models Side by Side

Compare 2-4 named LLM models against all 8 use-case profiles at a chosen monthly volume, showing list and optimized cost for each. Use when the user names specific models to weigh against each other, rather than filtering the whole catalogue. If they also supply their own token counts, or a volume outside 10k/100k/1m, use estimate-llm-cost instead. Every name is resolved against the catalogue and the outcome is reported in `resolution` and in the text: a name that matched nothing, matched several models, or duplicated an earlier pick is stated explicitly, and such a name gets no column rather than a zero cost. Prices and costs are final as returned: rounded server-side and dated by `provenance`.

输入参数models必填volumePreset

recommend-llm-model

Recommend an LLM Model

Pick a model. Returns a ranked top 3 for one workload under optional constraints, each with a per-constraint satisfied/violated breakdown as the evidence. Use this when the user wants an ANSWER rather than a table — 'what should I use for support tickets under $500 a month'. To browse or filter the whole catalogue instead, use compare-llm-models. Constraints: (monthly budget, minimum ELO, required capability, self-hostability). Returns a top 3 as structured facts — efficiency rank, ELO, list and optimized cost, FinOps flag, volatility, and a per-constraint satisfied/violated breakdown. When nothing satisfies every constraint the query is reported as over-constrained, `recommendations` is empty, and the nearest misses are returned in `nearMisses` instead, each carrying the constraint it failed and flagged as a miss in the text. The ranking is computed server-side and is final.

输入参数minEloopennessvolumePresetuseCasePreset必填maxMonthlyBudgetrequiredCapability

compare-compute-pricing

Compare Cloud Compute Pricing

Compare cloud compute instance pricing across AWS, Azure, GCP, DigitalOcean, OCI, OVH, and Alibaba. Filter by region, provider, vCPUs, memory, category, processor, or use case. All prices are Linux on-demand list prices in USD. Not every price column is live: `provenance.priceTypes` says which of each provider's price columns come from a live API, which are static constants, and which are unavailable, and `provenance.staticPriceColumns` lists the non-live ones outright; a savings-plan or reserved rate that appears there is a static estimate, not a live quote. Prices are returned as the catalogue serves them and dated by `provenance`.

输入参数limitregionsortByuseCasecategorymaxVCPUsminVCPUsprovidermaxMemoryminMemoryprocessor

版本历史

4
  1. v0.4.2最新Oct 8, 2026
  2. v0.4.1Oct 7, 2026
  3. v0.4.0Oct 5, 2026
  4. v0.2.0Sep 16, 2026

评分

已满足适用检查项的 100%

该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。

  • 近 30 天内可连通必需25 分
  • 已声明认证方式必需10 分
  • 已列出工具必需15 分
  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分