Skip to content

LeanScale GTM Knowledge MCP server

team.leanscale/gtm-knowledgeleanscale.teamstreamable-httpv0.1.0Scanned

GTM operations knowledge: delivery playbooks, field studies, benchmarks and operator interviews.

8 tools: 1 change things and 7 only read.

Tools: 0 delete, 0 irreversible, 1 write, 7 read.
  • Reads private data · 2
  • Reads text others write · 1
  • Can send data out · 0
  • 1 finding

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here changes things. Govern it.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the LeanScale GTM Knowledge MCP server can do

The LeanScale GTM Knowledge MCP server is published by leanscale.team, a domain the MCP Registry verified. It has 8 tools. It can create or change data (1 tool: about_leanscale), but cannot delete data. 7 tools only read.

2 tools read private data (search_leanscale and search_podcast); 1 tool brings in text other people can write (search_podcast).

The fixed checks matched 1 finding (long-description). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in, and its tools changed 2 times since Anlyon Radar first saw them.

Last scanned Nov 18, 2026, version 0.1.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

8 tools

Changes things 1Claude Code: ask
  • about_leanscaleWhat LeanScale is, what's in this knowledge base, and how to work with them.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.
Only reads 7Show 7 read-only tools
  • diagnose_gtmDescribe 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.No findings

    Why it is in this group

    • The description's first verb is "describe": a word for reading.
    Description, as the server wrote it
    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?'
  • get_benchmarkGet 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.No findings

    Why it is in this group

    • The name "get_benchmark" says "get": a word for reading.
    Description, as the server wrote it
    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.
  • get_case_studyRetrieve LeanScale customer case studies — the problem the company had and how it was solved.No findings

    Why it is in this group

    • The name "get_case_study" says "get": a word for reading.
    Description, as the server wrote it
    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.
  • get_playbookRetrieve a LeanScale delivery playbook in full, or one named section of it.No findings

    Why it is in this group

    • The name "get_playbook" says "get": a word for reading.
    Description, as the server wrote it
    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.
  • list_playbooksList every available LeanScale delivery playbook with its category and section headings.No findings

    Why it is in this group

    • The name "list_playbooks" says "list": a word for reading.
    Description, as the server wrote it
    List every available LeanScale delivery playbook with its category and section headings.
  • search_leanscaleSearch everything LeanScale knows: 14 GTM delivery playbooks, 7 proprietary field studies, 151 podcast episodes with operators and executives, 75 customer case studies (anonymized …Reads private data1 finding

    Why it is in this group

    • The name "search_leanscale" says "search": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "search" and "doc": it reads documents.

    Findings

    • Info

      The description is 2,823 characters long, over the 2,000 this check looks for.

      Matched text

      description ends: "...The Context Graph & Semantic Layer. Pass source:"resource" to search only those."

      What this check looks for
    Description, as the server wrote it
    Search everything LeanScale knows: 14 GTM delivery playbooks, 7 proprietary field studies, 151 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 and health audit: deduplication, lead status, task hygiene, unused fields and admin permissions; Discovery call structure, mutual action plans and paid vs free pilots; Documenting existing Salesforce flows and automation: inventory, flowcharts per object, and flagging deactivated automation; 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; Lifecycle stage timestamps and recycled MQLs: never regress the stage, re-enter with dated fields; Marketing nurture email: sending from a subdomain vs a separate domain, and protecting deliverability; 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; Pipeline stage definitions, exit criteria and required fields per stage; How to build pipeline when cold outreach stops working; Selling into a limited TAM: fintech go-to-market for banks and credit unions; Speed to lead: definition, start and end timestamps, business hours, and median vs average; Updata CEO Summit materials: metric definitions worksheet (40 GTM definitions); Updata CEO Summit materials — The Context Graph & Semantic Layer. Pass source:"resource" to search only those.
  • search_podcastSearch every episode of The LeanScale Podcast — conversations with CROs, VPs of RevOps, and founders.Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "search_podcast" says "search": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "search" and "conversation": it reads messages.
    • untrusted-inputThe description's first sentence says "search" and "conversation": it reads messages, which other people can write.
    Description, as the server wrote it
    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.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.

Reads private data2
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write1
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:19 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
1
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 1 tool that changes things (1 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://mcp.leanscale.team/mcp: tools/list returned 8 tools to an anonymous client, including about_leanscale (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

1 info
  • The description is 2,823 characters long, over the 2,000 this check looks for.

    Matched text

    description ends: "...The Context Graph & Semantic Layer. Pass source:"resource" to search only those."

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools1 changed.~1 changedView diff
  2. Tools1 changed.~1 changedView diff

Install

Pinned to version 0.1.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http gtm-knowledge https://mcp.leanscale.team/mcp
claude mcp add --transport http gtm-knowledge https://mcp.leanscale.team/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__gtm-knowledge__search_leanscale",
      "mcp__gtm-knowledge__diagnose_gtm",
      "mcp__gtm-knowledge__get_playbook",
      "mcp__gtm-knowledge__list_playbooks",
      "mcp__gtm-knowledge__get_benchmark",
      "mcp__gtm-knowledge__search_podcast",
      "mcp__gtm-knowledge__get_case_study"
    ],
    "ask": [
      "mcp__gtm-knowledge__about_leanscale"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as gtm-knowledge. Review it before you use it.

Capability tags behind 2 rules
  • mcp__gtm-knowledge__search_leanscale private-data
  • mcp__gtm-knowledge__search_podcast private-data, untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/team.leanscale/gtm-knowledge/verify?hash=84e786b0ef780c5d53380c4f5ac514495ffe970a9af518edf7550d69318934ab" | jq -e '.changed == false'

Pinned hash 84e786b0ef78, from Nov 18, 2026, 08:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/team.leanscale/gtm-knowledge/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for team.leanscale/gtm-knowledge
[![Anlyon Radar](https://radar.anlyon.com/badge/team.leanscale/gtm-knowledge.svg)](https://radar.anlyon.com/servers/team.leanscale/gtm-knowledge)

Source: MCP Registry · repository. Synced Oct 21, 2026, 18:55 UTC.

LeanScale GTM Knowledge MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the LeanScale GTM Knowledge MCP server safe?

No scan can promise that. What its definitions show: 8 tools, 1 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the LeanScale GTM Knowledge MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the LeanScale GTM Knowledge MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the LeanScale GTM Knowledge MCP server have?

8 tools: 1 write, 7 read. about_leanscale, search_leanscale, diagnose_gtm, get_playbook, list_playbooks, get_benchmark, search_podcast and get_case_study.

Does the LeanScale GTM Knowledge MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the LeanScale GTM Knowledge MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the LeanScale GTM Knowledge MCP server changed its tools?

Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 18, 2026. Every change is on this page and in its Atom feed.