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":"ndi-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.
# NDI MCP > **Looking for NDI (Nace Document Intelligence)?** Outside developers should start at > [Nace Console](https://console.nace.ai) and its [documentation](https://console.nace.ai/docs), > using `nace-sdk`, `nace-cli`, or `nace-mcp`. Console keys (`nace_sk_...`) use > `Authorization: Bearer` at `https://console.nace.ai`; they do not work at `ndi-api.nace.ai`. > > The examples below cover direct NDI service access with separately provisioned > `ndi_sk_...` credentials and the `ndi-*` packages. Local and hosted [Model Context Protocol](https://modelcontextprotocol.io) servers for **NDI** (Nace Document Intelligence). Licensed **MIT**. ```bash pip install ndi-mcp # or uvx ndi-mcp login uvx ndi-mcp ``` Depends on the Apache-2.0 [`ndi-sdk`](https://pypi.org/project/ndi-sdk/) client. Install and agent config details live in that package's README; prefer `uvx ndi-mcp` over the older `ndi-sdk[mcp]` install string.
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.