zero-core-budget
Server Details
Agent spending mgmt, budget tracking, ROI. Zero Core Budget.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- meltingpixelsai/harvey-budget
- GitHub Stars
- 0
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Average 4.1/5 across 6 of 6 tools scored.
Each tool serves a distinct purpose: pre-spend approval, post-spend recording, analytics, server health, tool discovery, and agent registration. No overlaps.
Most tools follow a consistent verb_noun snake_case pattern (check_spend, get_spending_report, report_spend, register_agent). 'health' deviates slightly but is a common single-word command. Minor inconsistency.
Six tools cover the core workflow of budget management (register, check, report, analyze) plus utilities (health, list_tools). Well-scoped for the domain.
Covers the essential lifecycle: agent setup, pre-spend validation, spend recording, and analytics. Missing explicit category limit management, but registration supports upsert, partially addressing updates.
Available Tools
6 toolscheck_spendInspect
Pre-spend budget approval check. Verifies daily/weekly/category limits, estimates ROI from historical data, and suggests cheaper alternatives. Call this BEFORE paying for any service.
| Name | Required | Description | Default |
|---|---|---|---|
| agent_id | Yes | Your agent identifier (must be registered first) | |
| category | Yes | Spending category | |
| amount_usd | Yes | Amount you're about to spend in USD | |
| service_id | Yes | Service you want to pay for (e.g. 'harvey-tools/scrape_url') |
get_spending_reportInspect
Detailed spending analytics report. Returns total spent, category breakdown, top services with ROI, and optimization recommendations. Use to understand spending patterns and find inefficiencies.
| Name | Required | Description | Default |
|---|---|---|---|
| period | Yes | Report period | |
| agent_id | Yes | Your agent identifier |
healthInspect
Check Harvey Budget server status, uptime, and payment network configuration.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
list_toolsInspect
List all available Harvey Budget tools with pricing and input requirements. Use this for discovery.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
register_agentInspect
Register an agent with daily and weekly budget limits. Free tool - call this before using check_spend or report_spend. Upserts if agent already exists.
| Name | Required | Description | Default |
|---|---|---|---|
| agent_id | Yes | Unique agent identifier (e.g. your wallet address or agent name) | |
| category_limits | No | Optional per-category weekly limits (e.g. {security: 1.0, content: 2.0}) | |
| daily_limit_usd | Yes | Maximum daily spending in USD | |
| weekly_limit_usd | Yes | Maximum weekly spending in USD |
report_spendInspect
Record a completed spend with optional outcome tracking. Call this AFTER paying for a service to track spending and build ROI history.
| Name | Required | Description | Default |
|---|---|---|---|
| agent_id | Yes | Your agent identifier | |
| category | Yes | Spending category | |
| amount_usd | Yes | Amount spent in USD | |
| service_id | Yes | Service that was used | |
| value_received | No | Description of value received | |
| outcome_success | No | Whether the service call succeeded |
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!