Back to Browse

Open Primitive Api MCP Server

Developer ToolsLow Risk8.8MCP RegistryLocal
Free

Server data from the Official MCP Registry

33 tools, 30 US federal data domains. Ed25519 signed, provenance chains, entity graph. Free.

About

33 tools, 30 US federal data domains. Ed25519 signed, provenance chains, entity graph. Free.

Security Report

8.8
Low Risk8.8Low Risk

Valid MCP server (3 strong, 3 medium validity signals). 3 known CVEs in dependencies ⚠️ Package registry links to a different repository than scanned source. Imported from the Official MCP Registry. 1 finding(s) downgraded by scanner intelligence.

9 files analyzed · 4 issues found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Required

This plugin requests these system permissions. Most are normal for its category.

HTTP Network Access

Connects to external APIs or services over the internet.

env_vars

Check that this permission is expected for this type of plugin.

How to Install

Add this to your MCP configuration file:

{
  "mcpServers": {
    "io-github-writesdavid-open-primitive": {
      "args": [
        "-y",
        "open-primitive-mcp"
      ],
      "command": "npx"
    }
  }
}

Documentation

View on GitHub

From the project's GitHub README.

Open Primitive Protocol (OPP)

The data layer of the agent internet.

OPP defines how data providers make their data agent-consumable, verifiable, and discoverable. Three components: provider manifest, response envelope, query interface.

The Problem

Agents get data naked. No provenance. No freshness guarantee. No confidence score. No way to verify the source. The agent internet is missing its data envelope.

The Protocol

ComponentWhat it does
Manifest (/.well-known/opp.json)Declares what data a provider serves, how fresh it is, how to verify it
Response EnvelopeEvery response carries domain, source, freshness, confidence, citation, Ed25519 signature
Query InterfaceStandardized HTTP GET endpoints with predictable parameters

Conformance Levels

  • Level 1 (Basic): Manifest + envelope with domain/source/freshness
  • Level 2 (Cited): Level 1 + confidence scores + citations
  • Level 3 (Verified): Level 2 + Ed25519 cryptographic proof

Reference Implementation

Live at api.openprimitive.com. 16 US federal data domains across 11 agencies. Level 3 compliant — every response is signed.

curl https://api.openprimitive.com/v1/drugs?name=aspirin
# Returns OPP envelope with proof.type: "DataIntegrityProof"

Quick Start

Use data from an OPP provider:

const res = await fetch('https://api.openprimitive.com/v1/drugs?name=aspirin');
const data = await res.json();
console.log(data.citations.statement);
// "According to FDA FAERS, aspirin has 601,477 reported adverse events"

Implement OPP for your own data:

// 1. Create /.well-known/opp.json (see spec)
// 2. Wrap responses in the OPP envelope
// 3. Optionally sign with Ed25519

Specification

Full spec: openprimitive.com/protocol.html

Detailed spec: api.openprimitive.com/spec.html

SDK

  • sdk/opp-client.js — Client library for consuming OPP providers
  • sdk/opp-provider.js — Helper for implementing OPP
  • sdk/opp-validator.js — Validate OPP conformance

MCP Server

13 tools for Claude, Cursor, and MCP-compatible agents:

npx open-primitive-mcp

Links

License

MIT

Reviews

No reviews yet

Be the first to review this server!

Open Primitive Api MCP Server - 33 tools, 30 US federal data domains. Ed25519 signed, | MCP Marketplace