Budgetary: estimate token spend

Pre-flight token-spend estimate (range, scenario, confidence) for a coding task, or an abstention.

Should I use this

Quality & Safety

A
Description quality
100%
Schema completeness
100%
Naming quality
80%
Poisoning risk
100%
Permission match
100%
Protocol compliance
100%

Based on automated analysis of tool definitions and protocol compliance.

Context Cost

~116Tokens (tool definitions)
~786 BTypical response size
Minimal attention impact (0.09% of 128k context)

This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.

Install

One-Click Install

Add this to your `claude_desktop_config.json` file:

{
  "mcpServers": {
    "budgetary": {
      "command": "npx",
      "args": [
        "@budgetary/mcp"
      ]
    }
  }
}

Runnable packages

npm@budgetary/mcp0.13.0stdio

Remote endpoints

https://api.budgetary.tools/mcpstreamable-http

What it can do

Tool inventory

Tools (1)

🟢 Read-only🟡 Write🔴 Delete⚪ Unknown
⚪estimate(query, model)

Return a pre-flight, probabilistic token-spend estimate (range + scenario + confidence) for a coding task before you run it. Estimates only — it never reports your actual token usage.

Input Schema

{
  "type": "object",
  "properties": {
    "query": {
      "type": "string",
      "description": "The coding task or prompt you're about to run."
    },
    "model": {
      "type": "string",
      "description": "Optional model identifier, e.g. claude-opus-4-7."
    }
  },
  "required": [
    "query"
  ],
  "additionalProperties": false
}

Community

Rate this Server

Evidence

Recent observations

verifiedversion not recorded1 tools
verifiedversion not recorded1 tools