Model Context Protocol exposure adapter for Agnara capabilities.
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":"agnara-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.
# agnara-mcp Model Context Protocol exposure adapter. Owns MCP server projection, tool discovery, invocation dispatch, schema mapping and MCP authorization integration. This distribution is built and versioned with the synchronized workspace set. Which versions exist on an index is answered by its PyPI project page, not by this file: a README ships inside the artifact and cannot describe the state of a publication that happens after it is built. - Import package: `agnara_mcp` - Depends on: the exact synchronized `agnara` version, plus `mcp==2.1.1` - Must not import: sibling adapter packages See `ARCHITECTURE.md` sections 3 and 4 for the package boundaries and the allowed dependency graph. ## Protocol baseline The first adapter line targets exactly MCP `2026-07-28` through the official Python SDK `mcp==2.1.1`. The public constants are: ```python from agnara_mcp import MCP_PROTOCOL_VERSION, SUPPORTED_MCP_PROTOCOL_VERSIONS assert MCP_PROTOCOL_VERSION == "2026-07-28" assert SUPPORTED_MCP_PROTOCOL_VERSIONS == ("2026-07-28",) ``` This pin establishes the protocol boundary; it is not a claim that the unfinished E7 adapter already implements every MCP feature. Tool projection, schema mapping, discovery, the request-scoped authorization bridge, canonical result and interaction-required projection, and `tools/call` dispatch are implemented. MRTR resumption and Tasks behavior remain separate backlog work, and invocation is not yet benchmarked. Bounded official SDK compatibility evidence is recorded in [`docs/MCP_CONFORMANCE.md`](../../docs/MCP_CONFORMANCE.md); it covers the implemented surfaces and does not claim complete MCP conformance. Legacy protocol revisions are not advertised until Agnara has explicit compatibility tests for them, even though the SDK can serve older clients. ## Tool exposures Declare tool exposure separately from capability semantics: ```python from agnara import Agnara from agnara_mcp import Mcp app = Agnara("users") mcp = Mcp(app) @app.…
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.