# BOP Data MCP Server

> Access: NO AUTH · NO COST · PUBLIC. MCP reads the same canonical datasets served by data.bop.ink.

## Endpoint

- Streamable HTTP: https://data.bop.ink/mcp/server
- Authentication: none
- Data source: canonical BOP Data public dataset artifacts
- Dataset stewardship: BOP Data maintains the normalized representation; original source publishers are identified in each dataset's provenance when available.
- Capability status: available
- Intended protocol era: MCP 2026-07-28 through the official TypeScript SDK v2

## Resources

- `bop://catalog` — public dataset catalog.
- `bop://dataset/{canonicalId}` — ResourceTemplate resolving one canonical dataset.

Dataset resources return the same `bop.dataset/1` representation used by the public JSON API. Agents should treat Canonical ID as the stable identity.

## Tools

- `search_datasets(query?, category?)` — read-only catalog search returning matching Canonical IDs/resources.

BOP Data uses Resources for direct dataset reads. A separate `get_dataset` tool is intentionally unnecessary when the dataset ResourceTemplate is supported by the client.

## HTTP fallback

- Catalog JSON: https://data.bop.ink/api/v1/datasets.json
- Dataset JSON: https://data.bop.ink/api/v1/datasets/{canonicalId}.json
- OpenAPI: https://data.bop.ink/openapi.json

## Discovery

- Website overview: https://data.bop.ink/llms.txt
- Generated dataset directory: https://data.bop.ink/llms-full.txt
- Human MCP page: https://data.bop.ink/mcp

## Safety and truth

- MCP never performs independent web research.
- MCP does not maintain an MCP-only dataset database.
- Dataset values, freshness and provenance must stay in parity with the canonical JSON representation.