Orchestraprime

io.github.OrchestraPrimePublished by GitHub account OrchestraPrimev2.0.1Updated Oct 25, 2026

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

VerifiedSTDIODesktop onlySecurity & MonitoringBusiness & Commerce

Overview

AI-generated overview

A local MCP server that gives an assistant regulatory intelligence (FDA, ICH, EMA) and sanctions screening (OFAC, EU, UK) for Claude.

What you can do
Look up regulatory intelligence from FDA, ICH and EMA sources through the assistant. Screen names or entities against sanctions lists from OFAC, the EU and the UK. The manifest lists no individual tools, so the exact operations are not documented in the supplied material.
When to use it
Useful when an assistant needs to check regulatory guidance or screen parties against sanctions lists during compliance, trade or research work. It is a desktop-only local process, so it suits users working from a desktop MCP client.
Requirements
Runs as a local stdio process on the user's machine, installed from the npm package @orchestraprime/mcp-server, so Node.js and npm are needed. Desktop only; no web execution. No authentication, environment variables or headers are declared.
Before you install
The manifest declares no authentication or credentials, but the README does not explain where regulatory or sanctions data comes from or whether queries leave the machine. Screening results should be verified against official sources before any compliance decision.

Installation

In SourceWeft

  1. Open Orchestraprime in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

mcp-server

OrchestraPrime MCP Server — Regulatory intelligence and sanctions screening for Claude

Source: README.md at commit 34e3806

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v2.0.1LatestSep 16, 2026

Score

40% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.