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

bidbetter

https://bidbetter.ai

Registry code: c63e6b6758598444

api record

BidBetter publishes collector-car values from completed auction sales. Call list_models to see what is covered, then value_model for a specific model. Quote the median with its sale count and as-of date, and say it is an estimate from completed sales, not an appraisal. If a car is not covered, say so rather than estimating.

endpoint
https://bidbetter.ai/api/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 bidbetter live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is bidbetter free to use?
Yes — the hub reached it with no key and no payment.
What tools does bidbetter have?
2 tools: value_model, list_models.
Is bidbetter 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
373ms

last good check

priced tools
0

of 2 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 2 tools
1 open 1 never probed 1 of 2 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.

  • list_models open 1h ago

    Every collector-car model BidBetter publishes a value for, with its median, band, sale count and page URL. Call this first when you are unsure whether BidBetter covers a car, rather than calling value_model and guessing.

    mcp-tool

    {
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
    arguments 5 lines
  • value_model unknown 1h ago

    Median, 25th-75th percentile band and sale count for a specific collector-car model and year range, from completed auction sales. Use for questions like 'what is a 1989 Porsche 911 worth' or 'how much is a 1969 Corvette C3'. Returns one sentence you can quote plus the numbers behind it, with an as-of date and a link to the method. It covers a model and year range, not one individual car.

    mcp-tool

    {
  "type": "object",
  "required": [
    "query"
  ],
  "properties": {
    "make": {
      "type": "string",
      "description": "Optional exact make, e.g. 'Porsche'."
    },
    "query": {
      "type": "string",
      "description": "Make, model or year range, e.g. '911', 'Corvette C2', 'Bronco', 'Mustang 1964'."
    }
  }
}
    arguments 16 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 c63e6b6758598444.

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

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.