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

tradebasis

https://tradebasis.net

Registry code: 6223946deb1aa70a

api record

TradeBasis general US connection: VIN decoding, static product information and research. This /mcp connection does not execute appraisals or expose raw comparable listings or customer data. A free, limited US appraisal pilot is available through a separate connection: https://tradebasis.net/mcp/appraisal (general MCP / Claude) or https://tradebasis.net/mcp/appraisal/chatgpt (ChatGPT). Add the separate appraisal connection; refreshing /mcp does not add appraisal functionality. Call tradebasis_about for inputs, asking-price caveats and shared pilot limits. Use tradebasis_research_library to…

endpoint
https://tradebasis.net/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 tradebasis live?
Yes — it answered the hub's last check (checked 43m ago). It answered 100% of checks over the last 30 days.
Is tradebasis free to use?
Yes — the hub reached it with no key and no payment.
What tools does tradebasis have?
4 tools: tradebasis_vin_decode, tradebasis_pricing_and_tiers, tradebasis_about, tradebasis_research_library.
Is tradebasis 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
99.8%

90 days 99.5%· all time 99.5%

latency
250ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 588 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
used for
  • decode a vin
  • read vehicle appraisal research briefs
  • compare appraisal saas tiers
takes → gives
text → data, text
tools
4 reads
_ 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
3 open 1 never probed 3 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.

  • tradebasis_pricing_and_tiers reads open 14h ago

    TradeBasis paid subscription tiers — Lite (1 user, $99/mo USD) vs Pro (up to 10 users, $249/mo USD). Separate from the free MCP appraisal pilot and the $99 one-time consumer report. Static markdown; as_of is the explicit content review date.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {}
    }
    arguments 5 lines
  • tradebasis_about reads open 14h ago

    What TradeBasis is, the problem it solves, what makes it different, and who it's for, plus how to connect to the separate free, limited US appraisal pilot. Static markdown; as_of is the explicit content review date.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {}
    }
    arguments 5 lines
  • tradebasis_research_library reads open 14h ago

    Search published TradeBasis US dealer research, BHPH (buy here pay here) economics and portfolio benchmarks, the experimental BHPH Macro Conditions Index and its methodology, public blog articles, and legacy briefs. No arguments lists the catalog. topic retrieves a document by ID/slug/title; topic + section retrieves a section or continuation part. query searches; optional limit is an integer 1–20 (default 5). These modes cannot be combined. Returns published Markdown tables, dated evidence, sources and qualifications, not new financial analysis. Long documents return an overview and section directory. Publication is rechecked on every retrieval; unverifiable sources return retryable errors, not cached article text. Blog access uses the public internet. Publication/update dates, CMS modification, data coverage and retrieval time are distinct. Structured output uses operation=list/search/get/section/invalid; retrieval includes the requested Markdown and publisher caveats. Unknown dates and coverage remain null. No search cursor is supported; use returned section/part IDs for long content.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "limit": {
          "type": "integer",
          "maximum": 20,
          "minimum": 1,
          "description": "Search results only: integer 1–20, default 5. Requires query."
        },
        "query": {
          "type": "string",
          "maxLength": 500,
          "minLength": 1,
          "description": "Ordinary-language search of published dealer research and blog articles. Cannot be combined with topic or section."
        },
        "topic": {
          "type": "string",
          "maxLength": 256,
          "description": "Stable document ID, legacy slug, or title. Alone retrieves a document; with section retrieves that section. Empty topic retains legacy listing behavior."
        },
        "section": {
          "type": "string",
          "maxLength": 256,
          "minLength": 1,
          "description": "Section or versioned part ID returned by this tool. Requires topic. Oversized sections list all continuation IDs."
        }
      },
      "additionalProperties": false
    }
    arguments 30 lines
  • tradebasis_vin_decode reads unknown 3h ago

    Decode a 17-character VIN into vehicle identity: year, make, model, trim, body style, drivetrain, engine, transmission and fuel type. Hybrid, plug-in hybrid and battery-electric vehicles also return their electrification level and, where stated, battery and charging facts. Identification only — this tool returns no valuation, no comparable listings and no market data.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "vin"
      ],
      "properties": {
        "vin": {
          "type": "string",
          "description": "Required. The vehicle's 17-character VIN. Lowercase and whitespace are normalized; I, O and Q are rejected, never guessed. Ask the user if missing. Identification only, not valuation."
        }
      },
      "additionalProperties": false
    }
    arguments 14 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 6223946deb1aa70a.

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