Skip to content

Pinpoint dealership sales tools MCP server

io.github.benian-technologies/pinpoint-dealership-toolsbenian-technologiesstreamable-httpv1.0.0Scanned

Car dealership sales tools from Pinpoint, the sales intelligence platform for car dealerships

18 tools: 18 change things.

Tools: 0 delete, 0 irreversible, 18 write, 0 read.
  • Reads private data · 0
  • Reads text others write · 8
  • Can send data out · 0
  • 4 findings

Tools listed without sign-in. Remote posture

With Anlyon

18 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Pinpoint dealership sales tools MCP server can do

The Pinpoint dealership sales tools MCP server is published by the GitHub account benian-technologies. It has 18 tools. It can create or change data (18 tools: check_appointment_ask, check_follow_up_text, call_recording_consent, ai_caller_disclosure and 14 more), but cannot delete data. None of its tools only reads.

8 tools bring in text other people can write (review_appointment_ask, write_follow_up_texts, rewrite_follow_up_text and 5 more).

The fixed checks matched 4 findings (annotation-conflict). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 16, 2026, version 1.0.0.

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.

18 tools

Changes things 18Claude Code: ask
  • ai_caller_disclosureWhat a US state requires when an automated or AI voice assistant answers a sales team's missed calls or places an approved outbound call: the AI disclosure rule, the consent rule f…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
    What a US state requires when an automated or AI voice assistant answers a sales team's missed calls or places an approved outbound call: the AI disclosure rule, the consent rule for automated calls, the statute, the federal baseline, and what the assistant should say. All 50 states and DC. General information, not legal advice.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • answer_ai_caller_questionAnswers a question about an automated or AI voice assistant answering missed calls or placing approved outbound calls in one US state, from the federal baseline and the state entry…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.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    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
    Answers a question about an automated or AI voice assistant answering missed calls or placing approved outbound calls in one US state, from the federal baseline and the state entry. General information, not legal advice.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: true
  • answer_recording_questionAnswers a sales manager's question about recording phone calls in one US state from the state's consent entry.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.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    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
    Answers a sales manager's question about recording phone calls in one US state from the state's consent entry. General information, not legal advice.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: true
  • call_scorecardThe eighteen-item pass-or-fail scorecard for a sales call, in five groups (open, discovery, the ask, control, close and record), with the scoring rules and the four-minute review m…1 finding

    Why it is in this group

    • The name "call_scorecard" says "call": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "call_scorecard" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"openWorldHint":false}; The name "call_scorecard" says "call": a word for a change.

      What this check looks for
    Description, as the server wrote it
    The eighteen-item pass-or-fail scorecard for a sales call, in five groups (open, discovery, the ask, control, close and record), with the scoring rules and the four-minute review method.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • check_appointment_askDeterministic check of one appointment ask on a sales call using six fixed text-pattern rules: day, clock time, holding the time, confirmation question, naming what the customer as…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
    Deterministic check of one appointment ask on a sales call using six fixed text-pattern rules: day, clock time, holding the time, confirmation question, naming what the customer asked about or promising it ready, and follow-up. Returns a structured score, per-part flags and fixes, and a fixed template example that reuses a detected day and time or supplies sample values when absent. Runs without an AI model. Use this for repeatable rule-based scoring; use review_appointment_ask for contextual AI feedback and a tailored rewrite.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • check_follow_up_textChecks a sales follow-up text message against eight practices: identifies the sender and company, refers to what the customer asked about, one question at most, a specific next ste…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
    Checks a sales follow-up text message against eight practices: identifies the sender and company, refers to what the customer asked about, one question at most, a specific next step, no price or payment or discount, an easy way out, two segments or fewer, no all-caps urgency. Returns what passed, what failed and why.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • conversation_signalsThe 40 moments in a sale worth acting on, in six groups (buying signals, appointment handling, follow-up gaps, coaching moments, record gaps, agent handoffs).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
    The 40 moments in a sale worth acting on, in six groups (buying signals, appointment handling, follow-up gaps, coaching moments, record gaps, agent handoffs). Without a signal, returns the list; with a signal slug, returns what it sounds like, why it matters, what to do next, how to coach it and how to practice it.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • crm_note_checklistWhat a complete CRM note carries after a sales call or text thread, in five sections, with an example of a strong note and the lead statuses that mislead managers.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
    What a complete CRM note carries after a sales call or text thread, in five sections, with an example of a strong note and the lead statuses that mislead managers.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • dealership_glossaryPlain definitions of the 92 terms in the Pinpoint sales conversation glossary, from appointment set rate to speed to lead and quiet hours.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
    Plain definitions of the 92 terms in the Pinpoint sales conversation glossary, from appointment set rate to speed to lead and quiet hours. Accepts a term's other names too. Returns the matching term, or the closest matches.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • follow_up_cadenceThe follow-up sequence for a sales situation (new web lead, missed inbound call, unconfirmed appointment, no-show, quote without an appointment, pricing question without a meeting,…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
    The follow-up sequence for a sales situation (new web lead, missed inbound call, unconfirmed appointment, no-show, quote without an appointment, pricing question without a meeting, text thread gone quiet, new customer first week): the starting event and each step's timing, channel, purpose, message with the names filled in, and the reply that stops it. Use startLabel to anchor the sequence; a step's whenLabel takes precedence over its retained legacy day value.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • review_appointment_askUses the configured AI assistant to review one appointment ask from a sales call in context.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.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    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
    Uses the configured AI assistant to review one appointment ask from a sales call in context. Returns prose with a verdict, present and missing parts, a tailored rewrite in the rep's voice, and one coaching line. Choose this for phrasing and coaching; use check_appointment_ask for deterministic six-part scoring and a fixed template example. Available only when an assistant provider is configured.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: true
  • rewrite_follow_up_textChecks a follow-up text against eight practices and rewrites it to pass them.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.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    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
    Checks a follow-up text against eight practices and rewrites it to pass them.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: true
  • roleplay_cardA practice card for a sales roleplay: a customer type (twelve, from the price shopper to the callback who went quiet) and an objection (eight, from "I need to think about it" to "j…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
    A practice card for a sales roleplay: a customer type (twelve, from the price shopper to the callback who went quiet) and an objection (eight, from "I need to think about it" to "just email me the numbers"): the customer's opening line, what they want and fear, their tells, the objection as the customer says it, the rep's goal, what a strong answer sounds like, and the feedback checklist.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • score_callScores a sales call transcript, notes or summary against the eighteen-item sales call scorecard: pass, fail or not observable per item with evidence, and a coaching note.Reads text others write1 finding

    Why it is in this group

    • The name "score_call" says "call": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.

    Findings

    • Warn

      The server marks "score_call" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"openWorldHint":true}; The name "score_call" says "call": a word for a change.

      What this check looks for
    Description, as the server wrote it
    Scores a sales call transcript, notes or summary against the eighteen-item sales call scorecard: pass, fail or not observable per item with evidence, and a coaching note.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: true
  • score_crm_noteScores a CRM note written after a sales call or text thread against what a complete note carries, and rewrites it complete with brackets for missing facts.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.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    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
    Scores a CRM note written after a sales call or text thread against what a complete note carries, and rewrites it complete with brackets for missing facts.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: true
  • tailor_follow_up_cadenceRewrites every step of a situation's follow-up cadence for the customer you describe, keeping the days, times and channels.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.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    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
    Rewrites every step of a situation's follow-up cadence for the customer you describe, keeping the days, times and channels.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: true
  • write_follow_up_textsWrites two follow-up texts for a sales situation you describe: under 300 characters, names the rep and company, one question, a way out, no price, payment or discount.Reads text others write1 finding

    Why it is in this group

    • The name "write_follow_up_texts" says "write": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.

    Findings

    • Warn

      The server marks "write_follow_up_texts" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"openWorldHint":true}; The name "write_follow_up_texts" says "write": a word for a change.

      What this check looks for
    Description, as the server wrote it
    Writes two follow-up texts for a sales situation you describe: under 300 characters, names the rep and company, one question, a way out, no price, payment or discount.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: true

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

Tools listed without sign-in

Looked at Nov 20, 2026, 19:02 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
18
Protocol version
2025-06-18
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
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 18 tools that change things (18 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://usepinpoint.ai/api/mcp: tools/list returned 18 tools to an anonymous client, including check_appointment_ask (write), check_follow_up_text (write), call_recording_consent (write), ai_caller_disclosure (write), follow_up_cadence (write) and 13 more

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

4 warn
  • The server marks "call_recording_consent" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"openWorldHint":false}; The name "call_recording_consent" says "call": a word for a change.

    What this check looks for
  • The server marks "call_scorecard" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"openWorldHint":false}; The name "call_scorecard" says "call": a word for a change.

    What this check looks for
  • The server marks "write_follow_up_texts" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"openWorldHint":true}; The name "write_follow_up_texts" says "write": a word for a change.

    What this check looks for
  • The server marks "score_call" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"openWorldHint":true}; The name "score_call" says "call": a word for a change.

    What this check looks for

History

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

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

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

claude mcp add --transport http pinpoint-dealership-tools https://usepinpoint.ai/api/mcp
claude mcp add --transport http pinpoint-dealership-tools https://usepinpoint.ai/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": [],
    "ask": [
      "mcp__pinpoint-dealership-tools__check_appointment_ask",
      "mcp__pinpoint-dealership-tools__check_follow_up_text",
      "mcp__pinpoint-dealership-tools__call_recording_consent",
      "mcp__pinpoint-dealership-tools__ai_caller_disclosure",
      "mcp__pinpoint-dealership-tools__follow_up_cadence",
      "mcp__pinpoint-dealership-tools__roleplay_card",
      "mcp__pinpoint-dealership-tools__crm_note_checklist",
      "mcp__pinpoint-dealership-tools__call_scorecard",
      "mcp__pinpoint-dealership-tools__conversation_signals",
      "mcp__pinpoint-dealership-tools__dealership_glossary",
      "mcp__pinpoint-dealership-tools__review_appointment_ask",
      "mcp__pinpoint-dealership-tools__write_follow_up_texts",
      "mcp__pinpoint-dealership-tools__rewrite_follow_up_text",
      "mcp__pinpoint-dealership-tools__score_crm_note",
      "mcp__pinpoint-dealership-tools__score_call",
      "mcp__pinpoint-dealership-tools__tailor_follow_up_cadence",
      "mcp__pinpoint-dealership-tools__answer_recording_question",
      "mcp__pinpoint-dealership-tools__answer_ai_caller_question"
    ],
    "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 pinpoint-dealership-tools. Review it before you use it.

Capability tags behind 8 rules
  • mcp__pinpoint-dealership-tools__review_appointment_ask untrusted-input
  • mcp__pinpoint-dealership-tools__write_follow_up_texts untrusted-input
  • mcp__pinpoint-dealership-tools__rewrite_follow_up_text untrusted-input
  • mcp__pinpoint-dealership-tools__score_crm_note untrusted-input
  • mcp__pinpoint-dealership-tools__score_call untrusted-input
  • mcp__pinpoint-dealership-tools__tailor_follow_up_cadence untrusted-input
  • mcp__pinpoint-dealership-tools__answer_recording_question untrusted-input
  • mcp__pinpoint-dealership-tools__answer_ai_caller_question 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/io.github.benian-technologies/pinpoint-dealership-tools/verify?hash=30ad13a1d6e4c8f06b024955c99a961308d6bf7fe161cfc67a0778383f27c43e" | jq -e '.changed == false'

Pinned hash 30ad13a1d6e4, from Nov 16, 2026, 22:18 UTC.

Watch

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

https://radar.anlyon.com/servers/io.github.benian-technologies/pinpoint-dealership-tools/changes.xml

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

Badge

Anlyon Radar badge for io.github.benian-technologies/pinpoint-dealership-tools
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.benian-technologies/pinpoint-dealership-tools.svg)](https://radar.anlyon.com/servers/io.github.benian-technologies/pinpoint-dealership-tools)

Source: MCP Registry. Synced Oct 21, 2026, 18:23 UTC.

Pinpoint dealership sales tools MCP server: questions and answers

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

Is the Pinpoint dealership sales tools MCP server safe?

No scan can promise that. What its definitions show: 18 tools, 18 of which can change, send or delete something, and 4 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 Pinpoint dealership sales tools MCP server delete data?

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

Can the Pinpoint dealership sales tools 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 Pinpoint dealership sales tools MCP server have?

18 tools: 18 write. check_appointment_ask, check_follow_up_text, call_recording_consent, ai_caller_disclosure, follow_up_cadence, roleplay_card, crm_note_checklist, call_scorecard and 10 more.

Does the Pinpoint dealership sales tools MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Pinpoint dealership sales tools MCP server send data to outside services?

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

Has the Pinpoint dealership sales tools MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 16, 2026.