Pharma MCP server
What it does
Three MCP servers for dispatching vendor requests and receiving bids across legal, insurance claims, and AEC services. Designed for AI assistants to connect with credentialed vendors who respond with quotes within ten minutes.
- Send a legal matter (court reporter, expert witness, translation, e-discovery) to vendors and receive live competitive bids.
- Route insurance claims work (IME, surveillance, peer review, life-care planning) to qualified providers with credential verification.
- Dispatch AEC subcontractor requests with prequalification checks, bonding capacity verification, and safety record pulls.
Tools this server exposes
| Tool | Does |
|---|---|
| scope_dispatch_matter | Send a matter to vendors and receive live quotes. |
| scope_briefing | Daily briefing across all open matters. |
| scope_get_matter | Retrieve details of a specific matter. |
| scope_list_matters | List all open or closed matters. |
| scope_list_categories | List available service categories. |
| scope_list_vendors | List vendors available in a category. |
| scope_list_roster | List your organization's preferred vendor roster. |
| scope_set_vendor_tier | Assign a vendor to a tier in your roster. |
| scope_remove_from_roster | Remove a vendor from your roster. |
| scope_award_matter | Award a matter to a vendor. |
| scope_roster_audit | Audit your vendor roster for compliance and status. |
| scope_vendor_health | Check the health and performance of a vendor. |
| scope_spend_rollup | View spending across vendors and categories. |
| scope_credential_alerts | Receive alerts about vendor credential changes. |
| swp_clarify | Clarify terms in an active Scope Work Protocol negotiation session. |
| swp_accept | Accept terms in an active negotiation session. |
| swp_reject | Reject terms in an active negotiation session. |
| swp_session_status | Check the status of an active negotiation session. |
This entry comes from the registry but points to no public repository, so there is nothing to check: no commit history, no source, no tool list. It is listed for completeness and left out of search engines.
Before you enable it
An MCP server runs with whatever access you give it. Start with a development account rather than production, and check which tools the server exposes before you let an agent call them unattended.