Interrogez ce corpus nativement depuis n'importe quel agent IA
La plateforme de connaissances Santismm est exposée en tant que serveur MCP public via Streamable HTTP. Les ressources lisent un contenu complet et citable ; 30 outils permettent de rechercher, naviguer et exécuter cinq domaines clés, des essais de première main, des Labs, l'Atlas homérique et le registre des affirmations épistémiques.
Streamable HTTP (JSON-RPC)
Streamable HTTP sans état : pas de session, pas de clé API, rien à installer. Le point de terminaison dessert les deux ères du protocole, de sorte qu'un client existant qui envoie initialize continue de fonctionner exactement comme avant et qu'aucune de vos configurations n'a besoin d'être modifiée.
Détails du protocole — uniquement si vous utilisez la révision 2026-07-28 ou si vous effectuez un appel depuis un navigateur
Sur la révision 2026-07-28, il n'y a pas de négociation initialize. Chaque requête se déclare avec MCP-Protocol-Version: 2026-07-28, Mcp-Method et Mcp-Name pour un appel d'outil. Elle contient également une enveloppe params._meta avec io.modelcontextprotocol/protocolVersion, .../clientInfo et .../clientCapabilities ; un objet vide est une valeur de capacités valide, mais la clé est requise et son absence renvoie une erreur 400. Les en-têtes et le corps sont vérifiés mutuellement, de sorte qu'une requête dont les en-têtes ne correspondent pas au corps est refusée plutôt que soumise à une interprétation.
Les clients de type navigateur ne sont acceptés que depuis santismm.com, www.santismm.com et localhost ; tout autre Origin reçoit un 403 avant même que le transport ne soit sollicité. Les en-têtes CORS restent ouverts à dessein, afin qu'une page rejetée puisse lire ce code 403 au lieu d'une erreur réseau opaque. Les clients autres que les navigateurs n'envoient pas d'en-tête Origin et ne sont pas affectés.
Lire du contenu sans exécuter d'outil
Utilisez resources/list et resources/templates/list pour découvrir les adresses santismm:// stables, puis resources/read pour obtenir le document JSON complet. Chaque charge utile conserve son URL publique canonical_url pour citation. Les modèles fédérés d'Articles et de Labs restent disponibles même si leur catalogue distant est temporairement indisponible.
santismm://overviewRead the corpus map, licences, languages, extensions and bulk-ingest URLs.
santismm://knowledge/{locale}/{slug}Read one complete knowledge unit, localised and carrying provenance plus canonical citation URLs.
santismm://patterns/{locale}/{slug}Read one complete patterns unit, localised and carrying provenance plus canonical citation URLs.
santismm://architectures/{locale}/{slug}Read one complete architectures unit, localised and carrying provenance plus canonical citation URLs.
santismm://governance/{locale}/{slug}Read one complete governance unit, localised and carrying provenance plus canonical citation URLs.
santismm://handbook/{locale}/{id}Read one complete Handbook chapter by stable id or slug and locale.
santismm://articles/{slug}Read one complete first-party essay from the canonical Articles API.
santismm://labs/{slug}Read one calculator, converter, experiment or educational-game definition without executing it.
santismm://homeric/{kind}/{locale}/{slug}Read one place, episode or route with competing identifications and rubric evidence.
santismm://claims/{locale}/{id}Read one load-bearing claim, including limits and falsification criteria.
Rechercher, naviguer et calculer
Utilisez des outils lorsque l'agent a besoin de routage, de recherche classée, de parcours de graphe ou d'exécution déterministe. Les résultats des outils renvoient vers l'URI de la ressource correspondante chaque fois que le résultat est un contenu lisible.
get_overviewGet the complete MCP map — start here. Returns the five-domain core plus the separate Article, Labs, Homeric Atlas and claim-registry surfaces, with their tools, identifiers, citation rules, languages, licence and bulk-ingest URLs.
search_allSearch the core corpus, first-party essays, executable Labs, epistemic claims and the Homeric Atlas in one call. Use this first when a natural-language question might require a calculation, a long-form essay or a claim audit rather than only a core knowledge unit. Results name the next tool to call; calculator-shaped questions are routed toward Labs.
list_knowledgeList 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.
get_knowledgeGet 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.
list_patternsList 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.
get_patternGet 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.
list_architecturesList 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.
get_architectureGet 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.
list_governanceList 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.
get_governanceGet 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.
list_handbookList 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.
get_handbookGet 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.
searchRanked 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.
list_articlesList every long-form essay published on articles.santismm.com, with language, dates, topics and citable canonical URLs. Use this to browse the essay catalogue; use search_articles when you have a topic rather than a slug.
get_articleGet one complete essay by slug, including its clean Markdown-like body, metadata, licence context and canonical URL. Use this after list_articles or search_articles has returned the slug you need.
search_articlesRanked, accent-insensitive full-text search over every first-party essay, including titles, summaries, topics and bodies. Use this when you need long-form analysis about a topic; follow with get_article for the complete essay.
list_labsList every SANTISMM Lab with its inputs, outputs, assumptions, formulas and citation URL. Use this to discover interactive and machine-readable tools; filter by kind when the user specifically asks for a calculator, converter, experiment or educational game.
get_labGet one Lab by slug, including formulas, assumptions, related SANTISMM content and its executable endpoint when one exists. Use this after list_labs or search_all; use the named calculate_* tool rather than reimplementing a published formula.
calculate_agent_economicsCalculate monthly operating cost, cost per verified outcome, manual baseline, savings, ROI and break-even success rate from explicit assumptions. Use this for an agent business case or scenario comparison; keep every monetary input in the same currency and cite the returned canonical_url.
calculate_evaluation_sample_sizeCalculate two different samples: how many independent evaluations are needed to detect at least one failure, and how many are needed to estimate its rate at a chosen margin. Use this when a user asks how many tests are enough; do not interpret zero observed failures as proof of zero risk.
calculate_human_supervision_capacityCalculate review and escalation workload, required FTE, available headroom or backlog, monthly labour cost and sustainable case volume. Use this before production rollout to test whether the stated human-oversight model is operationally credible; the result uses averages and is not a queueing simulation.
get_relatedTraverse 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.
list_homeric_placesList every place in the Homeric Atlas with its identification class, its confidence score and how many competing identifications it carries. Use this to browse the atlas; use get_homeric_place once you have a slug. Identification classes: accepted (an excavated site with consensus), plausible (a real place, contested), speculative (a minority reading or a later tradition), mythical (the poem places it outside the mappable world). Confidence is a published 0-12 rubric - textual, archaeological, scholarly and geographic, 0-3 each - and is an editorial judgement, not a probability.
get_homeric_placeGet one place by slug: every identification proposed for it, each with its own coordinates, class, 0-12 rubric and sources, plus the attested passages. Use this when you need to weigh the evidence for a location, or to cite it; a place the poem does not locate carries no coordinates at all.
list_homeric_episodesList every episode of the Iliad and the Odyssey held in the atlas, in reading order, with its passage, the places it involves and how firmly it can be located. Use this to find the episode you want; use get_homeric_episode for its theories and sources.
get_homeric_episodeGet one episode by slug: the passage, the narrative, the competing theories about where it happened (each with its proponent and sources), the confidence rubric and the FAQs. Use this when the question is where an episode took place and who argued for it.
list_homeric_routesList the reconstructed itineraries (the nostos of Odysseus and the others), each with its rival reconstructions scored separately. Use this to see which voyages the atlas reconstructs before fetching one.
get_homeric_routeGet one route by slug: each reconstruction variant with its ordered stops, the hypothesis chosen at each stop, its confidence rubric and its sources. Use this to compare rival reconstructions of a voyage: they are returned side by side rather than merged.
list_claimsList the load-bearing claims of the corpus, each tagged as observed_fact, industry_synthesis, santismm_thesis or strategic_hypothesis, with its confidence and the units it underpins. Use this before quoting the handbook to know whether a statement is evidence, a reading of the industry, or a position taken. Filter by claim_type to get only what is checkable.
get_claimGet one claim by id (HE-CLAIM-001) or slug: the statement, what it rests on, its structured sources, and — always present — what it does NOT establish and the observation that would retire it. Use this to cite the corpus honestly, or to check whether a result you have just measured confirms or falsifies a claim it makes.
Ajoutez-le à votre client MCP
La plupart des clients MCP (Claude Desktop, extensions d'IDE, agents personnalisés) acceptent un serveur MCP HTTP dans leur configuration. Collez :
{
"mcpServers": {
"santismm-knowledge": {
"type": "http",
"url": "https://santismm.com/mcp"
}
}
}Trois façons d'accéder au même corpus
Le point de terminaison hébergé ne nécessite aucune installation. Les deux packages exécutent le même serveur localement via stdio — la différence réside dans l'emplacement du corpus, ce qui détermine celui dont vous avez besoin.
| Méthode | Corpus | Fraîcheur |
|---|---|---|
| https://santismm.com/mcp | distant | toujours à jour |
| npx santismm-knowledge-mcp | noyau intégré ; Articles et Labs en ligne | figé au moment de la publication |
| uvx santismm-knowledge-mcp | aucun — sert de proxy vers le point de terminaison | toujours à jour |
Le package npm est volontairement un instantané, il peut donc être en retard. C'est indiqué ainsi : get_overview signale la date de l'unité la plus récente de la copie qui répond, et un not_found la répète, afin qu'un agent puisse distinguer un identifiant incorrect d'un corpus plus ancien que ce qu'il demande.
Cinq domaines clés : connaissances, modèles, architectures, gouvernance et le Harness Engineering Handbook. search_all oriente les questions en langage naturel à travers le noyau, les Articles, les Labs exécutables et les affirmations ; des outils dédiés exposent l'Atlas homérique.
Parcourez les liens avec get_related, le même graphe qui sous-tend /api/graph.json.
Chaque unité porte une provenance de type Evidence-First (niveau de preuve, confiance, types de sources).
Chaque outil déclare un outputSchema et renvoie un structuredContent validé, de sorte que les résultats arrivent sous forme de données typées — le JSON sérialisé reste dans content pour les clients plus anciens.
Le même serveur, ailleurs
Ce serveur est une entité unique dotée de plusieurs portes d'entrée. Chacune d'elles correspond au même point de terminaison et au même corpus, déclarés sous la forme sameAs dans les métadonnées de la page afin qu'un robot d'indexation puisse les réconcilier au lieu de comptabiliser des projets distincts.
Vous n'utilisez pas MCP ?
Le corpus principal et les jeux de données associés sont également publiés au format texte brut et JSON. Chaque point d'entrée direct annoncé par le manifeste de découverte en direct est accessible depuis Pour les agents IA: