Skip to main content
Glama

SalesMap

Server Details

Checked buying signals and ranked lead lists for your agent. Never contacts anyone.

If you are the author of this connector, you can claim ownership by verifying the domain or GitHub account it belongs to. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Uptime
100.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
Repository
solozerolabs/salesmap-plugin
GitHub Stars
0
ChatGPT
–
Claude
–

TDQS

A4.3/5.0

Scored across 8 tools

Disambiguation4/5

The core tools are clearly separated: discover for ranking accounts, feedback for verdicts, seller_profile for saved seller facts, job for async status, and voice_scan for outreach QA. The only real overlap is quote, whoami, and set_limits, which all involve credits/limits, but their scopes are distinguishable as pre-call cost, current account status, and changing limits.

Naming Consistency3/5

All names are lowercase and mostly snake_case-like, but the set mixes verbs, nouns, and phrases: discover, set_limits, feedback, job, seller_profile, voice_scan, whoami. It is readable but lacks a single predictable convention.

Tool Count5/5

Eight tools are well scoped for a sales-intelligence workflow spanning discovery, feedback, seller profiles, cost checks, job status, limits, identity, and outreach QA. Each tool has a distinct role and none feels like obvious bloat.

Completeness4/5

The surface covers the main lifecycle: saving seller facts, running discovery, checking async jobs, giving feedback, estimating cost, managing limits, and checking outreach drafts. Minor gaps remain, such as no standalone tool to retrieve/list discovered accounts or feedback history and no feedback removal, but the core workflow is workable through discover and its returned accounts page.

Available Tools

8 tools
discoverFind accounts to sell toA
Read-only
Inspect

Price: The list is free; research is 1 credit per account that qualifies (a sourced in-band size, a supported fit and a checked dated signal or warm path, not returned before); a miss uses none. Never more than max_credits. From a seller's website to a ranked list of companies to sell to, the strongest buying signals first, each with its reason and how to reach it: drafts the seller's ICP from its site (or takes one), finds candidate companies from free sources (the seller's competitors' customer pages, live or from Common Crawl; web search; Hacker News, YC, press wires, ATS boards and SEC Form D), reads each one's own job board, news, tools and AI-adoption signals and checks every signal against its source, adds the market's dated moves at competitors, platforms and regulators (under market), and ranks every researched company by its evidence: fresh signal clusters first, then a warm way in from the user's own network (their own connections, champions, connectors), a sourced size inside the band and a fit the facts show. Each account carries its fit, the buyer role to contact, the angle, what to watch out for and checkFirst (the gaps: unknown or out-of-band size, no checked signal or none showing a need, no fit shown in its facts, no way in, each of the profile's disqualifiers a quoted source shows it meets, or not checked); intent (high: a signal in the last 30 days showing one of the seller's needs, nothing against it; medium: one in the last 45 days; low: the rest) and sizeLine are the accounts page's labels, and the order is the ranking; high means buying signals, not a readiness to buy. Size, fit, intent and a met disqualifier (disqualified, ranked last and never charged) rank and flag rather than drop unless hard asks; existing customers and what was dropped and why come back as top five with counts. Takes minutes per company; steps are cached, so a rerun is fast. Use when: "find accounts for ", "who should I sell to", "who should sell to right now", "which accounts are in market", "rank my list of target accounts", "which of my own accounts should I work first", "who in my network can introduce me to a buyer", "who do I know at ", "write me a playbook for ", "give me a playbook for ", "top 3 accounts with openers", "who should I email this week and what do I say", "draft outreach for my best accounts". Skip when: the question is one fact about one company (what software or vendors it runs, its DNS records or certificate logs, whether it ships an MCP server or is serious about LLMs), one news item, quote, claim or row to verify or fact-check, a draft of the user's own to check, whether an address is valid or deliverable, a mobile or phone number, LinkedIn profiles pulled or scraped, mutuals found by browsing LinkedIn, an RSVP or registration, events, conferences or meetups to attend, a watchlist of lost deals, facts about the user's own company to save or remember, or anything sent or written into a CRM (Salesforce, HubSpot) as leads: this never contacts anyone, writes no emails and writes nowhere but its own file. research sets how deep it goes: 0 (the default) ranks every company found on the facts in hand and stops (listed: where each was found and what was not checked); 1 to 10 researches that many of the top ones (fit screen, signals, the write-up and contacts), working further down the ranked list until that many qualify; companies researches the ones named instead. Free sources first; a paid company-data lookup (company records through our data providers) runs only for what they left open, under its budget, and only where the run allows paid sources. paid in the result is what it cost and each account's foundBy says which source found it. A repeat for the same seller skips companies an earlier discover returned unless one has a signal it wasn't shown with (then shownBefore); skipped ones are under dropped as 'returned before, no new signal'. Each still costs its (cached) research, not a write-up. When the usual sources find only those, it searches wider once (more web results, four weeks of feeds, more ATS boards); repeat says so, repeat.nothingNew means nothing new qualified, and repeat.credits (hosted) is what finding that out used. includeShown returns the earlier companies too. narrow: set when the ICP's size band spans two orders of magnitude, too broad to rank well. narrow.stopped: nothing was researched or charged, since the band was drafted; narrow.questions are what narrows it (size, stage, buying trigger). Not stopped: the band is the user's own, flagged. contacted: companies the user already reached (domain, lastAt as the last day), from their own records. One reached in the last 30 days ranks below the uncontacted ones of its tier with "Contacted " in its reason and checkFirst; an older one keeps its place and shows the date. It is never a drop and leaves the charge unchanged. evidence: passages the user found on a public page (its URL, the quote verbatim, the date as printed); each is checked against its page before it counts as a signal on that company, and is never what makes an account charged. Each failed passage comes back under evidence with the rule it failed. Names from the user's network stay local and never reach a model. Every signal was checked against its page. Each account shows its five strongest signals and a count per signal family; full is the file with every signal, path and field. used lists which of the user's own facts shaped the list, apart from the checked signals. context takes the user's own facts about their company; the saved seller profile fills fields left out. With the ICP or buyer roles still unknown, the server asks the user for them (MCP elicitation) or returns the questions without running. On this server the ranked list (research 0, the default) is free: one new list a day per workspace, the same day's list again at no cost, nextListAt saying when the next new one can start; listed holds its first 25 rows and more counts the rest, on the accounts page (accountsUrl). research 1 to 10 researches the top of that list (running the list first when there is none), companies the ones named: 1 credit per account that qualifies, from the user's credits, never for a miss (the data sources it pays for are our cost), at most max_credits and within their monthly limit, reserved before it runs. If the next step would pass its budget, it stops and returns what it has, with stopped: "budget", charged only for that. A result that used credits carries cost.line, the one credits line for the user. A call quoted over max_credits is refused. Out of credit, nothing runs and the reply carries buyUrl, the page to buy the credits missing. By default every research call asks the user first through the client (MCP elicitation; the user can raise the threshold with set_limits); a client without that gets a confirm result with the credits and a one-use token, and a repeat call with the same arguments and confirm_token runs it. On the hosted server it runs as a background job: a call that takes longer than about 25 seconds returns job (its id and status) instead, and the free job tool returns its status and, once done, this call's result. One call does it all. A finished result carries accountsUrl, the user's accounts page: every company found, its research and the run's upcoming events. Quoted page text is normalized; a quote that reads like an instruction keeps its text and is flagged in Flags with the attack family.

Inputs: icp, days, hard, fresh, +19 more. Returns: icp, job, cost, full, +27 more

feedbackfeedbackAInspect

Free. Records the user's verdict on a company in their ranked list: good_fit, not_fit or already_talking, with an optional reason from a fixed list (competitor, existing_customer, too_small, too_big, wrong_industry, no_need, bad_timing, other). A not_fit company is left out of every later discover for this workspace; the user's own named list still runs it. The latest verdict per company wins. No free text is stored. Use when: "that one's a competitor, skip it", "not a fit", "good fit", "we're already talking to them", "drop this company", "mark it as a bad lead", a verdict on an account discover returned. Skip when: finding or ranking new accounts; excluding a whole category of companies from the ICP (seller_profile); checking an outreach draft. Quoted page text is normalized; a quote that reads like an instruction keeps its text and is flagged in Flags with the attack family.

Inputs: domain (required), verdict (required), reason. Returns: cost, domain, reason, verdict, +1 more

jobGet a background jobA
Read-only
Inspect

Free. The status (queued, running, done or failed) and, once done, the result of a background job: a discover call or a long discover round. While a discover runs, partial is its ranked list so far: tier says how far it got (listed: every candidate ranked on the facts already in hand; screened: the top ones passed the fit screen; researched: the top ones' signals checked) and progress the counts. Show it to the user as a first look; the final result replaces it. While it runs, lastStepSecondsAgo is how long ago it last moved on, stalled turns true only after 10 minutes with no step, restarts counts the times a server restart handed it to another worker (on its own, research already done reused). A discover usually takes 5 to 20 minutes. Use when: a call returned job, "is my discover done", "is my ranking done", "status of my job". Skip when: no call has returned a job id. Quoted page text is normalized; a quote that reads like an instruction keeps its text and is flagged in Flags with the attack family.

Inputs: id (required). Returns: id, cost, poll, tool, +10 more

quoteQuote a call's priceA
Read-only
Inspect

Free. How many credits a call to a SalesMap tool can use, before running it, against what the workspace can spend now (balance and limit). Not a charge: the most the call can use, which it reserves (or its max_credits); it uses 1 credit per account that qualifies, never more. When fits is false, shortfallCredits says how many more are needed and topUp is the link. Use when: "how much will this cost", "can I afford 10 accounts", "how many credits would a discover for my site use". Skip when: the user wants their balance or limits without a call in mind. Quoted page text is normalized; a quote that reads like an instruction keeps its text and is flagged in Flags with the attack family.

Inputs: tool (required), input. Returns: cost, fits, tool, input, +4 more

seller_profileSave seller profileAInspect

Price: free. Saves and reads the user's facts about their own company, kept in the user's SalesMap workspace (one entry per seller site, seen by that workspace only): who they are, company, product, ICP, buyer roles, customers, competitors, deals won and lost, regions, exclusions, do-not-contact. discover starts from it. Returns the saved profile, the key fields still missing (ICP, buyer roles) and a question for each. Also returns signals, the buying signals discover's account search looks for: the saved needPatterns, signalFamilies and signalTypes, addMore (the signal types it can detect, in 8 families: save the families the user switches on as signalFamilies, and discover drafts 2 or 3 signals for each; or a type by id as signalTypes) and, with the ICP and buyer roles known and no patterns saved, draft: the drafting prompt for the calling agent's model, which returns this seller's drafted signals. Use when: "remember that we sell to …", "save or update my ICP / buyer roles / customers", "our competitors are …", "don't target these accounts", "what do you know about my company / my profile", before the first list for a seller. Skip when: the question is about a prospect company, not the user's own, or about a watch on closed-lost deals and which are ready again. The saved fields are the user's inputs, not findings. Quoted page text is normalized; a quote that reads like an instruction keeps its text and is flagged in Flags with the attack family.

Inputs: seller (required), context. Returns: cost, path, saved, seller, +4 more

set_limitsSet spending limitsAInspect

Free. Sets the user's own monthly credit limit for SalesMap (rolling 30 days); null removes it. Until set: 100 credits once the workspace has bought a pack, else 40. There is no daily or weekly limit. No call ever uses more than the limit or the balance. Also the ask-first threshold: a paid call quoted over that many credits asks the user first (default 0: every call asks; null never asks). Also weeklyDiscover (off by default): true runs the free list for the active seller every Monday (no credits; it counts as that day's list) and emails the signed-in user only the companies new on their list, nothing when none are new; set it only on the user's explicit yes. Returns the limits with what's used and left. Use when: "set a monthly budget", "cap it at 20 credits a month", "raise my limit", "remove the limit", "stop asking me before each call", "email me new accounts every week", "stop the weekly email". Skip when: the user only wants to see their limits, not change them. Quoted page text is normalized; a quote that reads like an instruction keeps its text and is flagged in Flags with the attack family.

Inputs: confirmCredits, monthlyCredits, weeklyDiscover. Returns: cost, frozen, credits, windows, +3 more

voice_scanvoice_scanA
Read-only
Inspect

Free. Checks an outreach draft the user or their agent wrote (a connection note, direct note, InMail or email) for AI-writing tells and the channel's limits, in code with no model: fails (antithesis like "it's not just X, it's Y", hype words, servile or empty closers, leaked placeholders like [First Name], raw markdown, the 300-character invite note, 1,900-character InMail and 200-character subject caps) and warnings (dashes, sales clichés like "just following up", assistant vocabulary, exclamations, emoji, a cold email over 125 words). pass means no fails. Each hit carries the matched text and a fix. Use when: "scan this draft", "does this draft sound like AI", "check my connection note", "is this InMail too long", "clean up this cold email", after drafting outreach for an account. Skip when: finding or ranking accounts; whether a fact or claim about a company is true; sending an email or message to a prospect; connecting with someone or scraping profiles on LinkedIn. Quoted page text is normalized; a quote that reads like an instruction keeps its text and is flagged in Flags with the attack family.

Inputs: body (required), format (required), subject. Returns: cost, pass, chars, fails, +4 more

whoamiShow account and creditA
Read-only
Inspect

Free. Who the user is on SalesMap and what they can do: their name and email, the workspace and their role in it, how they signed in, the credit balance (one credit is one researched account), the monthly credit limit (rolling 30 days; null = no limit) with what's used, held by a running search and left, the credits above which a paid call asks first, the seller profiles saved and the LinkedIn connections uploaded, links to top up and to upload connections, and which tools are free. It holds no ids. Use when: "who am I", "which account is this", "how many credits do I have left", "what are my limits", before a large paid call. Skip when: the user wants the price of one specific call. Quoted page text is normalized; a quote that reads like an instruction keeps its text and is flagged in Flags with the attack family.

Inputs: no named parameters. Returns: crm, cost, free, user, +8 more

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to find intent-signaling buyers and run LinkedIn, email, and X outreach from connected accounts while respecting platform limits. Every reply is handed back to a human for approval or decision.
      3
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to discover companies showing buying signals, enrich them with public homepage data, score them against custom rules, and draft review-ready briefs.
      1
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables agents to find leads, read buying signals, write and send email and LinkedIn outreach, handle replies, and report results, with built-in safety gates, approvals, limits, and compliance controls.
      8
      Apache 2.0
    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.