Zero Core Budget

io.github.meltingpixelsaiPublished by GitHub account meltingpixelsaiv1.0.0Updated Oct 24, 2026

Agent spending mgmt, budget tracking, ROI. Zero Core Budget.

The publisher's own server: core.blue

VerifiedStreamable HTTPWeb executableFinance

Overview

AI-generated overview

A remote or local MCP server for agent spending management, budget tracking, and ROI reporting.

What you can do
The registry describes Zero Core Budget as covering agent spending management, budget tracking, and ROI. No tool list, README, or usage documentation is provided, so the specific tools and their inputs are not documented in the supplied material. It is offered both as a remote streamable HTTP endpoint and as an npm package that can run locally.
When to use it
Consider it when you want an assistant to help track or report on spending, budgets, or return on investment for agent activity. Because no tools or documentation are published, verify what it actually exposes before relying on it.
Requirements
Either a remote streamable HTTP endpoint or a local process; the npm package is named in the manifest. No authentication, environment variables, or headers are declared, and no accounts or API keys are listed.
Before you install
The manifest declares no authentication, no environment variables, and no headers, so any credentials or spending data handling is undocumented. The description mentions spending and budget tracking, which may involve financial data; no details on what is stored or sent to third parties are given. Review the provider before connecting it to real accounts.

Installation

In SourceWeft

  1. Open Zero Core Budget in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.meltingpixelsai%2Fzero-core-budget/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "zero-core-budget": {
      "type": "http",
      "url": "https://budget.rugslayer.com/mcp"
    }
  }
}

README

This repository has no README.

Tools

6

list_tools

List all available Harvey Budget tools with pricing and input requirements. Use this for discovery.

Takes no parameters.

health

Check Harvey Budget server status, uptime, and payment network configuration.

Takes no parameters.

register_agent

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.

Parametersagent_idrequiredcategory_limitsdaily_limit_usdrequiredweekly_limit_usdrequired

check_spend

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.

Parametersagent_idrequiredcategoryrequiredamount_usdrequiredservice_idrequired

report_spend

Record a completed spend with optional outcome tracking. Call this AFTER paying for a service to track spending and build ROI history.

Parametersagent_idrequiredcategoryrequiredamount_usdrequiredservice_idrequiredvalue_receivedoutcome_success

get_spending_report

Detailed spending analytics report. Returns total spent, category breakdown, top services with ROI, and optimization recommendations. Use to understand spending patterns and find inefficiencies.

Parametersperiodrequiredagent_idrequired

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

75% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.

Other Core integrations