Pinpoint dealership sales tools
REMOTE · USEPINPOINT.AI · SCANNED OCT 7
Car dealership sales tools from Pinpoint, the sales intelligence platform for car dealerships
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 Usability77
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 1704 tokens (~94/item across 18 items; 18 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management50
- Stability observed for 15 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage82
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 47% 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 18 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 19 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
remote · usepinpoint.ai
claude mcp add --transport http benian-technologies-pinpoint-dealership-tools 'https://usepinpoint.ai/api/mcp'
{
"mcpServers": {
"benian-technologies-pinpoint-dealership-tools": {
"url": "https://usepinpoint.ai/api/mcp"
}
}
} {
"servers": {
"benian-technologies-pinpoint-dealership-tools": {
"type": "http",
"url": "https://usepinpoint.ai/api/mcp"
}
}
} [mcp_servers.benian-technologies-pinpoint-dealership-tools] url = "https://usepinpoint.ai/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"benian-technologies-pinpoint-dealership-tools": {
"type": "remote",
"url": "https://usepinpoint.ai/api/mcp",
"enabled": true
}
}
} openclaw mcp add benian-technologies-pinpoint-dealership-tools --url 'https://usepinpoint.ai/api/mcp' --transport streamable-http
mcp_servers:
benian-technologies-pinpoint-dealership-tools:
url: "https://usepinpoint.ai/api/mcp" {
"McpServers": {
"benian-technologies-pinpoint-dealership-tools": {
"Transport": "http",
"Url": "https://usepinpoint.ai/api/mcp"
}
}
} assistant mcp add benian-technologies-pinpoint-dealership-tools -t streamable-http -u 'https://usepinpoint.ai/api/mcp'
{
"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.
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.
- 7 Oct 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.
- 5 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.
- 3 Oct 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.
- 30 Sept 26 +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.
- 29 Sept 26 0
- Tool “dealership_glossary” rewrote its description, which is the text the model reads security
- 28 Sept 26 +8
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Sept 26 0
- 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 security
- “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 cosmetic
- 25 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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 7 Oct 2026 · Probed https://usepinpoint.ai/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.usepinpoint.ai | CN=YR1,O=Let's Encrypt,C=US | 17 Sept 2026 | 16 Dec 2026 | RSA 2048 | SHA256-RSA | 65db68fb5215cc5bc35b3a30291f8cac044 |
| SANs: *.usepinpoint.ai, usepinpoint.ai | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| 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 usepinpoint.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| usepinpoint.ai. | 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=63072000 |
| content-security-policy | default-src 'self'; script-src 'self' https://www.googletagmanager.com; style-src 'self' 'unsafe-inline'; img-src 'self' data: https://*.google-analytics.com https://www.googletagmanager.com; font-src 'self'; media-src 'self'; connect-src 'self' https://*.google-analytics.com https://*.analytics.google.com https://www.googletagmanager.com; frame-ancestors 'none'; base-uri 'self'; form-action 'none' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://usepinpoint.ai/api/mcp | Verified | 200 | |
| http (plaintext) | http://usepinpoint.ai/api/mcp | HTTPS enforced | 308 | https://usepinpoint.ai/api/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 →
ai_caller_disclosure AI caller disclosure by state ~102
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.
| Name | Type | Req | Description |
|---|---|---|---|
| company | string | – | Your company name for the scripts |
| state | string | yes | State name or two-letter abbreviation |
No output schema declared.
No examples provided.
answer_ai_caller_question Answer a question about an AI assistant on a sales line in a state ~64
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.
| Name | Type | Req | Description |
|---|---|---|---|
| question | string | yes | – |
| state | string | yes | – |
No output schema declared.
No examples provided.
answer_recording_question Answer a question about recording calls in a state ~51
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.
| Name | Type | Req | Description |
|---|---|---|---|
| question | string | yes | – |
| state | string | yes | – |
No output schema declared.
No examples provided.
call_recording_consent Call recording consent by state ~116
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.
| Name | Type | Req | Description |
|---|---|---|---|
| company | string | – | Your company name for the notices |
| rep | string | – | Rep first name for the outbound notice |
| state | string | yes | State name or two-letter abbreviation, for example "FL" or "Florida" |
No output schema declared.
No examples provided.
call_scorecard Sales call scorecard ~51
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
check_appointment_ask Check an appointment ask ~133
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.
| Name | Type | Req | Description |
|---|---|---|---|
| text | string | yes | What the rep said when offering the appointment |
No output schema declared.
No examples provided.
check_follow_up_text Check a follow-up text ~92
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.
| Name | Type | Req | Description |
|---|---|---|---|
| text | string | yes | The text message as it would be sent |
No output schema declared.
No examples provided.
conversation_signals Conversation signals library ~96
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.
| Name | Type | Req | Description |
|---|---|---|---|
| signal | string | – | A signal slug from the list |
No output schema declared.
No examples provided.
crm_note_checklist CRM note checklist ~44
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
dealership_glossary Sales conversation glossary ~76
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.
| Name | Type | Req | Description |
|---|---|---|---|
| term | string | yes | The term, another name for it, or a word in it |
No output schema declared.
No examples provided.
follow_up_cadence Follow-up cadence for a situation ~195
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | The situation slug |
No output schema declared.
No examples provided.
review_appointment_ask Review an appointment ask ~94
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.
| Name | Type | Req | Description |
|---|---|---|---|
| ask | string | yes | – |
No output schema declared.
No examples provided.
rewrite_follow_up_text Rewrite a follow-up text ~33
Checks a follow-up text against eight practices and rewrites it to pass them.
| Name | Type | Req | Description |
|---|---|---|---|
| text | string | yes | – |
No output schema declared.
No examples provided.
roleplay_card Sales roleplay card ~113
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.
| Name | Type | Req | Description |
|---|---|---|---|
| customer_type | string | yes | – |
| objection | string | yes | – |
No output schema declared.
No examples provided.
score_call Score a call on the sales call scorecard ~66
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.
| Name | Type | Req | Description |
|---|---|---|---|
| transcript | string | yes | Transcript, notes or a summary of one call, up to 6,000 characters |
No output schema declared.
No examples provided.
score_crm_note Score a CRM note ~47
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.
| Name | Type | Req | Description |
|---|---|---|---|
| note | string | yes | – |
No output schema declared.
No examples provided.
tailor_follow_up_cadence Tailor a follow-up cadence to one customer ~99
Rewrites every step of a situation's follow-up cadence for the customer you describe, keeping the days, times and channels.
| Name | Type | Req | Description |
|---|---|---|---|
| company | string | – | – |
| customer | string | yes | Who the customer is and what they care about |
| customer_first_name | string | – | – |
| day_and_time | string | – | – |
| product | string | – | – |
| rep | string | – | – |
| situation | string | yes | – |
No output schema declared.
No examples provided.
write_follow_up_texts Write two follow-up texts ~99
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.
| Name | Type | Req | Description |
|---|---|---|---|
| company | string | – | – |
| customer_first_name | string | – | – |
| day_and_time | string | – | – |
| product | string | – | – |
| rep | string | – | – |
| situation | string | yes | What happened with the customer |
No output schema declared.
No examples provided.
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.