@comparedge/llm-cost-mcp

MCPcommunity
v1.0.0io.github.imkemit-opsUnknownUpdated 1mo agonpmGitHub

Token cost math for LLM API calls: verified per-1M-token rates for 69 models, 17 providers.

Works in
ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
1mo agoLast update
Package
Authorio.github.imkemit-ops
LicenseUnknown
Version1.0.0
Sourcenpm+mcp-registry
Trust Status
B
60/100Good
Listed in Forge index+10/10
Publisher identity verified+0/20
Publisher: run `forge publish` from the package repo to claim ownership
Ed25519 publish signature+0/5
Included automatically when the publisher runs `forge publish`
Domain verification+0/5
Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
npm Trusted Publishing (Sigstore)+0/5
Publish from GitHub Actions with --provenance so the attestation binds this package to this repo
npm maintainer match+0/5
Earned once your identity is verified above and that login is an npm maintainer of this package
CVE scan · clean+30/30
Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain
Provenance
Dependencies✓ 0 resolved · none vulnerable
Tool surface13 tools · none privileged
Security scan✓ Cleanv1.0.0 · 15d agoHow well does this scan work?
EvalsNone
IndexedJul 12, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

13 tools · none privileged
Statically extracted from the published packagev1.0.0 · 15d ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

list_providersNo description published

This tool published no description. Forge does not invent one.

list_modelsNo description published

This tool published no description. Forge does not invent one.

estimate_costNo description published

This tool published no description. Forge does not invent one.

compare_models_costNo description published

This tool published no description. Forge does not invent one.

cheapest_modelsNo description published

This tool published no description. Forge does not invent one.

monthly_budgetNo description published

This tool published no description. Forge does not invent one.

estimate_my_workflowNo description published

This tool published no description. Forge does not invent one.

workflowNo description published

This tool published no description. Forge does not invent one.

modelNo description published

This tool published no description. Forge does not invent one.

pick_cheapest_modelNo description published

This tool published no description. Forge does not invent one.

taskNo description published

This tool published no description. Forge does not invent one.

forecast_ai_budgetNo description published

This tool published no description. Forge does not invent one.

usageNo description published

This tool published no description. Forge does not invent one.

0 of 13 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

Token cost math for LLM API calls: verified per-1M-token rates for 69 models, 17 providers.

Keywords
mcp
Alternatives
Comparing tool surfaces…

No dependency coverage

This package was last scanned before Forge began storing the resolved tree. The next scan will record it.