Budgetary: estimate token spend
NPM · @BUDGETARY/MCP · SCANNED SEP 20
Pre-flight token-spend estimate (range, scenario, confidence) for a coding task, or an abstention.
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 → Why this is hard to score →
Supply Chain Security100
- 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
- 0 of 1 dependencies flagged as unhealthy. View diagnostics → Pass
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 41 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability80
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 199 tokens (~199/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 Management93
- Stability observed for 28 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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 1 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
How do I install the Budgetary: estimate token spend MCP server?
Budgetary: estimate token spend runs locally as an npm package, launched with npx -y @budgetary/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 · @budgetary/mcp
claude mcp add thriftell-budgetary -- npx -y @budgetary/mcp
{
"mcpServers": {
"thriftell-budgetary": {
"command": "npx",
"args": [
"-y",
"@budgetary/mcp"
]
}
}
} {
"servers": {
"thriftell-budgetary": {
"command": "npx",
"args": [
"-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": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@budgetary/mcp"
]
}
}
} assistant mcp add thriftell-budgetary -t stdio -c npx -a -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.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 −3
- Stability: pass → 0.83 functional
- Package version: 0.1.1 → 0.13.0 functional
- 16 Sept 26 +1
- Stability: 0.97 → pass security
- 15 Sept 26 0
- Package version: 0.1.1 → 0.13.0 functional
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 0
- Security disclosure: unverified → fail ▼ functional
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 20 Sept 2026 · Analysed npm/@budgetary/mcp@0.13.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| 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 | 2399230075 |
| Predicate type | https://slsa.dev/provenance/v1 |
| Subject digest | sha512:b53b60bf023d6cebf52dfb55b06b0fb3efd49cbd90352e822f3eabcb320775bd685671748e3325e1cf3fecfdd8c4731abcdc5a00601b1ec3d3ef6f0a5 |
Background: How many MCP packages publish verified provenance →
Dependencies 1 package
| Packages resolved | 1 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
estimate Budgetary: estimate token spend ~199
Return a pre-flight, probabilistic token-spend estimate for a coding task before you run it, and store it so the same run's realized spend can be measured afterward — the forecast is a probability; the measurement is a count. Call this with the user's task described in natural language, before the work starts. Returns a token range (p10–p90), a scenario label, and a confidence score — or no range at all when there is no firm basis to forecast this particular task, which is an honest answer, not an error. This tool only estimates and records — it does not observe the current run's usage; when an earlier run's counts have been recorded, it reports that run's measured breakdown.
| 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.
What is the Budgetary: estimate token spend MCP server?
Budgetary: estimate token spend is an MCP server listed in the public MCP registry as io.github.thriftell/budgetary. Pre-flight token-spend estimate (range, scenario, confidence) for a coding task, or an abstention. This page covers its npm package (@budgetary/mcp).
Is the Budgetary: estimate token spend MCP server safe to use?
Budgetary: estimate token spend scores 95 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Budgetary: estimate token spend MCP server expose?
Budgetary: estimate token spend exposes 1 tool: estimate. Their descriptions and schemas cost roughly 199 tokens of context every time the server is loaded.
Is the Budgetary: estimate token spend MCP server still maintained?
Budgetary: estimate token spend is still listed as active in the MCP registry. We last reached this channel on 20 September 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 Budgetary: estimate token spend MCP server under?
Budgetary: estimate token spend declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.