pinpoint-dealership-tools

endpoint

https://usepinpoint.ai/api/mcp

protocol

streamable-http ·2025-06-18

authentication

none observed

public key

none — nobody has proven they own this listing · is it yours? claim it

karma

0 · newcomer

Is pinpoint-dealership-tools live?

Yes — it answered the hub's last check (checked 25m ago). It answered 99% of checks over the last 30 days.

Is pinpoint-dealership-tools free to use?

Yes — the hub reached it with no key and no payment.

What tools does pinpoint-dealership-tools have?

18 tools: score_crm_note, answer_ai_caller_question, write_follow_up_texts, rewrite_follow_up_text, call_recording_consent, ai_caller_disclosure, review_appointment_ask, roleplay_card, ….

Is pinpoint-dealership-tools safe to connect?

The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

• crm_note_checklist reads open 11h ago

  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.

  mcp-tool

  1234

  {
    "type": "object",
    "properties": {}
  }

  arguments 4 lines copy
• call_scorecard reads open 11h ago

  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.

  mcp-tool

  1234

  {
    "type": "object",
    "properties": {}
  }

  arguments 4 lines copy
• score_crm_note reads unknown 25m ago

  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.

  mcp-tool

  1234567891011

  {
    "type": "object",
    "required": [
      "note"
    ],
    "properties": {
      "note": {
        "type": "string"
      }
    }
  }

  arguments 11 lines copy
• answer_ai_caller_question reads unknown 25m ago

  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.

  mcp-tool

  123456789101112131415

  {
    "type": "object",
    "required": [
      "state",
      "question"
    ],
    "properties": {
      "state": {
        "type": "string"
      },
      "question": {
        "type": "string"
      }
    }
  }

  arguments 15 lines copy
• write_follow_up_texts reads unknown never probed

  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.

  mcp-tool

  123456789101112131415161718192021222324252627

  {
    "type": "object",
    "required": [
      "situation"
    ],
    "properties": {
      "rep": {
        "type": "string"
      },
      "company": {
        "type": "string"
      },
      "product": {
        "type": "string"
      },
      "situation": {
        "type": "string",
        "description": "What happened with the customer"
      },
      "day_and_time": {
        "type": "string"
      },
      "customer_first_name": {
        "type": "string"
      }
    }
  }

  arguments 27 lines copy
• rewrite_follow_up_text reads unknown never probed

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

  mcp-tool

  1234567891011

  {
    "type": "object",
    "required": [
      "text"
    ],
    "properties": {
      "text": {
        "type": "string"
      }
    }
  }

  arguments 11 lines copy
• call_recording_consent reads unknown 19h ago

  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.

  mcp-tool

  1234567891011121314151617181920

  {
    "type": "object",
    "required": [
      "state"
    ],
    "properties": {
      "rep": {
        "type": "string",
        "description": "Rep first name for the outbound notice"
      },
      "state": {
        "type": "string",
        "description": "State name or two-letter abbreviation, for example \"FL\" or \"Florida\""
      },
      "company": {
        "type": "string",
        "description": "Your company name for the notices"
      }
    }
  }

  arguments 20 lines copy
• ai_caller_disclosure reads unknown 6h ago

  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.

  mcp-tool

  12345678910111213141516

  {
    "type": "object",
    "required": [
      "state"
    ],
    "properties": {
      "state": {
        "type": "string",
        "description": "State name or two-letter abbreviation"
      },
      "company": {
        "type": "string",
        "description": "Your company name for the scripts"
      }
    }
  }

  arguments 16 lines copy
• review_appointment_ask reads unknown 11h ago

  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.

  mcp-tool

  1234567891011

  {
    "type": "object",
    "required": [
      "ask"
    ],
    "properties": {
      "ask": {
        "type": "string"
      }
    }
  }

  arguments 11 lines copy
• roleplay_card reads unknown 6h ago

  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.

  mcp-tool

  123456789101112131415161718192021222324252627282930313233343536373839

  {
    "type": "object",
    "required": [
      "customer_type",
      "objection"
    ],
    "properties": {
      "objection": {
        "enum": [
          "need-to-think-about-it",
          "best-price-over-the-phone",
          "cheaper-somewhere-else",
          "not-ready-to-come-in",
          "talk-to-my-spouse",
          "is-switching-worth-it",
          "i-might-not-qualify",
          "just-email-me-the-numbers"
        ],
        "type": "string"
      },
      "customer_type": {
        "enum": [
          "price-shopper",
          "payment-shopper",
          "spouse-or-co-buyer",
          "current-provider-anchor",
          "out-of-market-buyer",
          "renewal-window-buyer",
          "internet-lead-with-quote",
          "existing-customer-upgrading",
          "approval-worried-buyer",
          "specific-product-check",
          "just-looking-caller",
          "quiet-callback"
        ],
        "type": "string"
      }
    }
  }

  arguments 39 lines copy
• check_appointment_ask reads unknown 19h ago

  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.

  mcp-tool

  123456789101112

  {
    "type": "object",
    "required": [
      "text"
    ],
    "properties": {
      "text": {
        "type": "string",
        "description": "What the rep said when offering the appointment"
      }
    }
  }

  arguments 12 lines copy
• follow_up_cadence reads unknown 17h ago

  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.

  mcp-tool

  123456789101112131415161718192021222324252627282930313233343536373839404142

  {
    "type": "object",
    "required": [
      "situation"
    ],
    "properties": {
      "rep": {
        "type": "string",
        "description": "The rep's first name"
      },
      "company": {
        "type": "string",
        "description": "Your company name"
      },
      "product": {
        "type": "string",
        "description": "What the customer asked about, for example \"umbrella policy\""
      },
      "situation": {
        "enum": [
          "new-internet-lead",
          "missed-inbound-call",
          "appointment-unconfirmed",
          "no-show",
          "quote-without-appointment",
          "pricing-question-without-meeting",
          "text-thread-gone-quiet",
          "new-customer-first-week"
        ],
        "type": "string",
        "description": "The situation slug"
      },
      "day_and_time": {
        "type": "string",
        "description": "The day and time on the table, for example \"Saturday at 12:30\""
      },
      "customer_first_name": {
        "type": "string",
        "description": "The customer's first name"
      }
    }
  }

  arguments 42 lines copy
• conversation_signals reads unknown never probed

  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.

  mcp-tool

  123456789

  {
    "type": "object",
    "properties": {
      "signal": {
        "type": "string",
        "description": "A signal slug from the list"
      }
    }
  }

  arguments 9 lines copy
• dealership_glossary reads unknown 17h ago

  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.

  mcp-tool

  123456789101112

  {
    "type": "object",
    "required": [
      "term"
    ],
    "properties": {
      "term": {
        "type": "string",
        "description": "The term, another name for it, or a word in it"
      }
    }
  }

  arguments 12 lines copy
• score_call reads unknown 6h ago

  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.

  mcp-tool

  123456789101112

  {
    "type": "object",
    "required": [
      "transcript"
    ],
    "properties": {
      "transcript": {
        "type": "string",
        "description": "Transcript, notes or a summary of one call, up to 6,000 characters"
      }
    }
  }

  arguments 12 lines copy
• tailor_follow_up_cadence reads unknown 25m ago

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

  mcp-tool

  1234567891011121314151617181920212223242526272829303132333435363738394041

  {
    "type": "object",
    "required": [
      "situation",
      "customer"
    ],
    "properties": {
      "rep": {
        "type": "string"
      },
      "company": {
        "type": "string"
      },
      "product": {
        "type": "string"
      },
      "customer": {
        "type": "string",
        "description": "Who the customer is and what they care about"
      },
      "situation": {
        "enum": [
          "new-internet-lead",
          "missed-inbound-call",
          "appointment-unconfirmed",
          "no-show",
          "quote-without-appointment",
          "pricing-question-without-meeting",
          "text-thread-gone-quiet",
          "new-customer-first-week"
        ],
        "type": "string"
      },
      "day_and_time": {
        "type": "string"
      },
      "customer_first_name": {
        "type": "string"
      }
    }
  }

  arguments 41 lines copy
• answer_recording_question reads unknown 19h ago

  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.

  mcp-tool

  123456789101112131415

  {
    "type": "object",
    "required": [
      "state",
      "question"
    ],
    "properties": {
      "state": {
        "type": "string"
      },
      "question": {
        "type": "string"
      }
    }
  }

  arguments 15 lines copy
• check_follow_up_text reads unknown 17h ago

  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.

  mcp-tool

  123456789101112

  {
    "type": "object",
    "required": [
      "text"
    ],
    "properties": {
      "text": {
        "type": "string",
        "description": "The text message as it would be sent"
      }
    }
  }

  arguments 12 lines copy

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.