Model Context Protocol (MCP) server for Evidentia — exposes gap analysis, risk generation, explanation, and OSCAL emit to MCP-aware AI clients (Claude Desktop, Claude Code, ChatGPT, etc.)
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":"evidentia-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.
# evidentia-mcp Model Context Protocol server for Evidentia. It exposes 15 tools for catalog reads, gap analysis, continuous monitoring, local evidence ingestion and artifact verification. ## Quick start ```bash pip install evidentia[mcp] evidentia mcp doctor evidentia mcp serve ``` The default transport is stdio. HTTP and SSE are also supported. For bind settings, client configuration and scope registries, see [MCP client setup](../../docs/wiki/2-guides/mcp-client-setup.md). ## Tool surface | Tool | Purpose | |---|---| | `list_frameworks` | List catalog metadata | | `get_control` | Read one catalog control | | `gap_analyze` | Analyze a local inventory | | `gap_diff` | Compare gap reports | | `conmon_list_cadences` | List continuous-monitoring cadences | | `conmon_next_due` | Calculate a cadence due date | | `conmon_check_state` | Read cadence state | | `conmon_health` | Report cadence health | | `gap_analyze_sarif` | Emit gap results as SARIF | | `collect_ocsf` | Ingest a local OCSF file | | `tprm_vendor_list` | List local vendor records | | `poam_list` | List local POA&M records | | `verify_signed_artifact` | Verify an Evidentia signed artifact | | `conmon_series` | Read a cadence evidence series | | `get_catalog_native` | Read a validated native catalog bundle at an exact digest | The [generated tool reference](../../docs/wiki/4-reference/mcp-tools.md) records signatures. Existing tool names and schemas retain the [append-only contract](../../docs/api-stability.md#mcp-tool-contract). ## Scope and source handling `get_catalog_native` requires a configured CIMD registry and an explicit literal grant for that tool. Missing registries and wildcard grants do not authorize it. Its only arguments are `framework_id` and `bundle_sha256`; it cannot import, download or accept a source path. A stale digest returns a fixed tool error. Default registry migration does not add the new grant. The existing fourteen tools keep their established no-registry behavior. With…
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.