OptimToken
REMOTE · OPTIMTOKEN-MCP.OPTIMNOW.IO
Compare LLM API and cloud compute pricing, estimate workload costs, pick a model within budget.
Available components
Last scanned (21 hours ago)
Scores higher than 89% of remote servers
Reachable. Last reached 4 Nov 2026.
Category AI and Machine Learning
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability74
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 2459 tokens (~245/item across 10 items; 5 tools + 5 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management90
- Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
- Supports UI / widget rendering.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Probed https://optimtoken-mcp.optimnow.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=optimtoken-mcp.optimnow.io | CN=YE1,O=Let's Encrypt,C=US | 7 Oct 2026 | 5 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 6d007eaf5380c56ae57ed75c616c47c179f |
| SANs: optimtoken-mcp.optimnow.io | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of optimtoken-mcp.optimnow.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 38690 | 8 | Verified |
| optimnow.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://optimtoken-mcp.optimnow.io/mcp | Verified | 200 | |
| http (plaintext) | http://optimtoken-mcp.optimnow.io/mcp | HTTPS enforced | 301 | https://optimtoken-mcp.optimnow.io/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
compare-compute-pricing Compare Cloud Compute Pricing ~500
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`.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Instance category. Must be one of these exactly (case-insensitive): General Purpose, Compute Optimized, Memory Optimized, Storage Optimized, GPU / Accelerated, Burstable. Any other string returns zer… |
| limit | number | – | Max instances to return (default: 20) |
| maxMemory | number | – | Maximum memory in GiB |
| maxVCPUs | number | – | Maximum number of vCPUs |
| minMemory | number | – | Minimum memory in GiB |
| minVCPUs | number | – | Minimum number of vCPUs |
| processor | string | – | Processor. Matched by exact equality (case-insensitive), so a partial value like 'H100' returns nothing. Known values: Intel, AMD, Graviton, Ampere, NVIDIA A100, NVIDIA H100, NVIDIA L4, NVIDIA T4, NV… |
| provider | string | – | Cloud provider. Must be one of these exactly (case-insensitive): AWS, Azure, GCP, DigitalOcean, OCI, OVH, Alibaba. Any other string returns zero matches rather than an error. |
| region | string | – | Pricing region: us-east, us-west, europe, asia-pacific. Default: us-east |
| sortBy | string | – | Sort by: price, vcpus, memory, pricePerVCPU. Default: price |
| useCase | string | – | Use case. Must be one of these exactly (case-insensitive): Web App, Database, HPC, ML & AI, Dev/Test, Big Data. Any other string returns zero matches rather than an error. |
| Name | Type | Req | Description |
|---|---|---|---|
| catalogSize | number | yes | – |
| error | string | – | – |
| instances | array | yes | – |
| matchingCount | number | yes | – |
| provenance | object | – | – |
| source | string | yes | – |
No examples provided.
compare-llm-models Compare LLM Models ~654
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.
| Name | Type | Req | Description |
|---|---|---|---|
| capability | string | – | Capability, matched by exact equality (case-insensitive): Text, Vision, Reasoning, Agents, Image Gen, Audio. Any other string returns zero matches. There is no Code capability: for what coding costs,… |
| category | string | – | Price tier, matched by exact equality (case-insensitive): Frontier, Mid-tier, Budget, Image. This is cost only — self-hostability is the separate `openness` axis. |
| limit | number | – | Max models to return (default: 15) |
| maxInputPrice | number | – | Max input price per 1M tokens in USD |
| maxOutputPrice | number | – | Max output price per 1M tokens in USD |
| minElo | number | – | Minimum Chatbot Arena ELO score. Typical range 1000-1500; ~1400 is roughly frontier-class. Models with no ELO score never satisfy this. |
| openness | string | – | Filter by self-hostability, derived from the licence: Open source, Open weights, Proprietary, Unknown |
| provider | string | – | Filter by provider name (e.g. 'OpenAI', 'Anthropic', 'Google') |
| useCasePreset | string | – | Workload shape, which sets tokens per request: supportTicket (1.5k in / 500 out), knowledgeQA (2k / 800), meetingSummary (10k / 1.2k, batch-eligible), marketingContent (2.5k / 1.8k), codingTask (3k /… |
| volumePreset | string | – | Monthly request volume: 10k, 100k, or 1m. Default: 100k |
| Name | Type | Req | Description |
|---|---|---|---|
| catalogSize | number | yes | – |
| dataAsOf | string | – | – |
| eloAsOf | string | yes | – |
| error | string | – | – |
| finopsBadge | object | – | – |
| matchingCount | number | yes | – |
| models | array | yes | – |
| provenance | object | – | – |
| source | string | yes | – |
| useCaseLabel | string | yes | – |
| volumeLabel | string | yes | – |
No examples provided.
compare-models-side-by-side Compare Models Side by Side ~235
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`.
| Name | Type | Req | Description |
|---|---|---|---|
| models | array | yes | 2-4 model names to compare, e.g. ['GPT-4o', 'Claude Opus 5', 'Gemini 3.1 Pro'] |
| volumePreset | string | – | Monthly request volume: 10k, 100k, or 1m. Default: 100k |
| Name | Type | Req | Description |
|---|---|---|---|
| dataAsOf | string | – | – |
| eloAsOf | string | yes | – |
| error | string | – | – |
| models | array | yes | – |
| provenance | object | – | – |
| resolution | array | yes | – |
| source | string | yes | – |
| volume | number | yes | – |
| volumeLabel | string | yes | – |
No examples provided.
estimate-llm-cost Estimate LLM Cost ~501
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.
| Name | Type | Req | Description |
|---|---|---|---|
| customInputTokens | integer | – | Custom input tokens per request. Must be supplied TOGETHER with customOutputTokens — either alone is ignored and the preset is used. A custom shape assumes no cacheable prefix and no batch eligibilit… |
| customOutputTokens | integer | – | Custom output tokens per request. Must be supplied TOGETHER with customInputTokens — either alone is ignored and the preset is used. |
| modelName | string | – | Model name, e.g. 'GPT-4o'. A partial name matches up to 5 models and ALL of them are costed. If omitted, the first 8 catalogue entries are used — that is catalogue order, not a quality ranking. |
| monthlyVolume | integer | – | Exact monthly request count, any integer (default 100,000). This tool does not take the 10k/100k/1m presets the other cost tools use. |
| useCasePreset | string | – | Workload shape, which sets tokens per request: supportTicket (1.5k in / 500 out), knowledgeQA (2k / 800), meetingSummary (10k / 1.2k, batch-eligible), marketingContent (2.5k / 1.8k), codingTask (3k /… |
| Name | Type | Req | Description |
|---|---|---|---|
| dataAsOf | string | – | – |
| eloAsOf | string | yes | – |
| error | string | – | – |
| modelCosts | array | yes | – |
| provenance | object | – | – |
| source | string | yes | – |
| volume | number | yes | – |
No examples provided.
recommend-llm-model Recommend an LLM Model ~500
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.
| Name | Type | Req | Description |
|---|---|---|---|
| maxMonthlyBudget | number | – | Maximum monthly budget in USD at the given volume. Tested against the LIST-price monthly cost, not the caching/batch-optimized cost. |
| minElo | number | – | Minimum Chatbot Arena ELO score. Typical range 1000-1500; ~1400 is roughly frontier-class. Models with no ELO score never satisfy this. |
| openness | string | – | Require a self-hostability bucket, derived from the licence: Open source, Open weights, Proprietary, Unknown |
| requiredCapability | string | – | Capability the model must have: Text, Vision, Reasoning, Agents, Image Gen, Audio. There is no Code capability: for coding, pass useCasePreset codingTask. |
| useCasePreset | string | yes | Workload shape, which sets tokens per request: supportTicket (1.5k in / 500 out), knowledgeQA (2k / 800), meetingSummary (10k / 1.2k, batch-eligible), marketingContent (2.5k / 1.8k), codingTask (3k /… |
| volumePreset | string | – | Monthly request volume: 10k, 100k, or 1m. Default: 100k |
| Name | Type | Req | Description |
|---|---|---|---|
| candidateCount | number | yes | – |
| catalogSize | number | yes | – |
| dataAsOf | string | – | – |
| eloAsOf | string | yes | – |
| error | string | – | – |
| nearMisses | array | yes | – |
| overConstrained | boolean | yes | – |
| provenance | object | – | – |
| rankedCount | number | yes | – |
| recommendations | array | yes | – |
| roiCalculatorUrl | string | yes | – |
| source | string | yes | – |
| useCaseLabel | string | yes | – |
| volume | number | yes | – |
| volumeLabel | string | yes | – |
No examples provided.
How do I install the OptimToken MCP server?
OptimToken is a hosted endpoint at https://optimtoken-mcp.optimnow.io/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · optimtoken-mcp.optimnow.io
claude mcp add --transport http optimnow-ai-pricing-hub 'https://optimtoken-mcp.optimnow.io/mcp'
What is the OptimToken MCP server?
OptimToken is an MCP server listed in the public MCP registry as io.github.OptimNow/ai-pricing-hub. Compare LLM API and cloud compute pricing, estimate workload costs, pick a model within budget. This page covers its hosted endpoint (https://optimtoken-mcp.optimnow.io/mcp).
Is the OptimToken MCP server safe to use?
OptimToken scores 84 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the OptimToken MCP server expose?
OptimToken exposes 5 tools: compare-llm-models, estimate-llm-cost, compare-models-side-by-side, recommend-llm-model, compare-compute-pricing. Their descriptions and schemas cost roughly 2,390 tokens of context every time the server is loaded.
Does the OptimToken MCP server require authentication?
No. We connected to OptimToken without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the OptimToken MCP server still maintained?
OptimToken is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.