Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

statlyte — live LLM pricing

NPM · STATLYTE

Live LLM pricing, context windows and model ids, read from each vendor's own page every 3 hours.

Available components

0 this week 83 Trust /100

Last scanned (9 hours ago)

Scores higher than 76% of npm servers

Category AI and Machine Learning

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency45
Schema Quality & AI Usability74
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 301 tokens (~60/item across 5 items; 5 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage87
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 60% of tool parameters carry a description.Partial
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 5 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
Changelog

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.

  • 2 Nov 26 0
    • Stability: 0.97 → pass security
  • 1 Nov 26 0
    • Stability: pass → 0.97 functional
  • 26 Oct 26 0
    • Stability: 0.97 → pass security
  • 25 Oct 26 0
    • Stability: pass → 0.97 functional
    • Package version: 0.1.0 → 0.1.1 functional
  • 19 Oct 26 0
    • Stability: 0.97 → pass security
    • Security disclosure: unverified → fail ▼ functional
  • 18 Oct 26 +1
    • Security disclosure: fail → unverified ▼ functional
  • 16 Oct 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.

  • 14 Oct 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.

Diagnostics

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 5 Nov 2026 · Analysed npm/statlyte@0.1.1

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 5 exposed · ~301 tokens

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 →

Tool Tokens
cheapest_for_workload ~71

Rank every generally-available model by what a monthly token volume would cost. Use to answer "what is the cheapest model for this workload".

NameTypeReqDescription
inputPerMonthnumber–input tokens per month
limitnumber––
outputPerMonthnumber–output tokens per month

No output schema declared.

No examples provided.

estimate_cost ~58

Cost in USD of a call or workload against one model, given raw token counts.

NameTypeReqDescription
cacheReadnumber––
inputnumber–input tokens
modelstringyes–
outputnumber–output tokens

No output schema declared.

No examples provided.

get_model_pricing ~56

Current published pricing and specs for one model. Accepts a statlyte id (anthropic/claude-opus-5) or a vendor API id (gpt-5-mini).

NameTypeReqDescription
modelstringyes–

No output schema declared.

No examples provided.

list_models ~83

List LLM models with current published pricing (USD per million tokens, or nonTokenPrice for audio/image models billed per minute/character/etc), context windows and API identifiers. Optionally filter by provider.

NameTypeReqDescription
includeRetiredboolean–Include deprecated and retired models
providerstring–e.g. anthropic, openai, google, mistral

No output schema declared.

No examples provided.

scheduled_price_changes ~33

Price changes vendors have announced for a future date, with the old and new figures. Check before committing to a model.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Install

How do I install the statlyte — live LLM pricing MCP server?

statlyte — live LLM pricing runs locally as an npm package, launched with npx -y statlyte. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · statlyte

# add to Claude Code
claude mcp add richardwilkinson9-statlyte -- npx -y statlyte
Common questions

What is the statlyte — live LLM pricing MCP server?

statlyte — live LLM pricing is an MCP server listed in the public MCP registry as io.github.richardwilkinson9/statlyte. Live LLM pricing, context windows and model ids, read from each vendor's own page every 3 hours. This page covers its npm package (statlyte).

Is the statlyte — live LLM pricing MCP server safe to use?

statlyte — live LLM pricing scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. 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 statlyte — live LLM pricing MCP server expose?

statlyte — live LLM pricing exposes 5 tools: list_models, get_model_pricing, estimate_cost, cheapest_for_workload, scheduled_price_changes. Their descriptions and schemas cost roughly 301 tokens of context every time the server is loaded.

Is the statlyte — live LLM pricing MCP server still maintained?

statlyte — live LLM pricing is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the statlyte — live LLM pricing MCP server under?

statlyte — live LLM pricing declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.