Keystone Harness Manager — the end-to-end harness manager for any project. MCP server that owns the full lifecycle: scaffold, sensors, actions, playbooks, skills, cascade verify, and forward-only shipped-template patches.
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"keystone-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# keystone-mcp — Keystone Harness Manager The **Keystone Harness Manager** is the end-to-end harness manager for any project. It's a single MCP server (`keystone-mcp` on PyPI) that owns the full lifecycle of a project harness: - scaffold + materialize a shipped template tree under `.keystone/harness/` - broker rules, reasoning, skills, and commands from any external source (markdown, folder, repo, GitHub, Confluence, Notion, Jira, Linear, Slack) - run computational and inferential sensors as blocking checks - resolve a cascade across external sources and the project layer (canonical locks, required gaps, conflicts, unreachable items) - apply forward-only shipped-template patches as the manager evolves - drive Learning + Pruning flywheels via shipped playbooks and skills - overlay the agent menu file (CLAUDE.md, AGENTS.md, …) without clobbering any pre-existing user content The agent treats each retrieved payload differently: - **rules** — constraints to obey (`must` / `should` / `may`) - **reasoning** — background facts and intent - **skills** — procedural how-to knowledge (multi-step playbooks) - **commands** — canned invocations (shell commands, scripts, named recipes) Instead of cramming organizational context into every system prompt, the agent reads `keystone://context/{topic}` resources or calls `keystone_get_context(topic)` and the broker fans the request out to the right backing source. ## Status **0.2.0.** Pre-1.0; the package name on PyPI stays `keystone-mcp`. Phases 1–28 shipped per [`FEATURE_PARITY_PLAN.md`](./FEATURE_PARITY_PLAN.md) and [`CHANGELOG.md`](./CHANGELOG.md). 361 tests pass. ## Adapters Source types (`type:` in `.keystone/context.yaml`): | Type | Auth | What it emits | | --- | --- | --- | | `markdown` | none (repo-local) | one markdown file per query — rules / reasoning / skills / commands | | `folder` | none (repo-local) | walks a local directory tree of markdown. Globs (`include` / `exclude`) | | `repo` | (optional, dep…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.