Academica MCP

Evidence infrastructure for scientific, healthcare, and financial agents.

Biomedical literature, clinical trials, physician-industry payments, healthcare-provider records, SEC ownership, SEC filing fundamentals, provider-market intelligence, and reimbursement evidence through eight read-only Model Context Protocol servers.

Get an API key · Documentation · Report an issue

Five evidence surfaces. One protocol.

Install one server in under a minute with Claude Code

/plugin marketplace add academica-sh/academica-mcp
/plugin install academica-pubmed@academica

Set the API key before loading the plugin:

export ACADEMICA_API_KEY="ak_…"

[!IMPORTANT]
One repository is the distribution authority; activation remains client-specific. Claude Code and Codex expose eight independently installable plugins. Cursor, Pi, Hermes, and the optional aggregate configurations register eight named servers together and let the client control which tools remain enabled.

From research question to cited evidence

flowchart LR
    A[Research agent<br/>Claude · Cursor · MCP client]
    B[Academica MCP<br/>Authenticated read-only tools]
    C[Primary records<br/>Identifiers and provenance retained]
    A --> B --> C

Hosted endpoints

All eight servers use Streamable HTTP and accept an Academica API key in the Authorization: Bearer <key> header.

What a result preserves

Academica tools return structured evidence records rather than untraceable prose. Depending on the selected server, a result can retain:

• source identifiers such as PMID, NCT ID, NPI, and CMS record identifiers;
• official titles, statuses, dates, organizations, and named entities;
• study interventions, eligibility criteria, sponsors, and locations;
• payment categories, amounts, manufacturers, and covered recipients;
• provider credentials, taxonomies, specialties, and practice locations.

Source identifiers support inspection of the corresponding primary record. Retrieved records are research evidence, not medical advice, and absence from a result set does not establish absence from the underlying world.

Client setup

/plugin marketplace add academica-sh/academica-mcp
/plugin install academica-pubmed@academica

/plugin install academica-clinical-trials@academica
/plugin install academica-open-payments@academica
/plugin install academica-hcp@academica
/plugin install academica-sec-ownership@academica
/plugin install academica-sec-filings@academica
/plugin install academica-provider-market@academica
/plugin install academica-reimbursement@academica

Name: Academica PubMed
URL: https://academica.sh/api/mcp/pubmed
Authorization: Bearer <Academica API key>

export ACADEMICA_API_KEY="ak_…"
codex plugin marketplace add academica-sh/academica-mcp
codex plugin add academica-pubmed@academica

export ACADEMICA_API_KEY="ak_…"
dsh plugin --profile web add github:academica-sh/academica-mcp

export ACADEMICA_API_KEY="ak_…"
pi install git:github.com/academica-sh/academica-mcp

Bearer <Academica API key>

Transport: Streamable HTTP
URL: https://academica.sh/api/mcp/<server>
Header: Authorization: Bearer <Academica API key>

https://academica.sh/api/mcp/pubmed/openapi.json
https://academica.sh/api/mcp/clinical-trials/openapi.json
https://academica.sh/api/mcp/open-payments/openapi.json
https://academica.sh/api/mcp/hcp/openapi.json
https://academica.sh/api/mcp/sec-ownership/openapi.json
https://academica.sh/api/mcp/sec-filings/openapi.json
https://academica.sh/api/mcp/provider-market/openapi.json
https://academica.sh/api/mcp/reimbursement/openapi.json

Client compatibility

The portable Agent Plugins files intentionally contain no Authorization header. Clients that require bearer authentication use the native integrations listed above.

Verified distribution gates

• Root Agent Plugins manifests validate against the 1.0.0 schemas.
• All eight Codex plugins declare native bearer-token environment-variable resolution.
• All eight OpenCode configurations validate as JSON and retain OAuth-disabled bearer authentication.
• Hermes configuration and catalog manifests parse as YAML.
• The Pi package installs from a local Git source and exports a valid extension function.
• The npm package contains the Pi extension and DeepSeek Cordis bundle; dependency audit reports zero known vulnerabilities.
• Smithery publication records enumerate eight hosted servers, and the session schema validates as JSON Schema 2020-12.
• All JSON manifests parse, and no operational API key is committed.

These checks prove packaging and configuration compatibility. Directory approval, npm publication, and authenticated evidence queries are separate release gates.

Built for evidence work

Repository map

academica-mcp/
├── plugin.json                         # Open Plugins identity
├── mcp.json                            # Portable eight-server MCP catalog
├── .cursor-plugin/plugin.json          # Cursor variables and authenticated MCPs
├── .agents/plugins/marketplace.json    # Codex marketplace catalog
├── .claude-plugin/marketplace.json      # Claude Code marketplace catalog
├── package.json                        # DeepSeek Harness and Pi package
├── cordis.patch.yml                    # DeepSeek MCP client bundle
├── extensions/                         # Pi MCP adapter extension
├── clients/                            # OpenCode and Hermes configurations
├── smithery/                           # Hosted-server publication records and session schema
├── plugins/
│   ├── academica-pubmed/                # Claude and Codex plugin manifests
│   ├── academica-clinical-trials/
│   ├── academica-open-payments/
│   ├── academica-hcp/
│   ├── academica-sec-ownership/
│   ├── academica-sec-filings/
│   ├── academica-provider-market/
│   └── academica-reimbursement/
└── registry/
    ├── pubmed/server.json               # Official MCP Registry metadata
    ├── clinical-trials/server.json
    ├── open-payments/server.json
    ├── hcp/server.json
    ├── sec-ownership/server.json
    ├── sec-filings/server.json
    ├── provider-market/server.json
    └── reimbursement/server.json

Cloning this repository downloads distribution metadata. It does not download the evidence corpora or start local servers; the manifests connect compatible clients to Academica's hosted endpoints.

Security and policy

• Never commit an operational API key.
• Store ACADEMICA_API_KEY in the client environment or its protected credential store.
• Revoke exposed or unused keys at the API key console.
• Report security concerns privately to sid@academica.sh.

Privacy policy · Terms · MIT license