@mukundakatta/promptbudget-mcp

MCPcommunity
v0.2.0Mukunda KattaMIT OR Apache-2.0Updated 5mo agonpmGitHub

MCP server for token-budget-aware text truncation. Helps an LLM fit text into a context window mid-task.

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 →
79Downloads/wk
5mo agoLast update
Package
AuthorMukunda Katta
LicenseMIT OR Apache-2.0
Version0.2.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✓ 60 resolved+ · none vulnerable
Tool surface3 tools · 1 privileged
Security scan✓ Cleanv0.2.0 · 1mo agoHow well does this scan work?
EvalsNone
IndexedAug 26, 2026

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

Tools

3 tools · 1 privileged
Statically extracted from the published packagev0.2.0 · 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.

count_tokensCount the approximate token usage of a text. Optionally compare against a budget and return a 'fits' flag plus overflow. Use as a pre-flight check before assembling a prompt: if count > budget, decide whether to truncate or chunk.

Count the approximate token usage of a text. Optionally compare against a budget and return a 'fits' flag plus overflow. Use as a pre-flight check before assembling a prompt: if count > budget, decide whether to truncate or chunk.

No input schema was published for this tool.

truncate_to_token_budgetprivilegedTruncate text to fit within a token budget. Four strategies: head (keep beginning), tail (keep end, good for chat history), head_tail (drop the middle, keep both ends), and smart_cut (head_tail with a visible cut marker). Use when you need to put long text into an LLM context window without going o…

Truncate text to fit within a token budget. Four strategies: head (keep beginning), tail (keep end, good for chat history), head_tail (drop the middle, keep both ends), and smart_cut (head_tail with a visible cut marker). Use when you need to put long text into an LLM context window without going o…

No input schema was published for this tool.

chunk_to_budgetSplit a long text into multiple chunks, each at most max_tokens tokens, with optional overlap between adjacent chunks. Use when you have source material too long for one prompt and want to feed it through in pieces (for example, RAG ingestion or a fan-out summarize pattern). Overlap is useful so a…

Split a long text into multiple chunks, each at most max_tokens tokens, with optional overlap between adjacent chunks. Use when you have source material too long for one prompt and want to feed it through in pieces (for example, RAG ingestion or a fan-out summarize pattern). Overlap is useful so a…

No input schema was published for this tool.

3 of 3 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

MCP server for token-budget-aware text truncation. Helps an LLM fit text into a context window mid-task.

Keywords
mcpllmtokenstruncationpromptcontext-window
Alternatives
Comparing tool surfaces…

Dependency tree

What one Forge scan resolved from npm metadata on 2026-08-30 — observed resolution, not a publisher declaration.

60 packages resolved · 1 direct · none carrying advisories Resolution stops at depth 4 and 60 packages.

The crawl stopped at the depth-4 limit. Anything below that level was never resolved.

The crawl stopped at the 60-package limit. The rest of the tree was never resolved.

36 more resolved packages are not drawn here (display cap: 24). Every dependency carrying an advisory is drawn regardless of the cap. Full inventory (CycloneDX SBOM)

Declared but not resolved

53 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.

+41 more not listed. The counts by reason above cover all of them.

Not followed: peerDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.