Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Bullpen

REMOTE · BULLPEN.SALE

AI sales team that works the phone: gets a real person on the line. Agents sign up by paying (MPP).

Available components

+3 this week 73 Trust /100

Last scanned (21 hours ago)

Scores higher than 59% of remote servers

Reachable. Last reached 21 Nov 2026.

Category CRM and Sales

Recent critical change

Authorization (9 Nov 2026). See the changelog before you install this server.

Trust breakdown (7 categories)

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 Security63
Transport & Reachability100
Schema Quality & AI Usability72
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 3191 tokens (~75/item across 42 items; 42 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management53
  • Stability observed for 16 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage98
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 94% 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
  • All 4 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 43 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 19 Nov 26 +1

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

  • 17 Nov 26 +1

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

  • 15 Nov 26 +1

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

  • 14 Nov 26 0
    • Tool “create_campaign” rewrote its description, which is the text the model reads security
    • Tool “find_companies” rewrote its description, which is the text the model reads security
    • Tool “set_campaign_customs” rewrote its description, which is the text the model reads security
    • Tool “set_mobile” rewrote its description, which is the text the model reads security
    • Tool “work_campaign” rewrote its description, which is the text the model reads security
    • Schema quality: 2890 → 3191 ▼ functional
    • New tool “list_campaign_contacts” functional
    • “find_companies” added an optional parameter “campaign_id” cosmetic
    • “work_campaign” added an optional parameter “contact_ids” cosmetic
    • “work_campaign” added an optional parameter “limit” cosmetic
  • 13 Nov 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.

  • 11 Nov 26 +1

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

  • 9 Nov 26 −6
    • Authorization: partial → fail ▼ critical
    • New tool “delete_call”, which the server declares destructive security
  • 8 Nov 26 0
    • Schema quality: 2289 → 2816 ▼ functional
    • New tool “draft_team_profile” functional
    • New tool “get_team_profile” functional
    • New tool “rename_crew_member” functional
    • New tool “set_campaign_customs” functional
    • New tool “set_team_profile” functional
Diagnostics

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 21 Nov 2026 · Probed https://bullpen.sale/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=*.bullpen.sale CN=YR1,O=Let's Encrypt,C=US 27 Sept 2026 26 Dec 2026 RSA 2048 SHA256-RSA 56d0c4254cfe22b46970c33f9e9ec9fceb6
SANs: *.bullpen.sale, bullpen.sale
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 bullpen.sale. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
sale. DS published 54547 8 Verified
bullpen.sale. No DS 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=31536000; includeSubDomains; preload
www-authenticate Bearer resource_metadata="https://bullpen.sale/.well-known/oauth-protected-resource/mcp"

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://bullpen.sale/mcp Verified 200
http (plaintext) http://bullpen.sale/mcp HTTPS enforced 308 https://bullpen.sale/mcp
MCP tools · 42 exposed · ~3,065 tokens

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 →

Tool Tokens
accept_outbound_agreement ~101

Accept the agreement on your person's behalf ONLY after they have read it and told you they agree. Requires their full name as they typed it; recorded with this connection. Admin or manager only.

NameTypeReqDescription
full_namestringyesThe accepting person's first and last name, as they typed it.
person_agreedbooleanyestrue only if your person explicitly said they agree.
versionstringyesVersion from get_outbound_agreement.

No output schema declared.

No examples provided.

ask_brain ~44

Answer a question from the workspace's own knowledge (calls, notes, docs), with sources, limited by the key's role.

NameTypeReqDescription
questionstringyesThe question.

No output schema declared.

No examples provided.

ask_herman ~80

Talk to Herman, the manager agent who runs the whole bullpen in plain language: status, finding companies, running campaigns, sending the crew to call. Anything that reaches the outside world comes back as a pending action with an id — nothing goes out until confirm_herman_action.

NameTypeReqDescription
messagestringyesWhat you want, in plain words.

No output schema declared.

No examples provided.

bullpen_about ~62

What Bullpen does, what it costs, and how to get a workspace: free with $10 of credits (no card) when your person signs in, or by paying over MPP. Call this first if you have no key. (No API key needed.)

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

bullpen_signup ~196

Start creating a Bullpen workspace for your principal by paying with the Machine Payments Protocol (MPP, Stripe). Returns the 402 payment challenge and the exact URL to retry with your MPP client (e.g. `npx @stripe/link-cli mpp pay <url>`). The paid retry returns an api_key; pass it to this MCP server as `Authorization: Bearer bp_live_…`. $25–$500, all of it becomes credits, plus $10 free. (No API key needed.)

NameTypeReqDescription
agent_namestring–Your name, shown in the workspace log.
amountnumber–USD to load as credits, 25–500. Default 25.
companystringyesCompany name for the workspace.
owner_emailstringyesEmail of the person who will own the workspace. They get an invite.
owner_namestring–Owner's name, optional.

No output schema declared.

No examples provided.

buy_credits ~57

A Stripe Checkout link your person opens to add credits by card ($20–$10,000). Agents with a wallet can use top_up_credits instead.

NameTypeReqDescription
usdnumberyesAmount in USD, 20–10000.

No output schema declared.

No examples provided.

buy_number ~95

Buy a number: $3/month from prepaid credits (first month charged now). Default is a crew line, and a crew member is put on it right away; for:"me" makes it your person's own caller ID instead. Admin or manager only. Confirm with your person before buying.

NameTypeReqDescription
e164stringyesNumber from search_numbers, E.164.
forstring–crew (default) or me.

No output schema declared.

No examples provided.

confirm_herman_action ~58

Run or drop a pending action Herman proposed (a call, text or Salesforce update). Only confirm what your principal actually wants.

NameTypeReqDescription
decisionstringyes–
idstringyesPending action id from ask_herman.

No output schema declared.

No examples provided.

connect_google ~27

A link your person opens to approve Google Calendar and Gmail, for booking meetings and sending mail.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

connect_salesforce ~32

A link your person opens to approve Bullpen in Salesforce, so every call writes there. Admin or manager only.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

create_campaign ~75

Create a calling campaign. It starts paused: add contacts (import_campaign_contacts, or find_companies with campaign_id), set its customs, then work_campaign switches it on.

NameTypeReqDescription
goalstring–What a win looks like, e.g. 'book a 20-minute demo'.
namestringyesCampaign name.

No output schema declared.

No examples provided.

credits_status ~26

Prepaid credit balance and recent usage. Spending tools return a 402 error at zero.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

delete_call ~74

Delete the transcript, summary and recording of one call, for good (a deletion request from the person called, or your team's retention policy). The call row, its outcome and its cost remain. Reps can delete their own calls; managers and admins any.

NameTypeReqDescription
idstringyesCall id or SID from list_calls.

No output schema declared.

No examples provided.

draft_team_profile ~102

Draft a team profile from the company's website and any notes from your person. Returns a draft and its sources; nothing is saved. Walk your person through it — name as spoken, product names, tone, words to use and avoid, house rules, the knock line — and save what they approve with set_team_profile.

NameTypeReqDescription
notesstring–What your person said about how the crew should sound.
websitestring–Company website, if known.

No output schema declared.

No examples provided.

find_companies ~106

Search for companies to sell to (e.g. 'HVAC companies in Salt Lake City'). Returns each company's id, name, main phone line, website, city and state. Pass campaign_id to add them to that campaign's contact list in the same call.

NameTypeReqDescription
campaign_idstring–Optional: add the companies found to this campaign.
maxnumber–Max results, default 20.
querystringyesWho you're looking for, with place.

No output schema declared.

No examples provided.

floor_state ~14

Live and recent crew calls.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_a_human ~120

A crew member dials the number, works the phone menu, hold and AI receptionist until a real person answers, then connects the key's owner into the live call. Spends credits ($0.30 per crew minute; no extra charge when a person is reached). Company lines only unless the callee gave written consent.

NameTypeReqDescription
targetstring–Who to ask for.
tostringyesE.164 phone number, e.g. +18015551234.
whystring–One line on why we're calling.

No output schema declared.

No examples provided.

get_call_transcript ~100

One call in full: the transcript as text and as timed lines with speakers (crew, the person reached, and your person after a handoff), the summary, outcome, and a signed recording link (MP3, valid one hour). Pass an id or call SID from list_calls.

NameTypeReqDescription
idstringyesCall id or call SID (CA…) from list_calls.
recordingboolean–Include a recording link. Default true.

No output schema declared.

No examples provided.

get_outbound_agreement ~42

The full Outbound Compliance Agreement and its version. Show it to your person before accept_outbound_agreement; calls and texts stay locked until it's accepted.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_team_profile ~85

The team profile the crew works from: company name as spoken, what the team sells, trademarks and how to say them, tone, how calls open and close, words to use and never use, house rules, the knock line, caller-ID name, and per-campaign overrides. Read it first; if is_set is false, offer to build it with draft_team_profile.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

hire_crew ~39

Put an AI crew member (name, voice, role) on every free phone line so the crew can dial. Run after a number is bought.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

import_campaign_contacts ~49

Add contacts to a campaign from CSV text (header row: company, phone, name, title, email).

NameTypeReqDescription
csvstringyesCSV text.
idstringyesCampaign id.

No output schema declared.

No examples provided.

invite_teammate ~60

Invite someone to the workspace by email; they get a sign-in link that lands on the join page. Roles: rep, manager, admin (only admins invite admins).

NameTypeReqDescription
emailstringyesTheir email.
rolestring––

No output schema declared.

No examples provided.

knock ~82

Reach a human at a company's main line and leave a short hello pointing to your principal. Business hours, once a week per company. Spends credits.

NameTypeReqDescription
companystringyesCompany name.
notestring–What to leave.
targetstring–Who to ask for.
tostringyesCompany main line, E.164.

No output schema declared.

No examples provided.

list_calls ~109

Recent calls, newest first: id, call SID, when, number, crew member, whether it was handed to your person, outcome, summary, and whether a transcript and recording exist. Reps see their own calls; managers and admins see all.

NameTypeReqDescription
limitnumber–How many, 1–50. Default 10.
sincestring–Optional ISO time; only calls after it.
tostring–Optional phone number; only calls to or from it.

No output schema declared.

No examples provided.

list_campaign_contacts ~59

Every contact in a campaign with its status (new, researched, excluded), phone, line type and whether it is already in a play.

NameTypeReqDescription
idstringyesCampaign id.
limitnumber–Max rows, default 200.

No output schema declared.

No examples provided.

list_team ~28

Members (role, whether their mobile is set, Herman on) and pending invites with their links.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

onboarding_status ~65

Checklist of what this workspace still needs before every feature works (Herman, compliance agreement, phone number, crew, your mobile, credits, Salesforce, Google, texting, team), in the order to do them, with the tool or link for each. Start here after signing up.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

open_page ~136

A link your person can open: floor (the live floor: who's on a call right now, and recent calls); human_line (Human line: your mobile and live bridge calls); herman (the app home, with Herman in the corner); campaigns (campaigns); companies (companies found and researched); integrations (phone numbers, texting registration, Salesforce and Google); billing (credits, billing and the Outbound Compliance Agreement); team (members and invites); api_keys (API keys and agent connections (revoke here)). "floor" is the live floor to watch calls. (No API key needed.)

NameTypeReqDescription
pagestringyes–

No output schema declared.

No examples provided.

rename_crew_member ~124

Rename a crew member for the team's culture or region, optionally with a new voice, persona or greeting. Admin only; paid workspaces (402 otherwise — buy_credits first). Keys from list_team's crew or onboarding_status.

NameTypeReqDescription
greetingstring–Optional: their outbound opener.
keystringyesCrew member key, e.g. jasper.
namestringyesNew first name.
personastring–Optional: who they are, a few lines.
voice_idstring–ElevenLabs voice id, optional.

No output schema declared.

No examples provided.

research_company ~34

Who to ask for at a company returned by find_companies.

NameTypeReqDescription
idstringyesCompany id from find_companies.

No output schema declared.

No examples provided.

search_numbers ~40

Available US numbers by area code, for the crew's lines.

NameTypeReqDescription
area_codestringyes3-digit area code, e.g. 801.

No output schema declared.

No examples provided.

send_email ~51

Email from the workspace's agent inbox.

NameTypeReqDescription
ccstring–Optional cc.
subjectstringyesSubject.
textstringyesPlain-text body.
tostringyesRecipient.

No output schema declared.

No examples provided.

send_text ~43

Text from the workspace's line. Opt-outs are honored. Spends credits.

NameTypeReqDescription
bodystringyesMessage.
tostringyesE.164 number.

No output schema declared.

No examples provided.

set_campaign_customs ~145

Override how one campaign sounds and who it is (admin only). Customs: tone, opening (said as the first line; {name} and {team} fill in), closing, say, never_say, customs, knock_line. Identity, for a campaign that calls as a different company: spoken_name, pronunciation, about, website, caller_name. Handoff: closer_name and handoff_number, the person and phone that ring when a live prospect wants a human on this campaign's calls (instead of the workspace's human line). Null returns a key to the team default.

NameTypeReqDescription
campaign_idstringyesCampaign id.
customsobjectyes–

No output schema declared.

No examples provided.

set_mobile ~109

Set the mobile that rings when the crew reaches a person (get_a_human). This is your number for every call in the workspace; to send one campaign's live handoffs to someone else, set handoff_number with set_campaign_customs instead. Yours by default; managers can set a teammate's with user_id (from list_team).

NameTypeReqDescription
mobilestringyesE.164 or 10-digit US number.
user_idstring–Teammate's user_id, optional.

No output schema declared.

No examples provided.

set_team_profile ~135

Save the team profile (admin only). Pass only fields your person approved: spoken_name, pronunciation, about, website, trademarks [{name, say_as}], tone, opening, closing, say [], never_say [], customs (house rules, prose), knock_line ({name} = crew member's first name, {team} = company), caller_name (≤15 chars). It shapes how the crew sounds; it cannot change the rules (the crew says it's an AI when asked, keeps to calling hours, honours do-not-call, invents nothing).

NameTypeReqDescription
profileobjectyesFields to set. Null clears a field.

No output schema declared.

No examples provided.

top_up_credits ~64

Start an MPP credit top-up ($5–$500). Returns the 402 challenge and the URL to pay and retry with your MPP client, sending your key as X-Bullpen-Key.

NameTypeReqDescription
amountnumberyesUSD, 5–500.

No output schema declared.

No examples provided.

turn_on_herman ~24

Switch Herman on for this member so ask_herman works.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

watch_companies ~38

Add companies to Social Intel, which scans them for buying and risk signals.

NameTypeReqDescription
namesstringyesCompany names, comma or newline separated.

No output schema declared.

No examples provided.

whoami ~20

The workspace, member and role this API key acts as.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

work_campaign ~115

Send the crew to work a campaign now. With only the campaign id it takes the reachable contacts not yet in a play (company lines, not excluded), easiest first, up to limit (default 10, max 25), and switches a paused campaign on. Pass contact_ids to choose. Spends credits.

NameTypeReqDescription
contact_idsarray–Optional: specific campaign contact ids.
idstringyesCampaign id.
limitinteger–How many to start when no contact_ids are given (1-25).

No output schema declared.

No examples provided.

Install

How do I install the Bullpen MCP server?

Bullpen is a hosted endpoint at https://bullpen.sale/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 · bullpen.sale

# add to Claude Code
claude mcp add --transport http sale-bullpen-bullpen 'https://bullpen.sale/mcp'
Common questions

What is the Bullpen MCP server?

Bullpen is an MCP server listed in the public MCP registry as sale.bullpen/bullpen. AI sales team that works the phone: gets a real person on the line. Agents sign up by paying (MPP). This page covers its hosted endpoint (https://bullpen.sale/mcp).

Is the Bullpen MCP server safe to use?

Bullpen scores 73 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 Bullpen MCP server expose?

Bullpen exposes 42 tools: bullpen_about, bullpen_signup, whoami, credits_status, top_up_credits, and 37 more. Their descriptions and schemas cost roughly 3,065 tokens of context every time the server is loaded.

Does the Bullpen MCP server require authentication?

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

Is the Bullpen MCP server still maintained?

Bullpen is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the Bullpen MCP server?

VerifyMCP ran 13 checks on Bullpen, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.