_ registry / mcp + a2a http-sse · checked 43m ago

harvey-budget

https://budget.rugslayer.com

Registry code: dd77ca55a59fb91d

api record

x402-paid MCP server for agent spending management with budget tracking, ROI analysis, and spend approval. 6 tools, $0.001–0.005 USDC on Solana. ([GitHub](https://github.com/meltingpixelsai/harvey-budget)) | ([npm](https://www.npmjs.com/package/@meltingpixels/harvey-budget))

from a public catalogue that lists it, not from the operator

endpoint
https://budget.rugslayer.com/mcp
door code
e8f45186b449bd06
protocol
http-sse ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is harvey-budget live?
Yes — it answered the hub's last check (checked 43m ago). It answered 100% of checks over the last 30 days.
Is harvey-budget free to use?
Yes — the hub reached it with no key and no payment.
What tools does harvey-budget have?
6 tools: get_spending_report, check_spend, register_agent, report_spend, health, list_tools.
Is harvey-budget safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 99.8%· all time 100%

latency
885ms

last good check

priced tools
0

of 6 tools

_ answered our checks, 90 days 659 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
used for
  • check a planned spend against an agent budget
  • record an agent spend
  • get an agent spending report
  • register an agent with budget limits
takes → gives
data → data
tools
4 reads2 changes data
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 6 tools
2 open 4 never probed 2 of 6 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • health reads open 5h ago

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

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {},
      "additionalProperties": false
    }
    arguments 6 lines
  • list_tools reads open 8h ago

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

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {},
      "additionalProperties": false
    }
    arguments 6 lines
  • get_spending_report reads unknown 8h ago

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

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "agent_id",
        "period"
      ],
      "properties": {
        "period": {
          "enum": [
            "day",
            "week",
            "month"
          ],
          "type": "string",
          "description": "Report period"
        },
        "agent_id": {
          "type": "string",
          "description": "Your agent's name. It belongs to the wallet you pay from: only calls paid from that wallet can read or change it"
        }
      },
      "additionalProperties": false
    }
    arguments 24 lines
  • check_spend reads unknown 8h ago

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "agent_id",
        "service_id",
        "amount_usd",
        "category"
      ],
      "properties": {
        "agent_id": {
          "type": "string",
          "description": "Your agent's name. It belongs to the wallet you pay from: only calls paid from that wallet can read or change it (register it first)"
        },
        "category": {
          "enum": [
            "security",
            "trading",
            "social",
            "content",
            "data",
            "infrastructure",
            "other"
          ],
          "type": "string",
          "description": "Spending category"
        },
        "amount_usd": {
          "type": "number",
          "minimum": 0,
          "description": "Amount you're about to spend in USD"
        },
        "service_id": {
          "type": "string",
          "description": "Service you want to pay for (e.g. 'harvey-tools/scrape_url')"
        }
      },
      "additionalProperties": false
    }
    arguments 39 lines
  • register_agent changes data unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "agent_id",
        "daily_limit_usd",
        "weekly_limit_usd"
      ],
      "properties": {
        "agent_id": {
          "type": "string",
          "description": "Your agent's name. It belongs to the wallet you pay from: only calls paid from that wallet can read or change it"
        },
        "category_limits": {
          "type": "object",
          "description": "Optional per-category weekly limits (e.g. {security: 1.0, content: 2.0})",
          "additionalProperties": {
            "type": "number"
          }
        },
        "daily_limit_usd": {
          "type": "number",
          "maximum": 10000,
          "minimum": 0.001,
          "description": "Maximum daily spending in USD"
        },
        "weekly_limit_usd": {
          "type": "number",
          "maximum": 100000,
          "minimum": 0.001,
          "description": "Maximum weekly spending in USD"
        }
      },
      "additionalProperties": false
    }
    arguments 35 lines
  • report_spend changes data unknown never probed

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

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "agent_id",
        "service_id",
        "amount_usd",
        "category"
      ],
      "properties": {
        "agent_id": {
          "type": "string",
          "description": "Your agent's name. It belongs to the wallet you pay from: only calls paid from that wallet can read or change it"
        },
        "category": {
          "enum": [
            "security",
            "trading",
            "social",
            "content",
            "data",
            "infrastructure",
            "other"
          ],
          "type": "string",
          "description": "Spending category"
        },
        "amount_usd": {
          "type": "number",
          "minimum": 0,
          "description": "Amount spent in USD"
        },
        "service_id": {
          "type": "string",
          "description": "Service that was used"
        },
        "value_received": {
          "type": "string",
          "description": "Description of value received"
        },
        "outcome_success": {
          "type": "boolean",
          "description": "Whether the service call succeeded"
        }
      },
      "additionalProperties": false
    }
    arguments 47 lines
_ try it over mcp through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id dd77ca55a59fb91d.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/dd77ca55a59fb91d/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/dd77ca55a59fb91d/badge.svg)](https://brick.blue/agent/dd77ca55a59fb91d?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we knowoff the mcp door
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.

_ also on rugslayer.com 4 entries

Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.