Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.OrchestraPrime/orchestraprime

NPM · @ORCHESTRAPRIME/MCP-SERVER · SCANNED SEP 20

Regulatory intelligence (FDA, ICH, EMA) and sanctions screening (OFAC, EU, UK) for Claude

0 this week 85 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 36 of 114 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability87
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 1175 tokens (~90/item across 13 items; 9 tools + 4 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management90
  • Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the io.github.OrchestraPrime/orchestraprime MCP server?

io.github.OrchestraPrime/orchestraprime runs locally as an npm package, launched with npx -y @orchestraprime/mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @orchestraprime/mcp-server

# add to Claude Code
claude mcp add orchestraprime-orchestraprime -- npx -y @orchestraprime/mcp-server
// .cursor/mcp.json
{
  "mcpServers": {
    "orchestraprime-orchestraprime": {
      "command": "npx",
      "args": [
        "-y",
        "@orchestraprime/mcp-server"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "orchestraprime-orchestraprime": {
      "command": "npx",
      "args": [
        "-y",
        "@orchestraprime/mcp-server"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add orchestraprime-orchestraprime -- npx -y @orchestraprime/mcp-server
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "orchestraprime-orchestraprime": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@orchestraprime/mcp-server"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add orchestraprime-orchestraprime --command npx --arg -y --arg @orchestraprime/mcp-server
# ~/.hermes/config.yaml
mcp_servers:
  orchestraprime-orchestraprime:
    command: "npx"
    args: ["-y", "@orchestraprime/mcp-server"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "orchestraprime-orchestraprime": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@orchestraprime/mcp-server"
      ]
    }
  }
}
# add to Vellum
assistant mcp add orchestraprime-orchestraprime -t stdio -c npx -a -y @orchestraprime/mcp-server
// mcp.json
{
  "mcpServers": {
    "orchestraprime-orchestraprime": {
      "command": "npx",
      "args": [
        "-y",
        "@orchestraprime/mcp-server"
      ]
    }
  }
}
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 20 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

  • 17 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 16 Sept 26 0
    • Stability: 0.97 → pass security
  • 15 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

  • 13 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

  • 12 Sept 26 0
    • Security disclosure: unverified → fail functional
  • 11 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 20 Sept 2026 · Analysed npm/@orchestraprime/mcp-server@2.0.1

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 114 packages
Packages resolved 114
Stale 36
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 9 exposed · ~1,111 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
check_cds_classification ~200

Analyze software against FDA Clinical Decision Support (CDS) 4-criteria to determine if it qualifies for the CDS exemption under the 21st Century Cures Act Section 3060. When to use: When you need to assess whether a software product requires FDA clearance/approval or qualifies as exempt CDS. Evaluates all 4 criteria: 1. Not intended to acquire/process medical images or signals 2. Intended to display, analyze, or print medical information 3. Intended for healthcare professionals (not patients) 4. Does not provide specific diagnostic/treatment recommendations Classification: EXEMPT (all 4 met) or DEVICE (any criterion failed)

NameTypeReqDescription
intended_usestringyesIntended use statement for the software
software_descriptionstringyesDetailed description of the software's functionality and features
target_userstringPrimary target user of the software (inferred from text if not provided)

No output schema declared.

No examples provided.

check_protocol_compliance ~136

Analyze a clinical trial protocol against ICH GCP E6(R2) required elements. Checks for presence and completeness of 8 essential protocol sections: background, objectives, design, subjects, treatment, safety, statistical, ethics. When to use: During protocol review to identify missing or incomplete sections before submission. Provides gap analysis with specific recommendations. Overall status: compliant (0 gaps), gaps_found (1-2 gaps), major_gaps (3+)

NameTypeReqDescription
check_categoriesarraySpecific protocol categories to check (default all 8)
protocol_textstringyesThe clinical trial protocol text to analyze

No output schema declared.

No examples provided.

get_recent_updates ~122

Get recent regulatory updates and guidance changes from FDA, ICH, EMA, WHO, and CDISC. Shows new guidance documents, rule changes, and announcements. When to use: To check what regulatory changes have happened recently, or to stay current on guidance updates in specific areas. Note: Currently uses curated sample data. Real-time API integration coming soon.

NameTypeReqDescription
days_backnumberNumber of days to look back for updates
limitnumberMaximum number of updates to return
sourcesarrayFilter updates to specific regulatory sources

No output schema declared.

No examples provided.

get_rule_details ~82

Retrieve the full text, citations, and metadata for a specific regulatory rule. Use rule IDs obtained from search_regulations results. When to use: After finding a relevant rule via search_regulations, use this tool to get the complete rule text, effective dates, and citation information.

NameTypeReqDescription
rule_idstringyesUnique rule identifier from search_regulations results

No output schema declared.

No examples provided.

list_sanctions_lists ~75

List all available sanctions lists with entity counts and coverage details. Includes OFAC SDN, OFAC Consolidated, EU Sanctions, UK HMT, UN Consolidated, and BIS DPL. When to use: To see which sanctions lists are available for screening, or to check entity coverage and last update dates.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_sources ~51

List all available regulatory data sources in CTWise, including rule counts and last update timestamps. When to use: To see what regulatory databases are available for searching, or to check how many rules each source contains.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

screen_batch ~145

Screen multiple individuals or organizations against global sanctions lists in a single batch operation. Supports up to 100 entities per batch. When to use: For bulk compliance screening during due diligence processes, onboarding multiple counterparties, or periodic re-screening of entity lists. IMPORTANT: Results are NEVER cached and always reflect real-time data. Results should be reviewed by compliance professionals.

NameTypeReqDescription
entitiesarrayyesArray of entities to screen (each with id, name, and optional entity_type)
listsarraySanctions lists to screen against
max_results_per_entitynumberMaximum matches per entity
thresholdnumberMatch confidence threshold for all entities

No output schema declared.

No examples provided.

screen_entity ~169

Screen an individual or organization against global sanctions lists including OFAC SDN, OFAC Consolidated, EU Sanctions, UK HMT, UN Consolidated, and BIS DPL. When to use: For compliance checks on counterparties, customers, or business partners. Results include match confidence scores and source evidence. IMPORTANT: Results are NEVER cached and always reflect real-time data. Results should be reviewed by compliance professionals.

NameTypeReqDescription
entity_typestringType of entity being screened
listsarraySpecific sanctions lists to screen against
max_resultsnumberMaximum number of matches to return
namestringyesFull name of the individual or organization to screen
thresholdnumberMatch confidence threshold (0.5 to 1.0)

No output schema declared.

No examples provided.

search_regulations ~131

Search across FDA, ICH, EMA, WHO, and CDISC regulatory databases using natural language. Returns relevant rules with citations, summaries, and reference links. When to use: When you need to find specific regulatory requirements, guidance documents, or rules related to a topic. Supports queries like "What FDA requirements apply to AI diagnostic software?" or "ICH GCP informed consent requirements".

NameTypeReqDescription
limitnumberMaximum number of results to return
querystringyesNatural language search query for regulatory content
sourcesarrayFilter results to specific regulatory sources (default all)

No output schema declared.

No examples provided.

Common questions

What is the io.github.OrchestraPrime/orchestraprime MCP server?

io.github.OrchestraPrime/orchestraprime is an MCP server listed in the public MCP registry as io.github.OrchestraPrime/orchestraprime. Regulatory intelligence (FDA, ICH, EMA) and sanctions screening (OFAC, EU, UK) for Claude. This page covers its npm package (@orchestraprime/mcp-server).

Is the io.github.OrchestraPrime/orchestraprime MCP server safe to use?

io.github.OrchestraPrime/orchestraprime scores 85 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the io.github.OrchestraPrime/orchestraprime MCP server expose?

io.github.OrchestraPrime/orchestraprime exposes 9 tools: check_cds_classification, check_protocol_compliance, get_recent_updates, get_rule_details, list_sanctions_lists, and 4 more. Their descriptions and schemas cost roughly 1,111 tokens of context every time the server is loaded.

Is the io.github.OrchestraPrime/orchestraprime MCP server still maintained?

io.github.OrchestraPrime/orchestraprime is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the io.github.OrchestraPrime/orchestraprime MCP server under?

io.github.OrchestraPrime/orchestraprime declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.