mcp server
Santismm Knowledge — Harness Engineering, Agentic AI & Governance
Search harness engineering, agentic AI patterns, architectures, governance and agent taxonomy.
Description as published by the maintainer. Source
- version 0.2.1
- active
- retrieval
active — Most recent push to the repository was 2026-08-02. Dashed tags are derived by ZBS Index from the published description, not stated by the maintainer.
What this server can do
13 functions, named and described by the server itself. Parameter names are shown because they say more about what a function does than its name usually does.
get_architecture(slug, locale)- Get one reference architecture by slug (includes the request flow, reference scenario, KPIs, cost & scaling, and the patterns/knowledge it composes). Use this once `search` or `list_architectures` has given you a slug. Required: slug.
get_governance(slug, locale)- Get one AI governance unit by slug (includes scope, key requirements, implementable controls, a checklist and common pitfalls). Use this once `search` or `list_governance` has given you a slug. Required: slug.
get_handbook(id, locale)- Get one Harness Engineering Handbook chapter, by id (e.g. 'HRN-001') or slug. Returns the full Markdown body plus its provenance and related ids. Use this once `search` or `list_handbook` has given you an id. Required: id.
get_knowledge(slug, locale)- Get one knowledge unit by slug. Returns the full entry, or a single-locale body if locale is given. Use this once `search` or `list_knowledge` has given you a slug. Required: slug.
get_overview- Get the corpus map — start here. Returns every domain (knowledge, patterns, architectures, governance and the Harness Engineering Handbook) with what it holds, the categories inside it, which tool retrieves a unit and what identifier that tool expects, plus the languages, licence and bulk-ingest URLs. One call is enough to know exactly where to go next.
get_pattern(slug, locale)- Get one Enterprise AI pattern by slug (includes problem, solution, KPIs, failure modes, lessons). Use this once `search` or `list_patterns` has given you a slug. Required: slug.
get_related(slug, domain, locale)- Traverse the knowledge graph: given a unit, return its neighbours — the units it links to (outgoing) and the units that reference it (incoming), each with the relationship type. Use this after a `get_*` call to widen an answer with adjacent units. Required: domain, slug.
list_architectures(locale)- List all reference architectures (end-to-end enterprise agentic blueprints) with id, slug, category, name, summary and provenance. Use this to browse the blueprints; use `search` when you have a use case rather than a name.
list_governance(locale)- List all AI governance units (regulations, standards, frameworks, playbooks — EU AI Act, ISO 42001, NIST AI RMF, agentic checklist) with id, slug, category, name and summary. Use this to browse the regulations and standards; use `search` for an obligation or control.
list_handbook(locale)- List the Harness Engineering Handbook chapters (HRN-001…): the canonical long-form corpus on harness engineering — definition, history, taxonomy, principles, memory, observability, evaluation, governance, planning, orchestration, security, case studies, glossary and bibliography. Use this to see the chapter map; use `search` when you have a topic rather than a chapter.
list_knowledge(locale)- List all knowledge units (concepts on agentic & enterprise AI) with slug, category, title, summary and Evidence-First provenance. Use this to browse the domain; use `search` when you have a question rather than a slug.
list_patterns(locale)- List all Enterprise AI patterns (reusable agentic design patterns) with slug, category, name, summary and provenance. Use this to browse the catalogue; use `search` when you are looking for a pattern that solves a problem.
search(limit, query, locale, domains)- Ranked keyword search across the whole corpus (knowledge, patterns, architectures, governance and the handbook). Matches every language and ignores accents, so query in the user's own words. Each hit carries a relevance score and the fields it matched; follow up with the matching get_* tool for full detail. Use this before any `get_*` tool whenever you have a question rather than an identifier. Required: query.
Last successful function declaration observed on . Source: https://santismm.com/mcp. We list what the server declared; we do not call any of these functions.
Endpoint status observed on . Source: https://santismm.com/mcp.
Signals
These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.
| Signal | Value | What it measures | Window | Observed | Source |
|---|---|---|---|---|---|
| GitHub stars | 0 | Number of GitHub accounts that bookmarked this repository since it was created. It is a bookmark count, not installs, not active users and not quality. | cumulative, all time | GitHub | |
| Last commit | 2026-08-02 | Date of the most recent push to any branch. This is the strongest cheap indicator of whether the project is still maintained. | point in time | GitHub | |
| Open issues | 0 | Open issues plus open pull requests, as GitHub counts them together. A high number can mean an active project or an abandoned one. | as of fetch | GitHub | |
| Latest published version | 0.2.1 | Latest version string the maintainer published to the registry. | as of fetch | Model Context Protocol | |
| Registry record last updated | 2026-08-02 | When the registry record was last updated by its maintainer. | point in time | Model Context Protocol | |
| First listed in the MCP Registry | 2026-08-02 | Date this server was first published to the official MCP Registry. Not a usage or quality measure. | point in time | Model Context Protocol | |
| repository status | active | The repository exists on GitHub and is not archived. This says nothing about how recently it was worked on. | as of fetch | GitHub | |
| mcp tools declared | 13 tools | Number of functions the server itself declared when asked to list them. This is what the server offers an agent, not a measure of how well any of them work. | as of probe | santismm.com | |
| mcp endpoint status | ok | The server listed 13 functions when asked. | as of probe | santismm.com |
Where to get it
Related, by what their authors tagged them
-
aden-hive-hive-browser-edge-cases
— last commit 2026-05-29, shares harness-engineering
SOP for debugging browser automation failures on complex websites. Use when browser tools fail on specific sites like L…
-
aden-hive-hive-hive-browser-automation
— last commit 2026-05-29, shares harness-engineering
Required before any browser_* tool call. Teaches the screenshot + browser_click_coordinate workflow that reaches shadow…
-
aden-hive-hive-hive-chart-creation-foundations
— last commit 2026-05-29, shares harness-engineering
Required reading whenever any chart_* tool is available. Teaches the one-tool embedding contract (call chart_render → l…
-
aden-hive-hive-hive-colony-progress-tracker
— last commit 2026-05-29, shares harness-engineering
Claim tasks, record step progress, and verify SOP gates in the colony SQLite queue. Applies when your spawn message inc…
-
aden-hive-hive-hive-context-preservation
— last commit 2026-05-29, shares harness-engineering
Proactively extract critical values from tool results into working notes before automatic context pruning destroys them.
-
aden-hive-hive-hive-error-recovery
— last commit 2026-05-29, shares harness-engineering
Follow a structured recovery decision tree when tool calls fail instead of blindly retrying or giving up.
-
aden-hive-hive-hive-linkedin-automation
— last commit 2026-05-29, shares harness-engineering
Read before automating LinkedIn with browser_* tools. LinkedIn combines shadow DOM (#interop-outlet), strict Trusted Ty…
-
aden-hive-hive-hive-note-taking
— last commit 2026-05-29, shares harness-engineering
Maintain a free-form scratchpad of decisions, extracted values, and open questions so context pruning doesn't lose anyt…
-
aden-hive-hive-hive-quality-monitor
— last commit 2026-05-29, shares harness-engineering
Periodically self-assess output quality to catch degradation before the judge does.
-
aden-hive-hive-hive-terminal-tools-foundations
— last commit 2026-05-29, shares harness-engineering
Required reading whenever any shell_* tool is available. Teaches the foreground/background dichotomy (terminal_exec aut…
These share tags the maintainers applied themselves, such as harness-engineering. Common tags like "mcp" or "ai" are ignored for this: agreeing with six hundred other projects is not a similarity.
This is not a recommendation and not a test result. It is a map of what the authors said their work is about.
How the author describes it
Topics the maintainer set on GitHub: agentic-ai, ai-governance, harness-engineering, knowledge-base, mcp, mcp-server, model-context-protocol.
This record as data
Every field on this page, with its source and observation date, is in the catalog JSON. Fetch the whole kind at once instead of parsing this HTML.
GET /api/v1/entries/mcp_server.json