Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

TradeBasis US Market Appraisal

REMOTE · TRADEBASIS.NET

Free US vehicle averages in USD from matched asking prices. VIN optional; limited public pilot.

Available components

+4 this week 78 Trust /100

Last scanned (4 hours ago)

Scores higher than 76% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Finance and Payments

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security80
Transport & Reachability100
Schema Quality & AI Usability30
  • 0% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Fail
  • AI-judged instruction clarity (fair).Partial
  • Context-footprint check failed: tool/resource definitions use about 495 tokens (~247/item across 2 items; 1 tools + 1 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management87
  • Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
  • Supports UI / widget rendering.Pass
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 5 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 3 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.

  • 1 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.

  • 30 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

  • 28 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

  • 26 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

  • 24 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

  • 21 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Probed https://tradebasis.net/mcp/appraisal

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=tradebasis.net CN=YE2,O=Let's Encrypt,C=US 6 Sept 2026 5 Dec 2026 ECDSA 256 ECDSA-SHA384 50150cd8e417be8675513b55d935621921a
SANs: tradebasis.net
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of tradebasis.net. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
net. present 37331 13 Verified
tradebasis.net. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=63072000; includeSubDomains

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://tradebasis.net/mcp/appraisal Verified 200
http (plaintext) http://tradebasis.net/mcp/appraisal HTTPS enforced 301 https://tradebasis.net:443/mcp/appraisal
MCP tools · 1 exposed · ~488 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
appraise_vehicle ~488

A derived TradeBasis asking-price market average. Supply odometerMiles plus either vin or all of year, make, model and trim. Ask the user for missing details; never invent vehicle identity or mileage. VIN-assisted decoding may still require a confirmed trim, fuelType or bodyStyle. If supplied identity conflicts with the VIN, ask the user to verify the VIN and conflicting fields; do not choose silently or retry unchanged. Omit market for nationwide US. Not a trade-in offer or completed-sale value.

NameTypeReqDescription
bodyStylestring–Optional confirmed body style: sedan, hatchback, coupe, convertible, SUV, pickup, wagon, minivan or van. Required later if identity is ambiguous; ask the user and do not contradict the VIN.
fuelTypestring–Optional confirmed powertrain/fuel type. Required later if identity is ambiguous. Ask the user rather than selecting a default; must agree with a reported VIN powertrain.
makestring–Confirmed vehicle manufacturer. Required without vin; optional with vin, but must agree with the decoded make.
marketstring–Optional US state name or two-letter state code, not the user's precise location. Omit for nationwide US.
modelstring–Confirmed US model name. Required without vin; optional with vin, but must agree with the decoded model.
odometerMilesnumberyesCurrent odometer reading in miles, required for BOTH input paths. Ask the user; never estimate mileage from the VIN or model year. Zero is valid only when actually reported.
trimstring–Confirmed exact trim, including meaningful +, hyphens and powertrain qualifiers. Required without vin. With vin, supply it if decoding does not identify one unambiguous trim; never assume Base or cho…
vinstring–VIN-assisted input: provide the vehicle's 17-character VIN with odometerMiles. Optional for complete manual input. Decoding may leave trim, fuelType or bodyStyle unresolved; ask the user to confirm t…
yearinteger–Confirmed model year. Required without vin; optional with vin, but must agree with the decoded year. Ask the user if unknown.
NameTypeReqDescription
actualMarketstring–Geography reported for the selected evidence; unknown listing states are explicitly identified.
automaticRetryAllowedbooleanyesRecoverability never authorizes automatic paid searches.
baseMarketAverageinteger––
calculatedAtstringyes–
clarificationFieldsarray––
currencystringyes–
evidenceCountintegeryes–
excludedCountintegeryes–
marketScopestringyes–
messagestringyes–
methodologystringyes–
mileageAdjustedMarketAverageinteger––
mileageAdjustmentinteger––
mileageAdjustmentAvailablebooleanyes–
mileageAdjustmentUnavailableReasonstring––
nextActionobjectyes–
odometerUnitstringyes–
outcomestringyes–
referralIdstring––
requestedMarketstringyes–
retryAtstring––
retryablebooleanyes–
schemaVersionstringyes–
searchMarketstring–Broadest provider search scope; not a claim about every selected listing.
subjectobject––
yearBracketUsedbooleanyes–

No examples provided.

Install

How do I install the TradeBasis US Market Appraisal MCP server?

TradeBasis US Market Appraisal is a hosted endpoint at https://tradebasis.net/mcp/appraisal, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · tradebasis.net

# add to Claude Code
claude mcp add --transport http net-tradebasis-market-appraisal 'https://tradebasis.net/mcp/appraisal'
Common questions

What is the TradeBasis US Market Appraisal MCP server?

TradeBasis US Market Appraisal is an MCP server listed in the public MCP registry as net.tradebasis/market-appraisal. Free US vehicle averages in USD from matched asking prices. VIN optional; limited public pilot. This page covers its hosted endpoint (https://tradebasis.net/mcp/appraisal).

Is the TradeBasis US Market Appraisal MCP server safe to use?

TradeBasis US Market Appraisal scores 78 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the TradeBasis US Market Appraisal MCP server expose?

TradeBasis US Market Appraisal exposes 1 tool: appraise_vehicle. Their descriptions and schemas cost roughly 488 tokens of context every time the server is loaded.

Does the TradeBasis US Market Appraisal MCP server require authentication?

No. We connected to TradeBasis US Market Appraisal without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the TradeBasis US Market Appraisal MCP server still maintained?

TradeBasis US Market Appraisal is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.