Discovery MCP Server

by peopleanalyst Your server? Claim it

not responding

Discovery is listed as active in the registry but did not answer our last check. It exposes 16 tools.

PeopleAnalyst's free people-analytics feeds: answers, tools, evidence, story and scene catalogs.

The linked repository no longer exists on GitHub — it was deleted or made private.

Uptime history 61 days of history · worst day 0%

61 days agonow

0.0%

Uptime 24h

0 of 92 checks

Tools

read from the server

131 ms

Response time

average over 24h

open, no key

Access

streamable-http

What changed 12

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 9 September 2026. No other catalogue keeps this.

13 Oct a tool description was rewritten get_product_description

27 Sep 2 tool descriptions were rewritten get_brandscripts, get_product_description

27 Sep 2 tools changed the parameters they ask for get_brandscripts, get_product_description

25 Sep a tool disappeared get_membership_offer

24 Sep a tool description was rewritten get_tools

10 Sep a tool description was rewritten list_answers

9 Sep 2 tools appeared get_membership_offer, list_answers

9 Sep a tool changed version2 times that day

and 1 more, back to 9 September 2026

Discovery does not always answer

Over the last week it answered 0.0% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 3 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add discovery --transport http https://peopleanalyst.com/mcp

Settings → Connectors → Add custom connector, then paste this address

https://peopleanalyst.com/mcp

~/.codex/config.toml

[mcp_servers.discovery]
url = "https://peopleanalyst.com/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "discovery": {
      "url": "https://peopleanalyst.com/mcp"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "discovery": {
      "type": "http",
      "url": "https://peopleanalyst.com/mcp"
    }
  }
}

Available tools 16

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

answer

get_answer

Returns one authored /answers page as structured content: question, markdown answer body (short answer, problem frame, evidence, grounded sources), and citations with libraryId or url. Known slugs (33): measure-employee-performance, survey-validity-check, people-analytics-program-maturity, people-analytics-vs-hr-reporting, engagement-survey-vs-listening-diagnostic, people-analytics-tools-compare, beyond-annual-engagement-survey, replace-gut-feel-talent-decisions, ….

answers

list_answers

Returns the full index of authored /answers pages — one entry per slug, with the question and canonical URL. Use this to discover available slugs before calling get_answer.

brandscripts

get_brandscripts

Per-persona StoryBrand arguments for each product. The persona × goal argument layer (SB7-shaped). Stable ?id is globally exact; ?product + ?persona + ?variant selects one exact scoped variant, while ?variant alone remains a compatible filter. Live is the default; ?status=draft|all opts into authoring records with capability readiness kept separate.

canonical

get_canonical_forms

The canonical form vocabulary — the structural primitive. 7 data shapes and the 33 canonical forms they resolve to. The form is why one engine reads compensation, attrition, funnels and survey data without a per-domain rewrite: the domain is in the metric tag, the structure is here. 'oftenMeans' is a labelled heuristic, never a conclusion.

claim

get_claim_warrant

How many works discuss a claim — discourse volume, with the works named. For a construct pair mined from the book corpus: how many distinct works discuss the link, and which ones, with each work's stated rationale. ⚠ This is DISCOURSE, not evidence — book frequency is confounded by publication incentives, fashion and citation cascades, so it is reported as 'discussed in N works' and never as corroboration, confidence, or a score. Single-work claims are returned, labelled as such; corroboration is not a gate. No query returns corpus-level stats including a counting discrepancy we state openly.

insight

get_insight_cards

A pitch rendered as player-ready InsightCards. Serves a named pitch as an ordered InsightCard[] (the cross-site insight-player contract). ?pitch selects the pitch; ?awareness optionally reshapes the sequence for the buyer's awareness state.

library

get_library_ids

Library id export — stable ids for the works homed here. Batch export of library_id rows (id, title, author, year, property tags) for the works that home on peopleanalyst.com. Ids are content-addressed (SHA-256 of normalized title|authors|year) and stable across repos, so a consumer can join to this catalog without string matching. Scoped to works homed here — titles whose canonical home is another property are excluded, matching /library.

marketing

get_marketing_registry

The Pitboss marketing-asset registry (typed cards + personas). Cross-site marketing-asset cards built from the portfolio's brandscripts and proofs, plus the persona set. ?product filters to one product; ?status filters by lifecycle.

peopleanalyst

list_peopleanalyst_feeds

List PeopleAnalyst's free machine-readable feeds and their MCP/REST availability. OpenAPI is also published at https://peopleanalyst.com/openapi.json.

plan

plan_next_data_ask

What data to ask for next, and what it would rule out. The acquisition planner. Given which data-stories are still candidates, returns the single most efficient next question, the full ranked list, and the minimum set of asks that makes every live story testable — split into what can be sent today versus what needs legal review. Ranked by information-per-friction: how evenly an answer splits the live hypothesis set (computed by entropy from the discrimination matrix, never hand-asserted) divided by a cost in which GOVERNANCE outweighs effort. Absent priors all live stories weigh equally, so results reflect structure, not likelihood. GET accepts ?live=, ?have=, ?lack= as comma lists.

product

get_product_description

Bicycle.LLC product descriptions through the stable PeopleAnalyst feed. Versioned, CORS-open descriptions of every product in the portfolio — general positioning plus structured personas, goals, problems, journeys, and associated BrandScripts where the product has that canon. Bicycle.LLC owns the company feed; this stable PA route and MCP tool proxy its validated v1 responses. Pass ?product to filter; live nested journeys are the default and ?status=draft|all opts into authoring records.

scene

get_scene_templates

Falsifiable scene templates — one claim plus what would make it false. The cards a story is told with. Each declares truth conditions the data can falsify, so a claim survives on evidence rather than assertion. Persona relevance is derived from focus (a stated heuristic). Drafts excluded unless ?status=all.

segmentation

run_segmentation

Behavioral segmentation, role discovery, and exemplar matching. Deterministic segmentation over caller-supplied numeric vectors: cluster subjects, discover roles from behaviour + relationship edges, detect emergent roles, or match against exemplars. Structured non-biometric signals only — no audio, video, or affect inference. The caller supplies all data; nothing is retained. Capped at 5,000 rows per request.

situations

get_situations

Demonstration scenarios (discovered → diagnosed → solved). The proof layer paired with brandscripts: concrete situations a product resolves. ?product filters; ?status opts into drafts.

story

get_story_tracks

Pre-authored data-story tracks — the possibility space. Complete data stories: the SB7 argument, the acts and beats that carry it, the branches it forks down, the decision it produces, and the data required to test it. Candidates only — nothing here asserts a story is true of any organisation; that is decided against data. ?persona / ?problem / ?metric / ?slug filter.

tools

get_tools

The PeopleAnalyst tool catalog (corpus-grounded acting tools). Machine-readable catalog of every corpus-grounded acting tool — name, category, what it does, inputs/outputs, concrete use cases, the profile URL, and how to run it (auth-gated REST + MCP). Last production probe (2026-09-23) reported grounded: true. Discovery is open (find + cite the tools); execution is API-key gated. ?category filters by family; ?slug returns one tool.

Tools removed

Tools this server used to expose. Anything built against them stopped working on the day they went.

get_membership_offer

removed 25 Sep 2026

Endpoints

URL	Transport	State	Latency	Checked
https://peopleanalyst.com/mcp	streamable-http	answering	131 ms	3 min ago

Alternatives to Discovery

same job, measured the same way

Neuronsearchlab

by neuronsearchlab

Recommendations, search, catalogue, analytics, and platform admin tools for NeuronSearchLab

552 installs/wk answering

Root Data Public Directory

by rootdata

Public Root Data dental analytics directory for DSOs, dental practices, blog, and FAQ tools.

8 tools answering

Singular

by singular

Marketing intelligence MCP server providing campaign performance data and analytics tools.

answering

Apify Market Intelligence

by timzinin-api

Pay-per-call Apify Store analytics with free MCP discovery and x402 payments.

6 tools answering

SavantoAI

by savantoai

Manage your Savanto store from your AI: catalog, content, prompts, and analytics, by chat.

52 installs/wk answering

Tech Stack Detector — CMS, Framework & CDN with Evidence

by kriton-dev

Detect a website's CMS, framework, analytics, CDN and hosting live, with evidence for each

answering

PromptEden

by yulanventures

Stdio MCP server for PromptEden projects, monitors, answers, and analytics.

46 installs/wk local only

Tech Stack Check

by bkeller-research

Detect a website's CMS, analytics, chat, payments and ad pixels, with evidence and tracking IDs.

answering

Discovery — questions

Answers built from our own checks of this server.

What can Discovery do?

It exposes 16 tools, read directly from the server on our last check. Among them: get_answer, get_brandscripts, get_canonical_forms, get_claim_warrant, get_insight_cards, get_library_ids and 10 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is Discovery working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 0 of 92 checks got a reply (0.0%), average response time 131 ms. The bar chart above shows every period we have measured.

Did Discovery ever remove tools?

Yes. get_membership_offer is no longer exposed — we recorded the date each one disappeared. A tool vanishing usually means a breaking change for anything that depended on it.

Is Discovery still maintained?

The linked repository no longer exists on GitHub — it was deleted or made private. We show this because it changes what you can expect: an unmaintained server may keep answering for months and then stop without warning.

The registry lists Discovery as active — why does it not respond?

The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.

How do I connect Discovery?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Discovery need an API key?

No. Discovery completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 16 of them are readable on this page. This is what we observed, not what the docs claim.