Model Context Protocol (MCP) server for Apollo.io API integration
Pinpoint dealership sales tools is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Car dealership sales tools from Pinpoint, the sales intelligence platform for car dealerships
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http pinpoint-dealership-sales-tools-mcp https://usepinpoint.ai/api/mcp
# 2 — ask your agent for something these tools do
# check_appointment_ask, check_follow_up_text, call_recording_consent and 15 more
Pinpoint dealership sales tools costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http pinpoint-dealership-sales-tools-mcp https://usepinpoint.ai/api/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
18 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Deterministic check of one dealership appointment ask using six fixed text-pattern rules: day, clock time, holding the time, confirmation question, vehicle mention or readiness phrase, 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 rep
No parameter schema on file.
Checks a dealership follow-up text message against eight practices: identifies the sender and store, refers to what the customer asked about, one question at most, a specific next step, no price or payment or trade value, an easy way out, two segments or fewer, no all-caps urgency. Returns what passed, what failed and why.
No parameter schema on file.
Whether one party or every party must consent before a phone call is recorded in a US state, the statute, a note for dealerships, and the greeting, outbound and text notices a dealership should use. All 50 states and DC. General information, not legal advice.
No parameter schema on file.
What a US state requires when an automated or AI voice assistant answers a dealership'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.
No parameter schema on file.
The follow-up sequence for a dealership sales situation (new internet lead, missed inbound call, unconfirmed appointment, no-show, quote without an appointment, trade question without an appointment, text thread gone quiet, sold 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 seque
No parameter schema on file.
A practice card for a dealership 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 salesperson's goal, what a strong answer sounds like, and the feedback
No parameter schema on file.
What a complete CRM note carries after a dealership sales call or text thread, in five sections, with an example of a strong note and the lead statuses that mislead managers.
No parameter schema on file.
The eighteen-item pass-or-fail scorecard for a dealership sales call, in five groups (open, discovery, the ask, control, close and record), with the scoring rules and the four-minute review method.
No parameter schema on file.
The 40 moments in a dealership 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.
No parameter schema on file.
Plain definitions of 100 terms dealership sales teams use, from appointment set rate and BDC to approved action and human handoff. Returns the matching term, or the closest matches.
No parameter schema on file.
Uses the configured AI assistant to review one dealership appointment ask 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.
No parameter schema on file.
Writes two dealership follow-up texts for a situation you describe: under 300 characters, names the rep and store, one question, a way out, no price or payment or trade value.
No parameter schema on file.
Checks a follow-up text against eight practices and rewrites it to pass them.
No parameter schema on file.
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.
No parameter schema on file.
Scores a dealership sales call transcript, notes or summary against the eighteen-item BDC scorecard: pass, fail or not observable per item with evidence, and a coaching note.
No parameter schema on file.
Rewrites every step of a situation's follow-up cadence for the customer you describe, keeping the days, times and channels.
No parameter schema on file.
Answers a dealership manager's question about recording phone calls in one US state from the state's consent entry. General information, not legal advice.
No parameter schema on file.
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.
No parameter schema on file.
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Pinpoint dealership sales tools or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.0.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Pinpoint dealership sales tools can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.