Skip to content

DealScore MCP server

com.cardealscore/dealscorecardealscore.comstreamable-httpv0.1.1Scanned

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

4 tools: 3 change things and 1 only read.

Tools: 0 delete, 0 irreversible, 3 write, 1 read.
  • Reads private data · 0
  • Reads text others write · 2
  • Can send data out · 0
  • No findings

Sign-in required, no OAuth metadata. Remote posture

Anlyon alternative

3 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

What the DealScore MCP server can do

The DealScore MCP server is published by cardealscore.com, a domain the MCP Registry verified. It has 4 tools. It can create or change data (3 tools: score_deal, health and check_quote), but cannot delete data. 1 tool only reads.

2 tools bring in text other people can write (score_deal and check_quote).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its tools changed 2 times since Anlyon Radar first saw them.

Last scanned Nov 12, 2026, version 0.1.1.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

4 tools

Changes things 3Claude Code: ask
  • check_quoteCheck a car dealer's quote.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • openWorldHint: true
    • destructiveHint: false
  • healthService health, coverage, cache policy, and limitations.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Service health, coverage, cache policy, and limitations. Same as GET /api/health.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
    • destructiveHint: false
  • score_dealGrade a car deal: compare asking price to expected market value.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Grade a car deal: compare asking price to expected market value. ZIP is optional. Same inputs/outputs as POST /api/score.

    Annotations the server declares

    • readOnlyHint: false
    • openWorldHint: true
    • destructiveHint: false
Only reads 1Show 1 read-only tool
  • explain_gradeExplain the score_v2 rubric grade for a delta_pct.No findings

    Why it is in this group

    • The name "explain_grade" says "explain": a word for reading.
    Description, as the server wrote it
    Explain the score_v2 rubric grade for a delta_pct. Same as POST /api/explain.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
    • destructiveHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write2
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Sign-in required, no OAuth metadata

Looked at Nov 20, 2026, 18:35 UTC, unchanged since Nov 20, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
410
tools/list served without credentials
no
Tools that change things, listed without credentials
0
Protocol version
not observed
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed

The probe stopped: initialize answered HTTP 410.

Posture changes

  1. Nov 20, 2026
    • HTTP status of an anonymous initialize: 200 to 410
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 3 to 0
    • Protocol version: 2025-06-18 to none
    • RFC 9728 protected resource metadata: https://cardealscore.com/.well-known/oauth-protected-resource/api/mcp to none
    • Authorization servers: https://cardealscore.com to none
    • Dynamic client registration: yes to not observed
    • Client ID metadata documents: yes to not observed
  2. Nov 6, 2026
    • Tools that change things, listed without credentials: 2 to 3

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. HTTP status of an anonymous initialize: 200 -> 410; tools/list served without credentials: yes -> no; Tools that change things, listed without credentials: 3 -> 0 (and 5 more).View diff
    • HTTP status of an anonymous initialize: 200 to 410
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 3 to 0
    • Protocol version: 2025-06-18 to none
    • RFC 9728 protected resource metadata: https://cardealscore.com/.well-known/oauth-protected-resource/api/mcp to none
    • Authorization servers: https://cardealscore.com to none
    • Dynamic client registration: yes to not observed
    • Client ID metadata documents: yes to not observed
  2. Tools1 added.+1 addedView diff
  3. PostureRemote posture changed. Tools that change things, listed without credentials: 2 -> 3.View diff
    • Tools that change things, listed without credentials: 2 to 3
  4. Tools1 changed.~1 changedView diff

Install

Pinned to version 0.1.1. Values in angle brackets are yours to fill in.

claude mcp add --transport http dealscore https://cardealscore.com/api/mcp
claude mcp add --transport http dealscore https://cardealscore.com/api/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__dealscore__explain_grade"
    ],
    "ask": [
      "mcp__dealscore__score_deal",
      "mcp__dealscore__health",
      "mcp__dealscore__check_quote"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as dealscore. Review it before you use it.

Capability tags behind 2 rules
  • mcp__dealscore__score_deal untrusted-input
  • mcp__dealscore__check_quote untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/com.cardealscore/dealscore/verify?hash=5697869ece6d3d7b539449958f92799754c7bec21a8585eae2fe1e18604e56f8" | jq -e '.changed == false'

Pinned hash 5697869ece6d, from Nov 12, 2026, 20:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.cardealscore/dealscore/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.cardealscore/dealscore
[![Anlyon Radar](https://radar.anlyon.com/badge/com.cardealscore/dealscore.svg)](https://radar.anlyon.com/servers/com.cardealscore/dealscore)

Source: MCP Registry. Synced Nov 13, 2026, 19:17 UTC.

DealScore MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the DealScore MCP server safe?

No scan can promise that. What its definitions show: 4 tools, 3 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the DealScore MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the DealScore MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the DealScore MCP server have?

4 tools: 3 write, 1 read. score_deal, health, check_quote and explain_grade.

Does the DealScore MCP server need sign-in or OAuth?

Its remote endpoint did not answer the last anonymous look.

Does the DealScore MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the DealScore MCP server changed its tools?

Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 12, 2026. Every change is on this page and in its Atom feed.