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":"inventree-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.
# InvenTreeMCP [](https://pypi.org/project/inventree-mcp/) [](https://github.com/inventree/inventree-mcp/actions/workflows/ci.yaml) [](https://codecov.io/gh/inventree/inventree-mcp) An MCP (Model Context Protocol) server for InvenTree, exposed as an InvenTree plugin. It lets MCP clients (Claude, other MCP-aware agents) query InvenTree inventory data over a Streamable HTTP endpoint. ## Design Every tool is a thin wrapper around InvenTree's own REST API view classes (see [`inventree_mcp/proxy.py`](inventree_mcp/proxy.py)), dispatched as the authenticated caller - MCP requests go through exactly the same permission checks, filtering, and serialization as the regular REST API. Tool code never queries the Django ORM directly. Currently read-only, covering parts, stock items/locations, part categories, purchase/sales/return/ build orders (with line items and allocations), companies, contacts, addresses, manufacturer/ supplier parts, BOM items, attachments, parameters, stock tracking history, test results, and project codes. Once write tools land, the `MCP_READ_ONLY` setting (see Configuration) will block them by default regardless of the calling user's permissions. Each tool's `outputSchema` and filter/ordering options are derived live from InvenTree's own serializers and views (not hand-maintained), so they can't drift as InvenTree evolves. Call `describe_filters(resource)` to see what's available for a given resource. The set of tools an MCP client sees is also filtered to what the calling user can actually use - though every call is still permission-checked in full regardless of what was advertised. ## Setup ### 1. Install the plugin Install via the InvenTree plugin manager, or via pip: ```bash pip install inventree-mcp ``` Then enable the plugin unde…
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.