zero-core-budget
Server Details
Agent spending mgmt, budget tracking, ROI. Zero Core Budget.
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-06-18
- URL
- Repository
- meltingpixelsai/harvey-budget
- GitHub Stars
- 0
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 6 tools
Each tool has a distinct role: pre-spend check, post-spend record, analytics report, registration, plus health and discovery. The trio check_spend / report_spend / get_spending_report share similar names and all concern spending, so a careless agent could momentarily confuse them, but the BEFORE/AFTER phrasing in the descriptions resolves it.
Five of six names follow a clear verb_noun convention (check_spend, get_spending_report, list_tools, register_agent, report_spend). The lone outlier is the bare noun 'health', which is a common convention for status endpoints and stays readable.
Six tools is well-scoped for a budget/approval server: two lifecycle writes, two reads/analytics, and two meta tools. Nothing feels padded or missing at the count level.
Core lifecycle is covered: register/update limits, pre-spend approval, spend recording, and analytics. Gaps remain: no way to read current agent budget/limits, no deregister or delete-agent operation, and no tool to correct or void a mistaken report_spend entry.
Available Tools
6 toolscheck_spendAInspect
Pre-spend budget approval check. Verifies daily/weekly/category limits, estimates ROI from your own past spends with this service, and suggests cheaper alternatives you have used. Call this BEFORE paying for any service.
Inputs: agent_id (required), category (required), amount_usd (required), service_id (required).
get_spending_reportAInspect
Detailed spending analytics report. Returns total spent, category breakdown, top services with ROI, and optimization recommendations. Use to understand spending patterns and find inefficiencies.
Inputs: period (required), agent_id (required).
healthAInspect
Check Harvey Budget server status, uptime, and payment network configuration.
Inputs: no named parameters.
list_toolsAInspect
List all available Harvey Budget tools with pricing and input requirements. Use this for discovery.
Inputs: no named parameters.
register_agentAInspect
Register an agent with daily and weekly budget limits, or update them. The agent_id belongs to the wallet that pays for this call: call check_spend, report_spend and get_spending_report from the same wallet.
Inputs: agent_id (required), daily_limit_usd (required), weekly_limit_usd (required), category_limits.
report_spendAInspect
Record a completed spend with optional outcome tracking. Call this AFTER paying for a service to track spending and build ROI history.
Inputs: agent_id (required), category (required), amount_usd (required), service_id (required), +2 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Agent payments, API key vaulting, and governed mandates. Agents spend within user-defined limits.
Budget & cost control for AI agents — per-agent spend caps + rate limits before each call.
Not a budget. A system. Three buckets — Bills, Lifestyle, Freedom — via hosted MCP for agents.
AI agent cost control: true cost per outcome, budgets, spend limits, anomalies, audit evidence.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceEnables agents to maintain sandboxed spend ledgers, enforce monthly budgets, transfer funds between agents, and generate invoices, all without real financial accounts.1MIT
- AlicenseAqualityCmaintenanceSpending limits for AI agents. Create budgets, enforce limits, track spend across x402, cards, MPP, or any payment rail.76 npmApache 2.0
- AlicenseAqualityDmaintenanceTracks AI agent token usage and spending in real time, with budget alerts, per-task cost breakdown, and a visual dashboard.61MIT
- AlicenseNot gradedqualityCmaintenanceBudget & cost control for AI agents: hard per-agent spend caps, rate limits, idempotency, and human-in-the-loop approval — enforced before each LLM call, not after the invoice. One hosted MCP endpoint (no proxy or self-hosting), settled via x402 (USDC on Base).MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.