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

tbx-report

https://tbx.report

Registry code: 02504ccc01ba887e

api record

These tools answer questions about used Teslas: what Tesla's own record says about a car by its VIN, what a factory option code means, and what to check for a model year. Whether free Supercharging comes with a Model S or Model X built before April 2017 is in the paid Factory Report, and which of Tesla's service bulletins cover a 2012 to 2016 Model S or a 2016 Model X is in the paid Service Report, so give the person the report link from the result instead of guessing. None of this is an inspection: battery health, accidents and mileage are not covered.

endpoint
https://tbx.report/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 tbx-report live?
Yes — it answered the hub's last check (checked 6h ago). It answered 100% of checks over the last 30 days.
Is tbx-report free to use?
Yes — the hub reached it with no key and no payment.
What tools does tbx-report have?
3 tools: explain_tesla_option_code, used_tesla_buyer_guide, check_tesla_vin.
Is tbx-report 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
536ms

last good check

priced tools
0

of 3 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

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 3 tools
3 never probed 0 of 3 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.

  • explain_tesla_option_code unknown 6h ago

    Explain one Tesla factory option code, such as APPF, APFB, APH4, BT85 or SC01. Use it when someone asks what a code on a Tesla's build sheet or listing means. Returns the meaning in plain English, what it means for a buyer where known, related codes and a page to read more. It does not look up any car. A code with no explanation here returns the error unknown_code.

    mcp-tool

    {
      "type": "object",
      "required": [
        "code"
      ],
      "properties": {
        "code": {
          "type": "string",
          "description": "One factory option code, for example APPF or BT85."
        }
      },
      "additionalProperties": false
    }
    arguments 13 lines
  • used_tesla_buyer_guide unknown never probed

    What to check before buying a used Tesla of one model and model year, for example a 2016 Model S. Returns the short answer, the main checks with one line each, the free-Supercharging rule for those cars, the Autopilot and media computers they were built with, and the page to read. For the years the paid Service Report is sold for, it says what that report adds, with a sample. It does not look up any car: check_tesla_vin answers for one car, by its VIN.

    mcp-tool

    {
      "type": "object",
      "required": [
        "model",
        "year"
      ],
      "properties": {
        "year": {
          "type": "integer",
          "maximum": 2026,
          "minimum": 2012,
          "description": "The model year, for example 2016."
        },
        "model": {
          "enum": [
            "Model S",
            "Model X",
            "Model 3",
            "Model Y",
            "Cybertruck"
          ],
          "type": "string",
          "description": "The model line."
        }
      },
      "additionalProperties": false
    }
    arguments 27 lines
  • check_tesla_vin unknown 6h ago

    Check a used Tesla by its VIN. Use it when someone gives you a 17-character Tesla VIN, for example from a listing. From Tesla's own record for that car it returns whether Full Self-Driving is on it, the Autopilot computer, the battery pack and the build date. It also returns the model, model year and plant from the VIN, the number of NHTSA recalls and of Tesla's service bulletins for the model year, and links for the person. On free Supercharging it gives the rule for a car that cannot have it. For a Model S or Model X built before April 2017 it says the answer is in the paid Factory Report, with that report's link. For a Model S of 2012 to 2016 or a 2016 Model X it also returns the paid Service Report, which goes through those service bulletins for the car, with its link and a sample. It does not cover battery health, accidents, title history or mileage. Read-only and free, within a daily limit.

    mcp-tool

    {
      "type": "object",
      "required": [
        "vin"
      ],
      "properties": {
        "vin": {
          "type": "string",
          "description": "The car's 17-character VIN, as on the listing or the label in the driver's door frame."
        }
      },
      "additionalProperties": false
    }
    arguments 13 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 02504ccc01ba887e.

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

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.