@f3d1/llmkit-mcp-server

MCPattested
v0.4.10f3d1MITUpdated 1mo agonpmGitHub

AI cost tracking: 11 tools for spend, budgets, and Claude Code costs

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.

Attested build
A verified provenance attestation binds this artifact to the listed repository. Nobody has claimed the listing yet — this proves where the code was built, not who stands behind it.
89Downloads/wk
16GitHub stars
5Forks
1mo agoLast update
Reads these credentials
  • LLMKIT_API_KEYAPI keyoptional

    LLMKit API key. Optional: local tools work without it.

Declared by the author in the official MCP registry. Forge does not store, broker, or ever see these values — the config below is scaffolded with placeholders you fill in locally.

Package
Authorf3d1
LicenseMIT
Version0.4.10
Sourcenpm+mcp-registry
npm@f3d1/llmkit-mcp-server
GitHubsmigolsmigol/llmkit
SBOMCycloneDX 1.6 ↓
Trust Status
A
85/100Trusted
✓Listed in Forge index+10/10
✓Identity verified · attested build+20/20
—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)+5/5
—npm maintainer match+0/5
→ Publisher: add the verified GitHub login to the npm package's maintainers (npm owner add <login>)
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusIdentity verified
PublisherUnverified
SignatureUnsigned
Domain—
Provenance✓ Sigstore-verified · ab147c4
Dependencies✓ 60 resolved+ · none vulnerable
Tool surface15 tools · none privileged
Security scan✓ Cleanv0.4.10 · 1mo agoHow well does this scan work?
EvalsNone
IndexedAug 16, 2026

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

Tools

15 tools · none privileged
Statically extracted from the published packagev0.4.10 · 1mo 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.

cost-reportNo description published

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

periodNo description published

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

budget-checkNo description published

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

session-summaryNo description published

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

llmkit_usage_statsNo description published

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

llmkit_cost_queryNo description published

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

llmkit_list_keysNo description published

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

llmkit_budget_statusNo description published

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

llmkit_healthNo description published

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

llmkit_session_summaryNo description published

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

llmkit_local_sessionNo description published

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

llmkit_local_projectsNo description published

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

llmkit_local_cacheNo description published

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

llmkit_local_forecastNo description published

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

llmkit_local_agentsNo description published

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

0 of 15 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

AI cost tracking: 11 tools for spend, budgets, and Claude Code costs

Keywords
mcpmodel-context-protocolclaude-codecursorllmaicost-trackingai-agents
Alternatives
Comparing tool surfaces…

Tools exposed

15 tools · none privileged · observed by static extraction. A tool surface is what one scan read on one day, not a live capability list.

Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.

No dependency coverage

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