# Pinpoint dealership sales tools (remote · usepinpoint.ai)

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

- Trust score: 78/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-07

## Components

- remote · `usepinpoint.ai`: 78/100 (this document), [markdown](https://verifymcp.io/servers/benian-technologies-pinpoint-dealership-tools/api-mcp.md), [page](https://verifymcp.io/servers/benian-technologies-pinpoint-dealership-tools/api-mcp)

## Channel facts

- Endpoint: `https://usepinpoint.ai/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-07.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 77/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 1704 tokens (~94/item across 18 items; 18 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 50/100
  - Stability observed for 15 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 82/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 47% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 18 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 19 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the Pinpoint dealership sales tools MCP server?

Pinpoint dealership sales tools is a hosted endpoint at https://usepinpoint.ai/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.

### Claude

```bash
claude mcp add --transport http benian-technologies-pinpoint-dealership-tools 'https://usepinpoint.ai/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "benian-technologies-pinpoint-dealership-tools": {
      "url": "https://usepinpoint.ai/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "benian-technologies-pinpoint-dealership-tools": {
      "type": "http",
      "url": "https://usepinpoint.ai/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.benian-technologies-pinpoint-dealership-tools]
url = "https://usepinpoint.ai/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "benian-technologies-pinpoint-dealership-tools": {
      "type": "remote",
      "url": "https://usepinpoint.ai/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add benian-technologies-pinpoint-dealership-tools --url 'https://usepinpoint.ai/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  benian-technologies-pinpoint-dealership-tools:
    url: "https://usepinpoint.ai/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "benian-technologies-pinpoint-dealership-tools": {
      "Transport": "http",
      "Url": "https://usepinpoint.ai/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add benian-technologies-pinpoint-dealership-tools -t streamable-http -u 'https://usepinpoint.ai/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "benian-technologies-pinpoint-dealership-tools": {
      "type": "http",
      "url": "https://usepinpoint.ai/api/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-07 (score 78, +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.

### 2026-10-05 (score 77, +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.

### 2026-10-03 (score 76, +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.

### 2026-09-30 (score 75, +1)

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

### 2026-09-29 (score 74, 0)

- [security] Tool “dealership_glossary” rewrote its description, which is the text the model reads

### 2026-09-28 (score 74, +8)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-26 (score 66, 0)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “ai_caller_disclosure” rewrote its description, which is the text the model reads
- [security] Tool “answer_recording_question” rewrote its description, which is the text the model reads
- [security] Tool “call_recording_consent” rewrote its description, which is the text the model reads
- [security] Tool “call_scorecard” rewrote its description, which is the text the model reads
- [security] Tool “check_appointment_ask” rewrote its description, which is the text the model reads
- [security] Tool “check_follow_up_text” rewrote its description, which is the text the model reads
- [security] Tool “conversation_signals” rewrote its description, which is the text the model reads
- [security] Tool “crm_note_checklist” rewrote its description, which is the text the model reads
- [security] Tool “dealership_glossary” rewrote its description, which is the text the model reads
- [security] Tool “follow_up_cadence” rewrote its description, which is the text the model reads
- [security] Tool “review_appointment_ask” rewrote its description, which is the text the model reads
- [security] Tool “roleplay_card” rewrote its description, which is the text the model reads
- [security] Tool “score_call” rewrote its description, which is the text the model reads
- [security] Tool “write_follow_up_texts” rewrote its description, which is the text the model reads
- [cosmetic] “ai_caller_disclosure” added an optional parameter “company”
- [cosmetic] “call_recording_consent” added an optional parameter “company”
- [cosmetic] “follow_up_cadence” added an optional parameter “company”
- [cosmetic] “follow_up_cadence” added an optional parameter “product”
- [cosmetic] “tailor_follow_up_cadence” added an optional parameter “company”
- [cosmetic] “tailor_follow_up_cadence” added an optional parameter “product”
- [cosmetic] “write_follow_up_texts” added an optional parameter “company”
- [cosmetic] “write_follow_up_texts” added an optional parameter “product”
- [cosmetic] “check_appointment_ask” reworded the description of “text”
- [cosmetic] “dealership_glossary” reworded the description of “term”
- [cosmetic] “follow_up_cadence” reworded the description of “rep”
- [cosmetic] “ai_caller_disclosure” dropped the optional parameter “dealership”
- [cosmetic] “call_recording_consent” dropped the optional parameter “dealership”
- [cosmetic] “follow_up_cadence” dropped the optional parameter “dealership”
- [cosmetic] “follow_up_cadence” dropped the optional parameter “vehicle”
- [cosmetic] “tailor_follow_up_cadence” dropped the optional parameter “dealership”
- [cosmetic] “tailor_follow_up_cadence” dropped the optional parameter “vehicle”
- [cosmetic] “write_follow_up_texts” dropped the optional parameter “dealership”
- [cosmetic] “write_follow_up_texts” dropped the optional parameter “vehicle”
- [cosmetic] Tool “call_scorecard” changed its title: BDC call scorecard → Sales call scorecard
- [cosmetic] Tool “dealership_glossary” changed its title: Dealership sales glossary → Sales conversation glossary
- [cosmetic] Tool “score_call” changed its title: Score a call on the BDC scorecard → Score a call on the sales call scorecard

### 2026-09-25 (score 66, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

## MCP tools (18)

### `check_appointment_ask` (~133 tokens)

Check an appointment ask

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.

Input parameters:

- `text` (string, required): What the rep said when offering the appointment

### `check_follow_up_text` (~92 tokens)

Check a follow-up text

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.

Input parameters:

- `text` (string, required): The text message as it would be sent

### `call_recording_consent` (~116 tokens)

Call recording consent by state

Whether one party or every party must consent before a phone call is recorded in a US state, the statute, a note for sales teams, and the greeting, outbound and text notices to use on your calls. All 50 states and DC. General information, not legal advice.

Input parameters:

- `company` (string): Your company name for the notices
- `rep` (string): Rep first name for the outbound notice
- `state` (string, required): State name or two-letter abbreviation, for example "FL" or "Florida"

### `ai_caller_disclosure` (~102 tokens)

AI caller disclosure by state

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.

Input parameters:

- `company` (string): Your company name for the scripts
- `state` (string, required): State name or two-letter abbreviation

### `follow_up_cadence` (~195 tokens)

Follow-up cadence for a situation

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.

Input parameters:

- `company` (string): Your company name
- `customer_first_name` (string): The customer's first name
- `day_and_time` (string): The day and time on the table, for example "Saturday at 12:30"
- `product` (string): What the customer asked about, for example "umbrella policy"
- `rep` (string): The rep's first name
- `situation` (string, required): The situation slug

### `roleplay_card` (~113 tokens)

Sales roleplay card

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.

Input parameters:

- `customer_type` (string, required)
- `objection` (string, required)

### `crm_note_checklist` (~44 tokens)

CRM note checklist

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.

### `call_scorecard` (~51 tokens)

Sales call scorecard

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.

### `conversation_signals` (~96 tokens)

Conversation signals library

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.

Input parameters:

- `signal` (string): A signal slug from the list

### `dealership_glossary` (~76 tokens)

Sales conversation glossary

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.

Input parameters:

- `term` (string, required): The term, another name for it, or a word in it

### `review_appointment_ask` (~94 tokens)

Review an appointment ask

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.

Input parameters:

- `ask` (string, required)

### `write_follow_up_texts` (~99 tokens)

Write two follow-up texts

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.

Input parameters:

- `company` (string)
- `customer_first_name` (string)
- `day_and_time` (string)
- `product` (string)
- `rep` (string)
- `situation` (string, required): What happened with the customer

### `rewrite_follow_up_text` (~33 tokens)

Rewrite a follow-up text

Checks a follow-up text against eight practices and rewrites it to pass them.

Input parameters:

- `text` (string, required)

### `score_crm_note` (~47 tokens)

Score a CRM note

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.

Input parameters:

- `note` (string, required)

### `score_call` (~66 tokens)

Score a call on the sales call scorecard

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.

Input parameters:

- `transcript` (string, required): Transcript, notes or a summary of one call, up to 6,000 characters

### `tailor_follow_up_cadence` (~99 tokens)

Tailor a follow-up cadence to one customer

Rewrites every step of a situation's follow-up cadence for the customer you describe, keeping the days, times and channels.

Input parameters:

- `company` (string)
- `customer` (string, required): Who the customer is and what they care about
- `customer_first_name` (string)
- `day_and_time` (string)
- `product` (string)
- `rep` (string)
- `situation` (string, required)

### `answer_recording_question` (~51 tokens)

Answer a question about recording calls in a state

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.

Input parameters:

- `question` (string, required)
- `state` (string, required)

### `answer_ai_caller_question` (~64 tokens)

Answer a question about an AI assistant on a sales line in a state

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.

Input parameters:

- `question` (string, required)
- `state` (string, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/benian-technologies-pinpoint-dealership-tools/api-mcp#diagnostics

## Score history

- 2026-10-07: 78
- 2026-10-06: 77
- 2026-10-05: 77
- 2026-10-04: 76
- 2026-10-03: 76
- 2026-10-02: 75
- 2026-10-01: 75
- 2026-09-30: 75
- 2026-09-29: 74
- 2026-09-28: 74
- 2026-09-27: 66
- 2026-09-26: 66
- 2026-09-25: 66
- 2026-09-24: 65
- 2026-09-23: 65
- 2026-09-22: 64

## Common questions

### What is the Pinpoint dealership sales tools MCP server?

Pinpoint dealership sales tools is an MCP server listed in the public MCP registry as io.github.benian-technologies/pinpoint-dealership-tools. Car dealership sales tools from Pinpoint, the sales intelligence platform for car dealerships. This page covers its hosted endpoint (https://usepinpoint.ai/api/mcp).

### Is the Pinpoint dealership sales tools MCP server safe to use?

Pinpoint dealership sales tools 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 Pinpoint dealership sales tools MCP server expose?

Pinpoint dealership sales tools exposes 18 tools: check_appointment_ask, check_follow_up_text, call_recording_consent, ai_caller_disclosure, follow_up_cadence, and 13 more. Their descriptions and schemas cost roughly 1,571 tokens of context every time the server is loaded.

### Does the Pinpoint dealership sales tools MCP server require authentication?

No. We connected to Pinpoint dealership sales tools without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Pinpoint dealership sales tools MCP server still maintained?

Pinpoint dealership sales tools is still listed as active in the MCP registry. We last reached this channel on 7 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://usepinpoint.ai/api/mcp
- Website: https://usepinpoint.ai/resources/api/
- Changelog RSS feed: https://verifymcp.io/servers/benian-technologies-pinpoint-dealership-tools/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/benian-technologies-pinpoint-dealership-tools/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/benian-technologies-pinpoint-dealership-tools/api-mcp