_ registry / mcp streamable-http · checked 1h ago

bill-budget-board-mcp

https://thewellhabit.com

Registry code: a07fe4d8a65748bc

api record

Use plan_bills_and_budget when someone wants to organise bills and due dates, check which bills are unpaid or due soon, compare planned with actual spending by category, or work out how much of their planned income is not yet allocated, without linking a bank. Pass the user's own numbers; leave an amount out (null) if they don't know it. The tool does arithmetic on what it is given and gives no financial advice.

endpoint
https://thewellhabit.com/mcp
protocol
streamable-http ·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 bill-budget-board-mcp live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is bill-budget-board-mcp free to use?
Yes — the hub reached it with no key and no payment.
What tools does bill-budget-board-mcp have?
1 tool: plan_bills_and_budget.
Is bill-budget-board-mcp 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 100%· all time 100%

latency
327ms

last good check

priced tools
0

of 1 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ 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 1 tools
1 open 1 of 1 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.

  • plan_bills_and_budget open 1h ago

    Helps with manual bill and budget planning, with no bank connection. Given a month's bills (name, amount, due date, paid or not) and/or planned income and spending categories (planned and actual amounts), it returns a bills checklist sorted by due date with the unpaid total and what is overdue or due in the next 7 days, each category's actual minus planned, and the plan difference (planned income minus planned category spending). A blank amount stays unknown, never zero, and bills are not added to category totals. With only a question, it explains how to set up a simple bills-and-budget board. Read-only: it stores nothing, connects to no bank and pays nothing. Not financial advice.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "as_of": {
          "type": "string",
          "description": "Today's date as YYYY-MM-DD, used for overdue and due-in-7-days. Omit to skip those."
        },
        "bills": {
          "type": "array",
          "items": {
            "type": "object",
            "required": [
              "name"
            ],
            "properties": {
              "name": {
                "type": "string",
                "maxLength": 80
              },
              "paid": {
                "type": "boolean",
                "description": "True if the user has marked it paid. Defaults to false."
              },
              "amount": {
                "type": [
                  "number",
                  "null"
                ],
                "maximum": 999999999.99,
                "minimum": 0,
                "description": "Bill amount, null if unknown."
              },
              "due_date": {
                "type": "string",
                "description": "Due date as YYYY-MM-DD."
              }
            },
            "additionalProperties": false
          },
          "maxItems": 200,
          "description": "Bills to track."
        },
        "currency": {
          "enum": [
            "USD",
            "GBP",
            "EUR"
          ],
          "type": "string",
          "description": "Currency for the figures. Defaults to USD."
        },
        "question": {
          "type": "string",
          "maxLength": 1000,
          "description": "The user's question in plain words, e.g. 'Which bills are still unpaid this month?' or 'How do I set up a budget without linking my bank?'"
        },
        "categories": {
          "type": "array",
          "items": {
            "type": "object",
            "required": [
              "name"
            ],
            "properties": {
              "name": {
                "type": "string",
                "maxLength": 80
              },
              "actual": {
                "type": [
                  "number",
                  "null"
                ],
                "maximum": 999999999.99,
                "minimum": 0,
                "description": "Actual spent so far, null if unknown."
              },
              "planned": {
                "type": [
                  "number",
                  "null"
                ],
                "maximum": 999999999.99,
                "minimum": 0,
                "description": "Planned amount, null if unknown."
              }
            },
            "additionalProperties": false
          },
          "maxItems": 200,
          "description": "Spending categories for the month."
        },
        "planned_income": {
          "type": [
            "number",
            "null"
          ],
          "maximum": 999999999.99,
          "minimum": 0,
          "description": "Planned income for the month. Omit or null if unknown."
        }
      },
      "additionalProperties": false
    }
    arguments 104 lines
_ try it 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 a07fe4d8a65748bc.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/a07fe4d8a65748bc/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/a07fe4d8a65748bc/badge.svg)](https://brick.blue/agent/a07fe4d8a65748bc?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 know
card completeness
50%

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.