_ registry / mcp http-sse · checked 44m ago

Caliper

https://www.calipermoney.com

Registry code: 73305ddaecd53919

api record

Free money calculators from Caliper (calipermoney.com), the AI net worth tracker. Use net_worth_percentile when someone asks how their net worth compares with others their age; net_worth_by_age for typical/median/average net worth or 'top 10%/1%' thresholds by age (Federal Reserve Survey of Consumer Finances). Use retirement_savings_needed for 'how much do I need to retire at X on $Y a year' and retirement_income_from_savings for 'is $Z enough to retire at X / how much can I spend'. Retirement answers come in weak / typical / strong market scenarios — present the range, not just one number.…

endpoint
https://www.calipermoney.com/mcp
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 Caliper live?
Yes — it answered the hub's last check (checked 44m ago). It answered 100% of checks over the last 30 days.
Is Caliper free to use?
Not measured yet.
What tools does Caliper have?
4 tools: net_worth_percentile, net_worth_by_age, retirement_savings_needed, retirement_income_from_savings.
Is Caliper 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
315ms

last good check

priced tools
0

of 4 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 4 tools
4 never probed 0 of 4 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.

  • net_worth_percentile unknown never probed

    Where a net worth ranks among US families whose head is the same age group. Args: age: the person's age (18-110). net_worth: total assets minus total debts, in US dollars (can be negative).

    mcp-tool

    {
      "type": "object",
      "title": "net_worth_percentileArguments",
      "required": [
        "age",
        "net_worth"
      ],
      "properties": {
        "age": {
          "type": "integer",
          "title": "Age"
        },
        "net_worth": {
          "type": "number",
          "title": "Net Worth"
        }
      }
    }
    arguments 18 lines
  • net_worth_by_age unknown never probed

    Median, average and top-percentile net worth for US families by age. Args: age: optional. Give an age for that age group's full breakdown (percentiles, homeowners vs renters); omit it for every age group.

    mcp-tool

    {
      "type": "object",
      "title": "net_worth_by_ageArguments",
      "properties": {
        "age": {
          "anyOf": [
            {
              "type": "integer"
            },
            {
              "type": "null"
            }
          ],
          "title": "Age",
          "default": null
        }
      }
    }
    arguments 18 lines
  • retirement_savings_needed unknown never probed

    How much someone needs saved to retire at an age and spend a yearly amount. Args: retirement_age: age at retirement (40-80). annual_spending: all-in yearly spending in today's dollars (5,000-1,000,000).

    mcp-tool

    {
      "type": "object",
      "title": "retirement_savings_neededArguments",
      "required": [
        "retirement_age",
        "annual_spending"
      ],
      "properties": {
        "retirement_age": {
          "type": "integer",
          "title": "Retirement Age"
        },
        "annual_spending": {
          "type": "number",
          "title": "Annual Spending"
        }
      }
    }
    arguments 18 lines
  • retirement_income_from_savings unknown never probed

    How much a nest egg can sustainably pay out per year from a retirement age to 95. Args: savings: total retirement savings in US dollars (10,000-50,000,000). retirement_age: age at retirement (40-80).

    mcp-tool

    {
      "type": "object",
      "title": "retirement_income_from_savingsArguments",
      "required": [
        "savings",
        "retirement_age"
      ],
      "properties": {
        "savings": {
          "type": "number",
          "title": "Savings"
        },
        "retirement_age": {
          "type": "integer",
          "title": "Retirement Age"
        }
      }
    }
    arguments 18 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 73305ddaecd53919.

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

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.