mcpbeat

Budgetary: estimate token spend MCP Server

io.github.thriftell/budgetary
answering

Budgetary: estimate token spend is answering right now. Last checked 5 min ago. 86 installs a week from npm. It exposes 1 tools. Last commit 29 Jul 2026.

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

Installs per day peak 816 · avg 56 · -62% w/w
a month agotoday
Uptime history 40 hours of history
40 hours agonow
100.0%
Uptime 24h
91 of 91 checks
1
Tools
read from the server
399 ms
Response time
average over 24h
86
Installs / week
npm and PyPI

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 5 min ago.

run in your terminal
claude mcp add budgetary --transport http https://api.budgetary.tools/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "budgetary": {
      "url": "https://api.budgetary.tools/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.budgetary]
url = "https://api.budgetary.tools/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "budgetary": {
      "url": "https://api.budgetary.tools/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "budgetary": {
      "url": "https://api.budgetary.tools/mcp"
    }
  }
}

Available tools 1

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

estimate
estimate
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.

Endpoints

URLTransportStateLatencyChecked
https://api.budgetary.tools/mcp streamable-http answering 457 ms 5 min ago

Budgetary: estimate token spend — questions

Answers built from our own checks of this server.

What can Budgetary: estimate token spend do?
It exposes 1 tools, read directly from the server on our last check. Among them: estimate. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Budgetary: estimate token spend working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 399 ms. The bar chart above shows every period we have measured.
How do I connect Budgetary: estimate token spend?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Budgetary: estimate token spend need an API key?
No. Budgetary: estimate token spend completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 1 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Budgetary: estimate token spend?
It answers our handshake in 399 ms on average, which is faster than 34% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.
How many people use Budgetary: estimate token spend?
The npm package @budgetary/mcp was installed 86 times in the last week. Week over week that is -62%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.
Is Budgetary: estimate token spend open source?
Yes — it is published under the Apache-2.0 licence, written in TypeScript and 0 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.