BuyerAware
REMOTE · API.BUYERAWAREAPP.COM · SCANNED SEP 21
Mechanic-grade used-car listing verdicts: risk score, failure points, repair costs, fair price.
Available components
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
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability76
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 783 tokens (~156/item across 5 items; 5 tools + 0 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 Management90
- Stability observed for 27 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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 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
How do I install the BuyerAware MCP server?
BuyerAware is a hosted endpoint at https://api.buyerawareapp.com/mcp, 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 · api.buyerawareapp.com
claude mcp add --transport http com-buyerawareapp-buyeraware 'https://api.buyerawareapp.com/mcp'
{
"mcpServers": {
"com-buyerawareapp-buyeraware": {
"url": "https://api.buyerawareapp.com/mcp"
}
}
} {
"servers": {
"com-buyerawareapp-buyeraware": {
"type": "http",
"url": "https://api.buyerawareapp.com/mcp"
}
}
} [mcp_servers.com-buyerawareapp-buyeraware] url = "https://api.buyerawareapp.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-buyerawareapp-buyeraware": {
"type": "remote",
"url": "https://api.buyerawareapp.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-buyerawareapp-buyeraware --url 'https://api.buyerawareapp.com/mcp' --transport streamable-http
mcp_servers:
com-buyerawareapp-buyeraware:
url: "https://api.buyerawareapp.com/mcp" {
"McpServers": {
"com-buyerawareapp-buyeraware": {
"Transport": "http",
"Url": "https://api.buyerawareapp.com/mcp"
}
}
} assistant mcp add com-buyerawareapp-buyeraware -t streamable-http -u 'https://api.buyerawareapp.com/mcp'
{
"mcpServers": {
"com-buyerawareapp-buyeraware": {
"type": "http",
"url": "https://api.buyerawareapp.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 20 Sept 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.
- 18 Sept 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.
- 16 Sept 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.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 5 Sept 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.
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 21 Sept 2026 · Probed https://api.buyerawareapp.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=api.buyerawareapp.com | CN=YE2,O=Let's Encrypt,C=US | 25 Aug 2026 | 23 Nov 2026 | ECDSA 256 | ECDSA-SHA384 | 5981f64864b18b273dd07e11d13be0fb50a |
| SANs: api.buyerawareapp.com | ||||||
| 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 api.buyerawareapp.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| buyerawareapp.com. | 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=31536000 |
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.buyerawareapp.com/mcp | Verified | 200 | |
| http (plaintext) | http://api.buyerawareapp.com/mcp | HTTPS enforced | 301 | https://api.buyerawareapp.com/mcp |
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 →
analyze_listing Analyze used-car listing ~251
Start a BuyerAware pre-purchase verdict on ONE used vehicle. Runs a mechanic-grade read: ranked failure points with $ exposure, recalls, seller-claim fact-check, fair price range, adjusted true cost, risk score 1-10, BUY / BUY_WITH_CONDITIONS / WALK_AWAY, a word-for-word negotiation script, and lower-risk 'Tank' alternatives. Supply whichever of listing_url, listing_text or vin you have — at least one is required, and more context sharpens the verdict. Takes ~1-2 minutes: returns a job_id, then poll get_verdict. Costs 1 credit. For 'what should I buy instead' use tank_alternatives, which is free.
| Name | Type | Req | Description |
|---|---|---|---|
| buyer_context | string | – | what the buyer needs it for, budget, and any specific concerns |
| listing_text | string | – | the listing copy pasted as-is, when there is no shareable URL |
| listing_url | string | – | link to the listing — Marketplace, Craigslist, AutoTrader, a dealer page |
| location | string | – | buyer city/state, for pricing and inspection context |
| vin | string | – | 17-character VIN, if the listing shows one |
No output schema declared.
No examples provided.
create_trial_key Create trial API key ~105
Create a BuyerAware API key so this user can run verdicts (3 free). Call this once when no key is configured, then show the user the key and tell them to save it. Do not call it again for someone who already has a key — one trial per email address.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | the user's email address; the key is issued against it, one trial key per address | |
| name | string | – | optional display name for the key record |
No output schema declared.
No examples provided.
get_verdict Get verdict result ~59
Fetch the result of an analyze_listing job. If status is 'queued' or 'running', wait ~15 seconds and call again. Free — polling never costs a credit.
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | string | yes | the job_id returned by analyze_listing |
No output schema declared.
No examples provided.
tank_alternatives Find lower-risk alternatives ~186
FREE, no API key needed, answers instantly. Recommend 2-3 lower-risk used vehicles ('Tanks') from BuyerAware's curated 47-platform database that land near a budget. Use when a buyer asks what to buy instead, or what is reliable for $X. Use analyze_listing instead when they have a specific car in mind.
| Name | Type | Req | Description |
|---|---|---|---|
| budget | number | yes | target purchase price in USD |
| category | string | – | sedan, hatchback, small suv, medium suv, large suv, midsize truck, full-size truck, diesel truck, minivan, wagon, hybrid, phev, ev, luxury |
| limit | number | – | how many to return; default 3 |
| max_risk | number | – | risk ceiling 1-10; default 5 |
| mileage | number | – | mileage to price at; default 100000 |
No output schema declared.
No examples provided.
tank_lookup Look up Tank vehicle ~129
FREE, no API key needed, answers instantly. Look up one platform in BuyerAware's curated database: risk score, verdict, the one known trap, private-party value at a mileage, 5-year operating cost. Covers 47 US-market platforms; anything outside it returns no match, which is itself a signal — follow up with analyze_listing.
| Name | Type | Req | Description |
|---|---|---|---|
| mileage | number | – | mileage to value at; default 100000 |
| query | string | yes | platform name, e.g. '4Runner', 'Camry V6', 'CR-V', 'Tundra 5.7' |
No output schema declared.
No examples provided.
What is the BuyerAware MCP server?
BuyerAware is an MCP server listed in the public MCP registry as com.buyerawareapp/buyeraware. Mechanic-grade used-car listing verdicts: risk score, failure points, repair costs, fair price. This page covers its hosted endpoint (https://api.buyerawareapp.com/mcp).
Is the BuyerAware MCP server safe to use?
BuyerAware scores 86 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 BuyerAware MCP server expose?
BuyerAware exposes 5 tools: create_trial_key, analyze_listing, get_verdict, tank_alternatives, tank_lookup. Their descriptions and schemas cost roughly 730 tokens of context every time the server is loaded.
Does the BuyerAware MCP server require authentication?
No. We connected to BuyerAware without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the BuyerAware MCP server still maintained?
BuyerAware is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.