Open Primitive Mcp
@writesdavid
17 US federal data domains as MCP tools. FDA drugs, EPA water, CMS hospitals, NHTSA cars, BLS jobs, Census demographics, SEC filings, NOAA weather, and more. Signed responses with provenance
Overview
What is Open Primitive Mcp?
The MCP server for the Open Primitive Protocol (OPP), providing 13 tools for Claude, Cursor, and MCP-compatible agents. OPP defines how data providers make their data agent-consumable, verifiable, and discoverable through provider manifests, response envelopes, and a standardized query interface.
How to use Open Primitive Mcp?
Run npx open-primitive-mcp to start the server, then query OPP providers using MCP-compatible clients. For example, fetch drug data with parameters like ?name=aspirin and receive a signed envelope containing citations and provenance.
Key features of Open Primitive Mcp
- 13 tools for Claude, Cursor, and MCP-compatible agents
- Every response carries domain, source, freshness, confidence, citation, and Ed25519 signature
- Three conformance levels: Basic, Cited, and Verified
- Reference implementation covering 16 US federal data domains across 11 agencies
- SDKs for client consumption, provider implementation, and conformance validation
Use cases of Open Primitive Mcp
- Agents retrieving FDA adverse event reports with verifiable provenance
- Data providers wrapping existing APIs in the OPP envelope for agent consumption
- Validating that a provider’s responses meet OPP conformance levels
FAQ from Open Primitive Mcp
How do I start the server?
Use npx open-primitive-mcp with Node.js installed.
What data does the reference implementation provide?
16 US federal data domains across 11 agencies, all Level 3 (Verified) compliant with cryptographic signatures.
How is data authenticity guaranteed?
Every response includes an Ed25519 signature with proof.type: "DataIntegrityProof".
Can I use OPP for my own data?
Yes – create a /.well-known/opp.json manifest, wrap responses in the OPP envelope, and optionally sign with Ed25519.
What transport does the server use?
Standard HTTP GET endpoints with predictable query parameters.
