MCP server for the British Natural History Museum data API
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":"natural-history-museum-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.
# A Model Context Protocol Server for the British Natural History Museum Data API This project is a Python MCP (https://modelcontextprotocol.io/introduction) server that allows your LLM to fetch data from the British Natural History Museum. Data can be fetched from their Specimens or Index Lots collections. More info on their Data API is available at https://naturalhistorymuseum.github.io/dataportal-docs/#introduction. # Developing This section is for anyone who wants to contribute to the codebase. ## Setup and Install Dependencies Clone the repository. The project is configured to use uv (Install link: https://docs.astral.sh/uv/#installation) for dependency management and building. It uses npx (Install link: https://www.npmjs.com/package/npx) to run the MCP inspector. Create a virtual env with ```shell uv venv ``` And install dependencies with ```shell uv pip install -r pyproject.toml ``` Run the inspector with ```shell ./inspector.sh ``` The inspector should run at http://localhost:5173. ## Running Unit Tests ```shell source .venv/bin/activate pytest ```
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.