Local MCP · Qualitative proof
A buyer wants to know whether the starter kit can be inspected without waiting for a hosted account.
evidence terminal
$ node mcp/local-server.mjs --self-test {"ok": true} $ node mcp/smoke.mjs tools/list + representative calls passed HERMES case-study frame
A reviewer should be able to answer seven things before opening the JSON export: what decision is in front of them, what changed against a cold start, which row carries the claim, where the value appears, what source trail exists, what purchase decision it informs, and what the case does not prove.
A buyer wants to know whether the starter kit can be inspected without waiting for a hosted account.
The buyer must trust a roadmap claim before they can inspect how project context becomes available to tools.
The extracted archive can answer health, search, context read, proof index, lint, and diagnostics calls from local files.
Hosted identity, payment operations, service visibility, and plan changes belong to the Phase 2 hosted service.
Proof row
The local inspection path reads extracted starter-kit files and does not require hosted authentication.
Supports the first-dollar starter-kit claim that buyers can inspect locally before the hosted service ships.
Evidence room
This is the public review surface for the case. Each row names the observation, the evidence values it stands on, the source trail, the boundary, and the matching structured entry in the evidence export.
A source trail is not always a raw public artifact. Public projection means the source has been redrawn or summarized; retained source means it is named for audit but withheld until redaction clears.
Public evidence excerpts
These excerpts are the public bridge between retained raw sources and the evidence table below. Each one says what was preserved, what was redacted, and which evidence rows it supports.
local-tool-contract-excerpt The local contract exposes six tools: health, search, context read, proof index, lint, and diagnostics.
offline-first-boundary-excerpt Local inspection reads the extracted starter-kit files and does not require a hosted account.
Claim under review
The launch offer is not blocked on hosted infrastructure. The local MCP proves the starter kit can be inspected from the same archive a buyer receives.
evidence_facts[0] source-01-local-mcp-readme Local MCP README starter-kit docs · public projection source-02-mcp-manifest MCP manifest machine-readable contract · public projection source-03-local-server Local server starter-kit runtime · public projection source-04-smoke-command Smoke command verification script · public projection The local server works against extracted kit files only.
evidence_facts[1] Hosted identity, payment operations, service visibility, and plan changes belong to the Phase 2 hosted service.
evidence_facts[2] Smoke tests prove startup and representative calls, not full hosted account behavior.
Evidence values
Source trail
source-01-local-mcp-readme Local MCP README starter-kit docs · public projection source-02-mcp-manifest MCP manifest machine-readable contract · public projection source-03-local-server Local server starter-kit runtime · public projection source-04-smoke-command Smoke command verification script · public projection Evidence status mix
Metrics
Source artifacts
Case quality review
This is a cold-review rubric, not a sales claim. It checks whether the case can be understood, inspected, bounded, and acted on.
A reviewer gets the situation, contrast, and buyer decision without reading the JSON.
The case exposes proof rows, values, source handles, and excerpts before the JSON export.
The page names what the case proves and what it does not prove.
The route uses visuals, storyboards, or surface frames to break the proof into inspectable layers.
The proof sends the buyer to an evidence room, artifact link, pricing path, or local run.
Cold-audience clarity: Tighten the opening latch or before/after language when the case still needs explanation.
Open case evidenceEvidence docket
Evidence Flow
Each case has to survive the same path: starting condition, system-backed change, visible result, retained evidence, stated limitation, and a next action.
Local MCP runbook
This is the purchase proof path for the starter kit: inspect the archive, run the local MCP smoke, read the bundled proof index, and see exactly where the hosted service begins later.
Command path
cd scaffold && pnpm install pnpm dev node mcp/local-server.mjs --self-test node mcp/smoke.mjs Tool surface
kbpd.health local:health Check whether the extracted starter-kit paths are readable.
kbpd.search context:search Search local scaffold, instance, and kit text files.
kbpd.read_context context:read Read a relative text file from the extracted starter kit.
kbpd.proof_index proof:read Read the bundled public Proof Studio evidence index.
kbpd.lint kit:lint Scan public outputs and kit text for private paths, ticket keys, and forbidden vocabulary.
kbpd.diagnostics kit:diagnose Summarize local MCP configuration and available tools.
Client config
{
"mcpServers": {
"kbpd-local": {
"command": "node",
"args": ["/absolute/path/to/kbpd-starter-kit/mcp/local-server.mjs"],
"env": {
"KBPD_KIT_ROOT": "/absolute/path/to/kbpd-starter-kit"
}
}
}
}Privacy boundary
The local server exits non-zero if the kit root, scaffold, instance, guide, MCP directory, local server, or smoke script is missing.
The manifest and smoke path agree on the exposed local tools, including proof-index access for reviewable evidence.
The local server reads inside the extracted kit root and does not require a subscription entitlement.
The starter kit includes the hosted-service checklist for review, but sale waits for 9 customer-control gates.
Hosted contract
The kit includes mcp/hosted-control-plane.contract.json so a technical buyer can
inspect the planned hosted-service checklist before treating it as a current entitlement.
Claude Desktop
The local Claude Desktop Extension package is source-built around the same read-only MCP server. It points Claude at the extracted starter kit; it is not hosted Claude access.
kbpd-local-starter-kit.mcpb Keep the downloaded starter-kit folder on your machine.
Import the MCPB bundle into Claude Desktop when the buyer package includes it.
Select the folder that contains START_HERE.md, scaffold/, instance/, and mcp/.
Use health and proof-index first, then search, read-context, lint, and diagnostics.
healthsearchread_contextproof_indexlintdiagnostics Already proven
Remaining gate
Not included yet
Claim
The launch offer is not blocked on hosted infrastructure. The local MCP proves the starter kit can be inspected from the same archive a buyer receives.
Before / after
Before · account-gated access
The buyer must trust a roadmap claim before they can inspect how project context becomes available to tools.
Wait for hosted access, then decide whether the local artifact has enough context to evaluate.
After · offline-first MCP surface
The extracted archive can answer health, search, context read, proof index, lint, and diagnostics calls from local files.
Run the local server from the extracted archive or the Docker image and inspect the tools before hosted auth exists.
Evidence
Run metadata
Metrics
Source artifacts
Limitations
Next