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.

SalesMap

REMOTE · API.SALESMAP.SITE · 2 COMPONENTS

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

0 this week 76 Trust /100

Last scanned (2 hours ago)

Scores higher than 66% of remote servers

Reachable. Last reached 5 Nov 2026.

Category CRM and Sales

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 Security89
Transport & Reachability100
Schema Quality & AI Usability73
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 4152 tokens (~519/item across 8 items; 8 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
  • Stability check failed: schema churn in the 15 days we've observed: 11 tool removals, 0 breaking changes, 0 auth/transport breaks, 2 additions. See how to fix → Fail
Tool Coverage87
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 54% of tool parameters carry a description.Partial
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
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.

  • 4 Nov 26 0
    • “feedback” reworded the description of “verdict” cosmetic

    1 cosmetic change on this day. Switch on “Show cosmetic changes” to see it.

  • 3 Nov 26 0
    • Tool “set_limits” rewrote its description, which is the text the model reads security
    • Tool “discover” rewrote its description, which is the text the model reads security
    • Tool coverage: 59% → 54% ▼ functional
    • “discover” added an optional parameter “research” cosmetic
    • “set_limits” reworded the description of “weeklyDiscover” cosmetic
    • “discover” dropped the optional parameter “resume” cosmetic
    • “discover” dropped the optional parameter “searches” cosmetic
    • “discover” dropped the optional parameter “callerSearch” cosmetic
    • “discover” dropped the optional parameter “limit” cosmetic
    • “discover” dropped the optional parameter “mode” cosmetic
  • 31 Oct 26 0
    • Tool “discover” rewrote its description, which is the text the model reads security
    • Tool “job” rewrote its description, which is the text the model reads security
    • “discover” added an optional parameter “fresh” cosmetic
  • 28 Oct 26 0
    • Tool “discover” rewrote its description, which is the text the model reads security
  • 27 Oct 26 0
    • Tool “whoami” rewrote its description, which is the text the model reads security
    • Tool “discover” rewrote its description, which is the text the model reads security
    • Tool “quote” rewrote its description, which is the text the model reads security
    • Tool “set_limits” rewrote its description, which is the text the model reads security
    • Schema quality: 3637 → 4023 ▼ functional
    • New tool “feedback” functional
    • “discover” added an optional parameter “max_credits” cosmetic
    • “set_limits” added an optional parameter “confirmCredits” cosmetic
    • “set_limits” added an optional parameter “monthlyCredits” cosmetic
    • “set_limits” added an optional parameter “weeklyDiscover” cosmetic
    • “discover” reworded the description of “limit” cosmetic
    • “discover” reworded the description of “mode” cosmetic
    • “quote” reworded the description of “tool” cosmetic
    • “discover” dropped the optional parameter “max_usd” cosmetic
    • “set_limits” dropped the optional parameter “confirmUsd” cosmetic
    • “set_limits” dropped the optional parameter “monthlyUsd” cosmetic
  • 26 Oct 26 +1
    • A breaking change shipped without a version bump: still 0.1.0 ▼ security
    • Tool “playbook” was removed ▼ security
    • Tool “seller_profile” rewrote its description, which is the text the model reads security
    • Tool “job” rewrote its description, which is the text the model reads security
    • Tool “quote” rewrote its description, which is the text the model reads security
    • Schema quality: 3228 → 3637 ▼ functional
    • Prompt “playbook” was removed ▼ functional
    • Tool coverage: 45% → 53% ▲ functional
    • New prompt “discover” functional
    • New prompt “draft” functional
    • New tool “discover” functional
    • New tool “voice_scan” functional
  • 25 Oct 26 −1
    • A breaking change shipped without a version bump: still 0.1.0 ▼ security
    • Tool “events” was removed ▼ security
    • Tool “ai_adoption” was removed ▼ security
    • Tool “discover” was removed ▼ security
    • Tool “rank” was removed ▼ security
    • Tool “signals” was removed ▼ security
    • Tool “tech_scan” was removed ▼ security
    • Tool “verify” was removed ▼ security
    • Tool “verify_signal” was removed ▼ security
    • Tool “watch” was removed ▼ security
    • Tool “watch_changes” was removed ▼ security
    • Tool “job” rewrote its description, which is the text the model reads security
    • Tool “playbook” rewrote its description, which is the text the model reads security
    • Tool “quote” rewrote its description, which is the text the model reads security
    • Tool “seller_profile” rewrote its description, which is the text the model reads security
    • Tool coverage: 62% → 45% ▼ functional
    • Prompt “changes” was removed ▼ functional
    • Prompt “discover” was removed ▼ functional
    • Prompt “events” was removed ▼ functional
    • Prompt “rank” was removed ▼ functional
    • Prompt “research” was removed ▼ functional
    • Prompt “signals” was removed ▼ functional
    • Prompt “verify” was removed ▼ functional
    • Prompt “watch” was removed ▼ functional
    • Schema quality: 625 → 538 ▲ functional
    • “playbook” added an optional parameter “evidence” cosmetic
    • “playbook” added an optional parameter “mobiles” cosmetic
    • “playbook” added an optional parameter “resume” cosmetic
  • 24 Oct 26 +1
    • Tool “discover” rewrote its description, which is the text the model reads security
    • Tool “events” rewrote its description, which is the text the model reads security
    • Tool “job” rewrote its description, which is the text the model reads security
    • Tool “playbook” rewrote its description, which is the text the model reads security
    • Tool “rank” rewrote its description, which is the text the model reads security
    • Tool “signals” rewrote its description, which is the text the model reads security
    • Tool “verify” rewrote its description, which is the text the model reads security
    • “playbook” added an optional parameter “hard” cosmetic
    • “playbook” added an optional parameter “mode” cosmetic
    • “discover” added an optional parameter “hard” cosmetic
    • “discover” added an optional parameter “mode” cosmetic
    • “events” added an optional parameter “mode” cosmetic
    • “rank” added an optional parameter “hard” cosmetic
    • “rank” added an optional parameter “mode” cosmetic
    • “signals” added an optional parameter “mode” cosmetic
    • “verify” added an optional parameter “mode” cosmetic
    • “discover” reworded the description of “callerSearch” cosmetic
    • “events” reworded the description of “callerSearch” cosmetic
    • “job” reworded the description of “id” cosmetic
    • “playbook” reworded the description of “callerSearch” cosmetic
    • “rank” reworded the description of “callerSearch” cosmetic
    • “signals” reworded the description of “callerSearch” cosmetic
    • “verify” reworded the description of “callerSearch” cosmetic
    • “rank” dropped the optional parameter “paid” cosmetic
    • “discover” dropped the optional parameter “callerJudge” cosmetic
    • “discover” dropped the optional parameter “paid” cosmetic
    • “events” dropped the optional parameter “budgetUsd” cosmetic
    • “events” dropped the optional parameter “paid” cosmetic
    • “playbook” dropped the optional parameter “callerJudge” cosmetic
    • “playbook” dropped the optional parameter “paid” cosmetic
    • “rank” dropped the optional parameter “callerJudge” cosmetic
    • “signals” dropped the optional parameter “paid” cosmetic
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 5 Nov 2026 · Probed https://api.salesmap.site/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=api.salesmap.site CN=YE1,O=Let's Encrypt,C=US 11 Oct 2026 9 Jan 2027 ECDSA 256 ECDSA-SHA384 6d64b914ac5f99f769eab7651db88170a01
SANs: api.salesmap.site
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of api.salesmap.site. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
site. present 31826 13 Verified
salesmap.site. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Enforced and verified

The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.

Result Enforced and verified
Enforced On tool calls
HTTP status 200

WWW-Authenticate challenge Bearer resource_metadata="https://api.salesmap.site/.well-known/oauth-protected-resource/mcp"

Bearer resource_metadata="https://api.salesmap.site/.well-known/oauth-protected-resource/mcp"

Protected resource metadata

Document https://api.salesmap.site/.well-known/oauth-protected-resource/mcp
Retrieved Yes
Resource https://api.salesmap.site/mcp
Authorisation server https://lzotkacjqkjxubuymhlk.supabase.co/auth/v1

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://api.salesmap.site/mcp Verified 200
http (plaintext) http://api.salesmap.site/mcp HTTPS enforced 301 https://api.salesmap.site/mcp
MCP tools · 8 exposed · ~4,152 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
discover ~2,154

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 <seller site>", "who should I sell to", "who should…

NameTypeReqDescription
championsarray––
companiesarray––
confirm_tokenstring–The token a previous call returned in `confirm`, standing for the user's agreement to that cost; one use, same arguments.
connectionsobject––
connectorsarray––
contactedarray––
contextobject–The user's own facts about their company: who they are, the company, product, ICP, buyer roles, customers, competitors, deals won and lost, regions, exclusions. Fields left out come from the saved se…
customersarray––
daysinteger––
doNotContactarray––
evaluatorsarray––
evidencearray–Passages the user found on a public page (domain, url, verbatim quote, date as printed); each is checked before it counts
freshboolean–true: research the named companies again even when they were researched in the last 7 days. Left out, such a call asks the user first, or returns that saved research (`saved`) with nothing charged.
hardarray––
icpobject––
includeShownboolean––
max_creditsinteger–Most credits this call may use; default its quote. A call quoted over it is refused.
openDealsarray––
previousConnectionsobject––
priorContactsarray––
researchinteger–How many accounts to research, 1 to 10: each is screened, researched and written up with its signals, fit, angle and contacts. 0 (the default) returns the ranked list alone: every company found, each…
sellerstring––
vendorsarray––
NameTypeReqDescription
accountsarray––
accountsUrlstring––
addMorearray––
budgetobject––
costobject––
droppedobject––
evidencearray––
existingCustomersobject––
fullstring–The full result on disk: every signal, path and field (local runs only)
icpobject––
jobobject––
listedarray––
listingobject––
marketarray––
moreinteger––
narrowobject––
needPatternHitsarray––
needPatternsarray––
needPatternsFromstring––
nextListAtstring|null––
noticestring––
paidarray––
profileobject––
repeatobject––
savedobject––
sincestring––
sourcesarray––
stoppedstring––
stoppedEarlyarray––
todaystring––
upcomingEventsinteger––

No examples provided.

feedback ~259

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 <field>Flags with the attack family.

NameTypeReqDescription
domainstringyesThe company's domain, as the ranked list shows it
reasonstring–Why, from the list
verdictstringyesgood_fit, not_fit or already_talking (both leave later discovers)
NameTypeReqDescription
costobject––
domainstringyes–
reasonstring|nullyes–
updatedAtstringyes–
verdictstringyesgood_fit, not_fit or already_talking (both leave later discovers)

No examples provided.

job ~270

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 <field>Flags with the attack family.

NameTypeReqDescription
idstringyesThe job id a call returned
NameTypeReqDescription
costobject––
createdAtstringyes–
errorstring|nullyes–
finishedAtstring|nullyes–
idstringyes–
lastStepAtstring––
lastStepSecondsAgointeger––
partial–yes–
pollstring––
restartsinteger––
result–yes–
stalledboolean––
statusstringyes–
toolstringyes–

No examples provided.

quote ~209

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 <field>Flags with the attack family.

NameTypeReqDescription
inputobject–That tool's arguments, as in a call to it
toolstringyesThe tool to quote, e.g. discover
NameTypeReqDescription
canSpendCreditsnumberyes–
costobject––
fitsbooleanyes–
inputobjectyes–
quoteCreditsnumberyes–
shortfallCreditsnumber––
toolstringyes–
topUpstring––

No examples provided.

seller_profile ~388

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 <field>Flags with the attack family.

NameTypeReqDescription
contextobject–Fields to save, merged into the saved profile field by field. Omit to read.
sellerstringyesThe user's own company site, e.g. getklira.com
NameTypeReqDescription
costobject––
missingarrayyes–
pathstringyes–
profile–yes–
questionsarrayyes–
savedbooleanyes–
sellerstringyes–
signalsobject––

No examples provided.

set_limits ~353

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 <field>Flags with the attack family.

NameTypeReqDescription
confirmCredits––Credits; paid calls quoted over it need the user's yes first; 0 means every call; null means none; omitted, it is kept
monthlyCredits––Credits; null removes this limit; omit to keep it
weeklyDiscoverboolean–The weekly free list and its new-accounts email to the signed-in user; only on the user's explicit yes; omitted, it is kept
NameTypeReqDescription
canSpendCreditsnumberyes–
confirmCreditsnumber|nullyes–
costobject––
creditsnumberyes–
frozenbooleanyes–
weeklyDiscoverbooleanyes–
windowsobjectyes–

No examples provided.

voice_scan ~321

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 <field>Flags with the attack family.

NameTypeReqDescription
bodystringyesThe draft, as plain text
formatstringyesconnection_note (LinkedIn invite note), linkedin_message, inmail or email
subjectstring–The subject line, for an email or InMail
NameTypeReqDescription
charsnumberyes–
costobject––
failsarrayyes–
formatstringyes–
limitnumber––
passbooleanyes–
warningsarrayyes–
wordsnumberyes–

No examples provided.

whoami ~198

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 <field>Flags with the attack family.

Input schema present but exposes no named parameters.

NameTypeReqDescription
connections–yes–
costobject––
creditsobjectyes–
crm–––
freearrayyes–
frozenstring––
limitsobjectyes–
linksobjectyes–
sellersarrayyes–
signedInWithstringyes–
userobjectyes–
workspaceobjectyes–

No examples provided.

Install

How do I install the SalesMap MCP server?

SalesMap is a hosted endpoint at https://api.salesmap.site/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 · api.salesmap.site

# add to Claude Code
claude mcp add --transport http site-salesmap-signals 'https://api.salesmap.site/mcp'
Common questions

What is the SalesMap MCP server?

SalesMap is an MCP server listed in the public MCP registry as site.salesmap/signals. Checked buying signals and ranked lead lists for your agent. Never contacts anyone. This page covers its hosted endpoint (https://api.salesmap.site/mcp).

Is the SalesMap MCP server safe to use?

SalesMap scores 76 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 SalesMap MCP server expose?

SalesMap exposes 8 tools: discover, seller_profile, voice_scan, feedback, whoami, and 3 more. Their descriptions and schemas cost roughly 4,152 tokens of context every time the server is loaded.

Does the SalesMap MCP server require authentication?

Yes. SalesMap asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

Is the SalesMap MCP server still maintained?

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