Budgetary: estimate token spend
NPM · @BUDGETARY/MCP · 2 COMPONENTS · SCANNED AUG 3
Pre-flight, probabilistic token-spend estimate (range, scenario, confidence) for a coding task.
Available components
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 →
Supply Chain Security87
- No malware found by supply-chain analysis.Pass
- Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to thriftell/budgetary-clients). View diagnostics → Pass
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 11 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability71
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 135 tokens (~135/item across 1 items; 1 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · @budgetary/mcp
claude mcp add thriftell-budgetary -- npx -y @budgetary/mcp
codex mcp add thriftell-budgetary -- npx -y @budgetary/mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"thriftell-budgetary": {
"type": "local",
"command": [
"npx",
"-y",
"@budgetary/mcp"
],
"enabled": true
}
}
} openclaw mcp add thriftell-budgetary --command npx --arg -y --arg @budgetary/mcp
mcp_servers:
thriftell-budgetary:
command: "npx"
args: ["-y", "@budgetary/mcp"] {
"mcpServers": {
"thriftell-budgetary": {
"command": "npx",
"args": [
"-y",
"@budgetary/mcp"
]
}
}
} 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 Aug 26 +57
- Install scripts: unverified → pass ▲ security
- Provenance: unverified → pass ▲ security
- Known CVEs: unverified → partial ▲ security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- The attested source repository moved: thriftell/budgetary-clients security
- Security disclosure: unverified → fail ▼ functional
- Dependency health: partial → unverified ▼ functional
- Schema quality: unverified → good ▲ functional
- License: unverified → pass ▲ functional
- Stability: unverified → 0.20 ▲ functional
- Maintenance: unverified → pass ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Licence: Apache-2.0 functional
- 1 Aug 26 −25
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 46
First indexed and scored.
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 3 Aug 2026 · Analysed npm/@budgetary/[email protected]
Provenance verified
Ecosystem: npm · Outcome: verified
Reason: verified
- Source repo:
- thriftell/budgetary-clients
- Certificate issuer:
- https://token.actions.githubusercontent.com
- Certificate SAN:
- https://github.com/thriftell/budgetary-clients/.github/workflows/release.yml@refs/heads/main
- Rekor log index:
- 1798872482
- Predicate type:
- https://slsa.dev/provenance/v1
- Subject digest:
- sha512:2805a546109b00c82d73345032816bc60250d3f36953c60b179522c5325cea0944da14a1b4caafbbfd5175b467b2fd5a1a9f577c748289acc28a588e4
- Discovery method:
- attestation_endpoint
Dependencies 95 packages
95 packages in the resolved dependency tree · 94 deprecated · 29 stale.
The dependency tree was only partially resolved, so these counts may be incomplete.
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.
estimate Budgetary: estimate token spend ~135
Return a pre-flight, probabilistic token-spend estimate for a coding task before you run it, and store it so the realized cost can be recorded afterward. Call this with the user's task described in natural language. Returns a token range (p10–p90), a scenario label, and a confidence score. This tool only estimates and records — it never reports how many tokens a run actually used.
| Name | Type | Req | Description |
|---|---|---|---|
| model | string | — | Optional target model identifier (e.g. claude-opus-4-7). Omit to use the account default. |
| query | string | yes | Natural-language description of the coding task to estimate. |
No output schema declared.
No examples provided.