io.github.OrchestraPrime/orchestraprime
NPM · @ORCHESTRAPRIME/MCP-SERVER · SCANNED AUG 3
Regulatory intelligence (FDA, ICH, EMA) and sanctions screening (OFAC, EU, UK) for Claude
Available components
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 →
Supply Chain Security88
- No malware found by supply-chain analysis.Pass
- Only part of the dependency tree could be resolved (113 of 114), so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- Only part of the dependency tree could be resolved (113 of 114), so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 175 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability83
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).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 Management27
- Stability observed for 8 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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · @orchestraprime/mcp-server
claude mcp add orchestraprime-orchestraprime -- npx -y @orchestraprime/mcp-server
codex mcp add orchestraprime-orchestraprime -- npx -y @orchestraprime/mcp-server
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"orchestraprime-orchestraprime": {
"type": "local",
"command": [
"npx",
"-y",
"@orchestraprime/mcp-server"
],
"enabled": true
}
}
} openclaw mcp add orchestraprime-orchestraprime --command npx --arg -y --arg @orchestraprime/mcp-server
mcp_servers:
orchestraprime-orchestraprime:
command: "npx"
args: ["-y", "@orchestraprime/mcp-server"] {
"mcpServers": {
"orchestraprime-orchestraprime": {
"command": "npx",
"args": [
"-y",
"@orchestraprime/mcp-server"
]
}
}
} 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.
- 3 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Aug 26 +65
- Provenance: unverified → fail ▼ security
- Known CVEs: unverified → partial ▲ security
- Install scripts: unverified → pass ▲ security
- Malware scan: unverified → pass ▲ security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- Security disclosure: unverified → fail ▼ functional
- Stability: unverified → 0.23 ▲ functional
- Maintenance: unverified → pass ▲ functional
- Dependency health: unverified → partial ▲ functional
- License: unverified → pass ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Schema quality: unverified → 100 ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Licence: MIT functional
- 1 Aug 26 −32
- Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
- Security disclosure: fail → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: 100 → unverified ▼ functional
- 31 Jul 26 −27
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 −11
- Malware scan: pass → unverified ▼ security
- Schema quality: unverified → good ▲ functional
- 29 Jul 26 +50
- Provenance: unverified → fail ▼ security
- Install scripts: unverified → pass ▲ security
- Known CVEs: unverified → partial ▲ security
- Security disclosure: unverified → fail ▼ functional
- Schema quality: unverified → 100 ▲ functional
- License: unverified → pass ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Maintenance: unverified → pass ▲ functional
- Licence: MIT functional
- 28 Jul 26 −28
- Tool coverage: 100 → unverified ▼ functional
- Security disclosure: fail → unverified ▼ functional
- Schema quality: 100 → unverified ▼ functional
- Dependency health: unverified → partial ▲ functional
- 27 Jul 26 53
First indexed and scored.
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 3 Aug 2026 · Analysed npm/@orchestraprime/[email protected]
Provenance none
Ecosystem: npm · Outcome: none
Dependencies 113 packages
113 packages in the resolved dependency tree · 112 deprecated · 34 stale.
The dependency tree was only partially resolved, so these counts may be incomplete.
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.
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)
| Name | Type | Req | Description |
|---|---|---|---|
| intended_use | string | yes | Intended use statement for the software |
| software_description | string | yes | Detailed description of the software's functionality and features |
| target_user | string | — | Primary 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+)
| Name | Type | Req | Description |
|---|---|---|---|
| check_categories | array | — | Specific protocol categories to check (default all 8) |
| protocol_text | string | yes | The 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.
| Name | Type | Req | Description |
|---|---|---|---|
| days_back | number | — | Number of days to look back for updates |
| limit | number | — | Maximum number of updates to return |
| sources | array | — | Filter 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.
| Name | Type | Req | Description |
|---|---|---|---|
| rule_id | string | yes | Unique 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.
| Name | Type | Req | Description |
|---|---|---|---|
| entities | array | yes | Array of entities to screen (each with id, name, and optional entity_type) |
| lists | array | — | Sanctions lists to screen against |
| max_results_per_entity | number | — | Maximum matches per entity |
| threshold | number | — | Match 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.
| Name | Type | Req | Description |
|---|---|---|---|
| entity_type | string | — | Type of entity being screened |
| lists | array | — | Specific sanctions lists to screen against |
| max_results | number | — | Maximum number of matches to return |
| name | string | yes | Full name of the individual or organization to screen |
| threshold | number | — | Match 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".
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | — | Maximum number of results to return |
| query | string | yes | Natural language search query for regulatory content |
| sources | array | — | Filter results to specific regulatory sources (default all) |
No output schema declared.
No examples provided.