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.

DealScore

REMOTE · CARDEALSCORE.COM

For AI agents: grade a used car's asking price vs live market comps.

Available components

+4 this week 89 Trust /100

Last scanned (5 hours ago)

Scores higher than 97% of remote servers

Reachable. Last reached 5 Nov 2026.

Category E-commerce

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 Security97
Transport & Reachability100
Schema Quality & AI Usability64
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 384 tokens (~96/item across 4 items; 4 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
  • Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage75
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 26% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 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
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.

  • 3 Nov 26 +2
    • Schema quality: 67 → 96 ▼ functional
    • Tool coverage: 0% → 26% ▲ functional
    • New tool “check_quote” functional
  • 1 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.

  • 30 Oct 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.

  • 27 Oct 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.

  • 25 Oct 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.

  • 24 Oct 26 0
    • Server version: 0.1.0 → 0.1.1 functional
  • 23 Oct 26 +1
    • Tool “explain_grade” rewrote its description, which is the text the model reads security
  • 21 Oct 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.

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://cardealscore.com/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=cardealscore.com CN=YR2,O=Let's Encrypt,C=US 9 Sept 2026 8 Dec 2026 RSA 2048 SHA256-RSA 62347998f4a0df27668d37fc686c728e53d
SANs: cardealscore.com
CN=YR2,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA 4ebd24947e24d394802d84a52fd5b319
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of cardealscore.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
cardealscore.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Enforced and verified

The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.

Result Enforced and verified
Enforced On tool calls
HTTP status 200

WWW-Authenticate challenge Bearer error="invalid_token", error_description="No authorization provided", scope="mcp", resource_metadata="https://cardealscore.com/.well-known/oauth-protected-resource"

Bearer error="invalid_token", error_description="No authorization provided", scope="mcp", resource_metadata="https://cardealscore.com/.well-known/oauth-protected-resource"
Header Value
strict-transport-security max-age=63072000

Protected resource metadata

Document https://cardealscore.com/.well-known/oauth-protected-resource
Retrieved Yes
Resource https://cardealscore.com/api/mcp
Authorisation server https://cardealscore.com

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://cardealscore.com/api/mcp Verified 200
http (plaintext) http://cardealscore.com/api/mcp HTTPS enforced 308 https://cardealscore.com/api/mcp
MCP tools · 4 exposed · ~337 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
check_quote ~181

Check a car dealer's quote. Returns a grade from A to F, the flagged fees and add-ons, and lines to send the dealer. Pass paste (the quote text), or selling_price and msrp. 3 free checks per UTC month. Same as POST /api/quote-check.

NameTypeReqDescription
invoicenumber–Dealer invoice in dollars.
linesarray–Fees and add-ons in dollars. Set kind when known. Otherwise the label decides.
makestring––
modelstring––
msrpnumber–MSRP in dollars.
pastestring–The dealer quote as text. Used for this check only and never stored.
selling_pricenumber–Selling price in dollars.
trimstring––
vinstring––
yearinteger––

No output schema declared.

No examples provided.

explain_grade ~36

Explain the score_v2 rubric grade for a delta_pct. Same as POST /api/explain.

NameTypeReqDescription
delta_pctnumberyes–

No output schema declared.

No examples provided.

health ~26

Service health, coverage, cache policy, and limitations. Same as GET /api/health.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

score_deal ~94

Grade a car deal: compare asking price to expected market value. ZIP is optional. Same inputs/outputs as POST /api/score.

NameTypeReqDescription
asking_pricenumberyes–
makestring––
mileagenumberyes–
modelstring––
trimstring––
vinstring––
yearinteger––
zipstring––

No output schema declared.

No examples provided.

Install

How do I install the DealScore MCP server?

DealScore is a hosted endpoint at https://cardealscore.com/api/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 · cardealscore.com

# add to Claude Code
claude mcp add --transport http com-cardealscore-dealscore 'https://cardealscore.com/api/mcp'
Common questions

What is the DealScore MCP server?

DealScore is an MCP server listed in the public MCP registry as com.cardealscore/dealscore. For AI agents: grade a used car's asking price vs live market comps. This page covers its hosted endpoint (https://cardealscore.com/api/mcp).

Is the DealScore MCP server safe to use?

DealScore scores 89 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 DealScore MCP server expose?

DealScore exposes 4 tools: score_deal, explain_grade, health, check_quote. Their descriptions and schemas cost roughly 337 tokens of context every time the server is loaded.

Does the DealScore MCP server require authentication?

Yes. DealScore asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

Is the DealScore MCP server still maintained?

DealScore 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.