mcpbeat Sign in

Discovery MCP Server

by peopleanalyst Your server? Claim it
answering

Discovery is answering right now. Last checked 9 min ago. It exposes 17 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 10 days of history · worst day 70%
10 days agonow
97.8%
Uptime 24h
89 of 91 checks
17
Tools
read from the server
307 ms
Response time
average over 24h
open, no key
Access
streamable-http

What changed 5

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

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 87.8% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Three servers free · no card

Connect this server

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

run in your terminal
claude mcp add discovery --transport http https://peopleanalyst.com/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "discovery": {
      "url": "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
{
  "mcpServers": {
    "discovery": {
      "url": "https://peopleanalyst.com/mcp"
    }
  }
}

Available tools 17

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-level argument layer (SB7-shaped): the major problem solved for a persona and what the solution looks like. ?product / ?persona filter; ?status opts into drafts.
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.
membership
get_membership_offer
Returns the people analytics chapter of the Bicycle Cooperative membership offer: five options (enterprise member, practitioner member, worker, practitioner rent, enterprise rent) with chapter substitution applied and this front's join URL.
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
Machine-readable description of each PeopleAnalyst product. Versioned, CORS-open descriptions of every product in the portfolio — name, category, oneLiner, problemFrames, capabilities, beachheads, whenNotToUse (honest disqualifiers), canonicalUrls, relatedProducts. Assembled from canon. Pass ?product to filter.
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 (each answer reports its grounding). Machine-readable catalog of acting tools — name, category, what it does, inputs/outputs, concrete use cases, the profile URL, and how to run it (auth-gated REST + MCP). Each Bicycle answer reports provenance.grounding. Production currently reports grounded: false (HO-2512); approach strings describe the designed product, not the last production run. Discovery is open (find + cite the tools); execution is API-key gated. ?category filters by family; ?slug returns one tool.

Endpoints

URLTransportStateLatencyChecked
https://peopleanalyst.com/mcp streamable-http answering 279 ms 9 min ago

Alternatives to Discovery

same job, measured the same way
Neuronsearchlab
by neuronsearchlab

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

140 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.

23 installs/wk answering
Asterpay
by timolein74

EUR settlement for AI agents. Trust scoring, market data, crypto analytics. 16 free tools.

15 installs/wk local only
Sputnikx Market
by drivenbymyai-max

EU trade analytics, product catalog, orders, and heating fuel calculator for AI agents.

local only
Stride20k x402 Data Gateway
by marysbrain

x402 analytics feed + 20+ pay-per-call agent tools over x402 (data, LLM, risk), no accounts.

64 installs/wk local only

Discovery — questions

Answers built from our own checks of this server.

What can Discovery do?
It exposes 17 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 11 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 89 of 91 checks got a reply (97.8%), average response time 307 ms. The bar chart above shows every period we have measured.
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.
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 with the file path 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 17 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Discovery?
It answers our handshake in 307 ms on average, which is faster than 49% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.