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.

AiGanak LLM Cost

NPM · @AIGANAK/LLM-COST-MCP

LLM API prices, cost estimates, model comparisons and language token tax for GPT, Claude and Gemini.

+3 this week 74 Trust /100

Last scanned (13 hours ago)

Scores higher than 49% 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 Security98
  • 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
  • 30 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability65
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 723 tokens (~103/item across 7 items; 7 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management53
  • Stability observed for 16 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 8 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
What we tested

Checks we ran (16)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

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.

  • 19 Nov 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.

  • 17 Nov 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.

  • 15 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

  • 13 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

  • 11 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

  • 9 Nov 26 +6
    • Source repository: unverified → pass ▲ security
  • 8 Nov 26 −5
    • Provenance: pass → unverified ▼ security
  • 7 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 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 21 Nov 2026 · Analysed npm/@aiganak/llm-cost-mcp@2026.11.5

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 92 packages
Packages resolved 92
Stale 30
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 7 exposed · ~637 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
compare_models ~155

Price the same request on every model (optionally one provider or tier), cheapest first. Use to choose a model on cost before testing quality.

NameTypeReqDescription
batchboolean–Use asynchronous batch prices (results within 24 hours)
cached_input_tokensinteger–Part of input_tokens read from the prompt cache
datestring–Price on this date (YYYY-MM-DD), including announced changes; default today
input_tokensintegeryesPrompt tokens per request, including cached tokens
output_tokensintegeryesOutput tokens per request, including any reasoning/thinking tokens
providerstring––
requestsinteger–Number of requests to price
tierstring––

No output schema declared.

No examples provided.

estimate_cost ~147

Cost in USD of N requests on one model, with input/output breakdown, caching, batch, long-context surcharges and announced price changes.

NameTypeReqDescription
batchboolean–Use asynchronous batch prices (results within 24 hours)
cached_input_tokensinteger–Part of input_tokens read from the prompt cache
datestring–Price on this date (YYYY-MM-DD), including announced changes; default today
input_tokensintegeryesPrompt tokens per request, including cached tokens
modelstringyes–
output_tokensintegeryesOutput tokens per request, including any reasoning/thinking tokens
requestsinteger–Number of requests to price

No output schema declared.

No examples provided.

estimate_text_cost ~89

Estimate how many tokens a text takes on a model and what N such messages cost as input or output, using measured tokens-per-character for its language. Detects the script if language is omitted.

NameTypeReqDescription
asstring––
languagestring––
messagesinteger–How many messages of this size
modelstringyes–
textstringyes–

No output schema declared.

No examples provided.

get_model_price ~72

Full pricing for one model: standard, cached input, cache write, batch, long-context surcharge, announced future price changes and the provider's source page.

NameTypeReqDescription
modelstringyesAPI model ID or name, e.g. gpt-6.1-terra or Claude Sonnet 5.5

No output schema declared.

No examples provided.

list_models ~47

List current OpenAI, Anthropic and Google API models with standard, cached-input and batch prices in USD per million tokens.

NameTypeReqDescription
providerstring––
tierstring––

No output schema declared.

No examples provided.

price_changes ~34

Dated, sourced log of LLM API price changes and pricing announcements (newest first).

NameTypeReqDescription
limitinteger––

No output schema declared.

No examples provided.

token_tax ~93

How many more tokens the same text takes in a language than in English, on each measured model (OpenAI GPT-6, Claude 5.x, Gemini 3.x, Gemini 4 Argon). 22 languages incl. Hindi, Tamil, German, Japanese. Omit language to list all.

NameTypeReqDescription
languagestring–Language name or code, e.g. Hindi, ta, German, Hinglish

No output schema declared.

No examples provided.

Install

How do I install the AiGanak LLM Cost MCP server?

AiGanak LLM Cost runs locally as an npm package, launched with npx -y @aiganak/llm-cost-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @aiganak/llm-cost-mcp

# add to Claude Code
claude mcp add aiganak-llm-cost -- npx -y @aiganak/llm-cost-mcp
Common questions

What is the AiGanak LLM Cost MCP server?

AiGanak LLM Cost is an MCP server listed in the public MCP registry as io.github.AiGanak/llm-cost. LLM API prices, cost estimates, model comparisons and language token tax for GPT, Claude and Gemini. This page covers its npm package (@aiganak/llm-cost-mcp).

Is the AiGanak LLM Cost MCP server safe to use?

AiGanak LLM Cost scores 74 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 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 AiGanak LLM Cost MCP server expose?

AiGanak LLM Cost exposes 7 tools: list_models, get_model_price, estimate_cost, compare_models, token_tax, and 2 more. Their descriptions and schemas cost roughly 637 tokens of context every time the server is loaded.

Is the AiGanak LLM Cost MCP server still maintained?

AiGanak LLM Cost is still listed as active in the MCP registry. We last reached this channel on 21 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 AiGanak LLM Cost MCP server under?

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

What did VerifyMCP test on the AiGanak LLM Cost MCP server?

VerifyMCP ran 16 checks on AiGanak LLM Cost, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.