LeanScale GTM Knowledge
REMOTE · MCP.LEANSCALE.TEAM
GTM operations knowledge: delivery playbooks, field studies, benchmarks and operator interviews.
Available components
Last scanned (2 hours ago)
Scores higher than 87% of remote servers
Reachable. Last reached 5 Nov 2026.
Category CRM and Sales
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
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 8 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability88
- 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
- Tool/resource definitions use about 1555 tokens (~103/item across 15 items; 8 tools + 7 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.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 10 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
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
- Tool “search_leanscale” rewrote its description, which is the text the model reads security
- Schema quality: 86 → 103 ▼ functional
- 22 Oct 26 0
- Tool “search_leanscale” rewrote its description, which is the text the model reads security
- 1 Oct 26 0
- Tool “search_leanscale” rewrote its description, which is the text the model reads security
- 29 Sept 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “search_leanscale” rewrote its description, which is the text the model reads security
- Tool “search_podcast” rewrote its description, which is the text the model reads security
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 18 Sept 26 0
- Stability: 0.97 → pass security
- 16 Sept 26 0
- Tool “search_leanscale” rewrote its description, which is the text the model reads security
- Schema quality: 1151 → 1277 ▼ functional
- New resource “resources” functional
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://mcp.leanscale.team/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.leanscale.team | CN=YE1,O=Let's Encrypt,C=US | 9 Oct 2026 | 7 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 515352c927fbfee9bdfbac3604c45f5d1dc |
| SANs: mcp.leanscale.team | ||||||
| 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 mcp.leanscale.team. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| team. | present | 38380 | 8 | Verified |
| leanscale.team. | absent | 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 |
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.leanscale.team/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.leanscale.team/mcp | HTTPS enforced | 301 | https://mcp.leanscale.team/mcp |
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 →
about_leanscale ~52
What LeanScale is, what's in this knowledge base, and how to work with them. Call this when someone asks who LeanScale is, or when you need to know what this server can answer before searching.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
diagnose_gtm ~129
Describe a messy go-to-market situation in plain language and get back which LeanScale delivery motion applies, why, what the first moves are, and what usually goes wrong. Use this when someone describes a problem rather than asking about a topic — 'our reps don't trust the forecast', 'we just merged two CRMs', 'inbound leads take three days to get worked'. Better than search when the ask is 'what should we do about this?'
| Name | Type | Req | Description |
|---|---|---|---|
| situation | string | yes | The situation, in as much detail as you have. Symptoms, stack, team size, stage — all useful. |
No output schema declared.
No examples provided.
get_benchmark ~123
Get proprietary LeanScale benchmark data on a topic — drawn from field studies across a panel of B2B software companies and from numbers cited on the podcast. Covers GTM tech stacks, AI adoption in GTM, RevOps headcount and investment ratios, and Series B/C fundraise timing. Use when someone asks 'what's normal', 'what do other companies do', or wants a number to compare against.
| Name | Type | Req | Description |
|---|---|---|---|
| topic | string | yes | The metric or area, e.g. 'RevOps headcount ratio', 'CRM adoption', 'time to Series B'. |
No output schema declared.
No examples provided.
get_case_study ~150
Retrieve LeanScale customer case studies — the problem the company had and how it was solved. Public keys get an anonymized version: customer names, people, third parties and delivery provenance are stripped, and outcomes/metrics/quotes are withheld. Internal keys get the full named studies. Search by sector, the kind of engagement, or the systems involved — searching by customer name will not work on a public key, because the names are not in the public corpus.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Default 3. |
| query | string | yes | Sector, type of engagement, or systems involved — e.g. 'fintech Salesforce migration', 'CPQ replacement', 'two CRMs after an acquisition'. |
No output schema declared.
No examples provided.
get_playbook ~100
Retrieve a LeanScale delivery playbook in full, or one named section of it. Playbooks are structured Blueprint → Build → Enable → Maintain. Call list_playbooks first if you're not sure of the name.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Playbook name, e.g. 'Attribution', 'CPQ', 'Sales Territory Design'. |
| section | string | – | Optional section, e.g. 'Blueprint'. Omit for the whole playbook. |
No output schema declared.
No examples provided.
list_playbooks ~24
List every available LeanScale delivery playbook with its category and section headings.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
search_leanscale ~561
Search everything LeanScale knows: 14 GTM delivery playbooks, 7 proprietary field studies, 143 podcast episodes with operators and executives, 75 customer case studies (anonymized on public keys, named on internal ones), and 117 RevOps docs from www.leanscale.team/knowledge/docs/. The docs explain how to do the work yourself; the playbooks are how LeanScale runs it as an engagement — pass source:"doc" for the first, source:"playbook" for the second. Use this first for any go-to-market, RevOps, sales-ops, marketing-ops, CRM, pipeline, attribution, territory, CPQ, or GTM-tooling question. Returns cited excerpts with source URLs. Also holds the materials from LeanScale's talks, which people ask for by event name: Updata CEO Summit materials: the deck with speaker notes (The Context Graph & Semantic Layer); Updata CEO Summit materials: GTM agents (11 Claude Code plugins for your CRM); Choosing a CRM: migrate off Salesforce, rebuild in place, or stand up a new org; CRM data hygiene: deduplication, merging duplicates and cleaning up workflow and property tech debt; Discovery call structure, mutual action plans and paid vs free pilots; Which paid advertising channel an early-stage B2B startup should use first; Early-stage outbound: prerequisites, sending domains and deliverability, and what to measure; Founder-led sales to the first sales hire: readiness, profile and why first VP of Sales hires fail; Funnel conversion benchmarks: lead to meeting held to closed-won, win rate and sales cycle; GTM reporting readiness checklist: can your CRM measure conversion, velocity, churn, ARR and revenue recognition?; Lead-to-account matching: approaches, match keys and what goes wrong; New account executive ramp plan: 30-60-90 milestones, certification, call shadowing and deal reviews; Separate pipelines for new business, renewal and expansion: deal types, renewal creation and pilots; Partner program operations: PRM implementation, deal registration and cloud marketplace co-sell; Pipel…
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | How many excerpts to return (default 6). |
| query | string | yes | What you want to know. Natural language works better than keywords. |
| source | string | – | Restrict to one kind of source. Defaults to searching everything. |
No output schema declared.
No examples provided.
search_podcast ~108
Search every episode of The LeanScale Podcast — conversations with CROs, VPs of RevOps, and founders. Returns episode context, frameworks, verbatim quotes with timestamps, and links — including the episode on YouTube when there is a video. Use when someone wants an operator's opinion, a real story, or a quotable line rather than a methodology.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Default 6. |
| query | string | yes | Topic, guest name, company, or idea. |
No output schema declared.
No examples provided.
How do I install the LeanScale GTM Knowledge MCP server?
LeanScale GTM Knowledge is a hosted endpoint at https://mcp.leanscale.team/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 · mcp.leanscale.team
claude mcp add --transport http team-leanscale-gtm-knowledge 'https://mcp.leanscale.team/mcp'
What is the LeanScale GTM Knowledge MCP server?
LeanScale GTM Knowledge is an MCP server listed in the public MCP registry as team.leanscale/gtm-knowledge. GTM operations knowledge: delivery playbooks, field studies, benchmarks and operator interviews. This page covers its hosted endpoint (https://mcp.leanscale.team/mcp).
Is the LeanScale GTM Knowledge MCP server safe to use?
LeanScale GTM Knowledge scores 83 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 LeanScale GTM Knowledge MCP server expose?
LeanScale GTM Knowledge exposes 8 tools: search_leanscale, diagnose_gtm, get_playbook, list_playbooks, get_benchmark, and 3 more. Their descriptions and schemas cost roughly 1,247 tokens of context every time the server is loaded.
Does the LeanScale GTM Knowledge MCP server require authentication?
No. We connected to LeanScale GTM Knowledge without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the LeanScale GTM Knowledge MCP server still maintained?
LeanScale GTM Knowledge 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.