io.github.rootsbymenda/pharma-regulatory
REMOTE · PHARMA-MCP-SERVER.ROOTSBYBENDA.WORKERS.DEV · 2 COMPONENTS · SCANNED AUG 3
Drug safety: DrugBank, interactions, FAERS, WHO, TGA. 7 databases. Free.
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS not yet verified: we couldn't determine whether a plaintext access path exists. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability63
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 968 tokens (~242/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- 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.
remote · pharma-mcp-server.rootsbybenda.workers.dev
claude mcp add --transport http rootsbymenda-pharma-regulatory https://pharma-mcp-server.rootsbybenda.workers.dev/mcp
[mcp_servers.rootsbymenda-pharma-regulatory] url = "https://pharma-mcp-server.rootsbybenda.workers.dev/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"rootsbymenda-pharma-regulatory": {
"type": "remote",
"url": "https://pharma-mcp-server.rootsbybenda.workers.dev/mcp",
"enabled": true
}
}
} openclaw mcp add rootsbymenda-pharma-regulatory --url https://pharma-mcp-server.rootsbybenda.workers.dev/mcp --transport streamable-http
mcp_servers:
rootsbymenda-pharma-regulatory:
url: "https://pharma-mcp-server.rootsbybenda.workers.dev/mcp" {
"mcpServers": {
"rootsbymenda-pharma-regulatory": {
"type": "http",
"url": "https://pharma-mcp-server.rootsbybenda.workers.dev/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 1 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 29 Jul 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Jul 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 62
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 · Probed https://pharma-mcp-server.rootsbybenda.workers.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=rootsbybenda.workers.dev | CN=WE1,O=Google Trust Services,C=US | 1 Aug 2026 | 30 Oct 2026 | ECDSA 256 | ECDSA-SHA256 | a19ebb28df33c3640efc0c208730db7e |
| SANs: rootsbybenda.workers.dev, *.rootsbybenda.workers.dev | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
DNSSEC insecure
Validation of pharma-mcp-server.rootsbybenda.workers.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| workers.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://pharma-mcp-server.rootsbybenda.workers.dev/mcp | Verified | 200 | |
| http (plaintext) | http://pharma-mcp-server.rootsbybenda.workers.dev/mcp | Inconclusive | 406 |
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_adverse_events ~202
Retrieve FDA FAERS post-market adverse event reports and safety signals for a drug or active ingredient. Input: drug brand name or generic active ingredient (e.g. 'ibuprofen', 'metformin'). Returns: total FAERS report counts, serious outcome counts, death report counts, top 10 adverse reactions by frequency, most common patient age groups, and drug ranking. Source: FDA Adverse Event Reporting System (FAERS) — 2,000 top-reported drugs with aggregated safety signals. For pharmacovigilance and post-market drug safety assessment. Do not use for interaction mechanisms (use check_drug_interactions), regulatory approvals (use check_drug), or supplement/nutrition questions.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Drug brand name or generic active ingredient for FDA FAERS adverse-event lookup (e.g. 'ibuprofen', 'acetaminophen', 'metformin'). Use the active ingredient when possible to capture reports filed unde… |
No output schema declared.
No examples provided.
check_drug ~288
Retrieve pharmaceutical regulatory reference data for a drug, medicine, or active ingredient across multiple authoritative datasets. Input: drug brand name, generic active ingredient, or CAS number (e.g. 'metformin', 'ibuprofen', '50-78-2'). Returns: DrugBank compound data (ID, groups, targets, SMILES, DDI count), WHO Essential Medicines listing (ATC code, formulations, indications, dosage, contraindications, pregnancy safety), Australian TGA ARTG records (ARTG ID, sponsor, category, schedule, dosage form, route, indications), and FDA NDI notifications (NDI number, FDA response, intended use). Sources: DrugBank (4,947 compounds), WHO EML, Australian TGA ARTG (23,259 medicines), FDA NDI (1,330 notifications). For pharmaceutical regulatory compliance and drug safety reference. Do not use for drug-drug interactions (use check_drug_interactions), adverse events (use check_adverse_events), or cosmetic/food/cannabis substances.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Drug brand name, generic active ingredient, medicine name, synonym, or CAS number (Chemical Abstracts Service registry number, e.g. '50-78-2'). Use generic active ingredient names when possible for c… |
No output schema declared.
No examples provided.
check_drug_interactions ~237
Check drug-drug interactions with severity, mechanism, clinical effect, and management guidance from a curated pharmaceutical interaction database. Input: primary drug name and optional second drug for pair-specific lookup (e.g. 'warfarin' + 'aspirin'). Returns: interaction pairs with severity classification, pharmacological mechanism, clinical effect description, evidence level, and management recommendations. Single-drug queries return all known interactions grouped by severity. Database: 5,000 documented drug-drug interactions with clinical evidence. For pharmaceutical safety review and medication management. Do not use for drug monographs (use check_drug), adverse events (use check_adverse_events), or non-drug interactions.
| Name | Type | Req | Description |
|---|---|---|---|
| drug | string | yes | Primary drug or active ingredient name for interaction lookup (e.g. 'warfarin', 'metformin', 'lisinopril'). Use generic names when possible because interaction datasets usually normalize to active su… |
| second_drug | string | — | Optional second drug or active ingredient name for a specific interaction pair (e.g. 'aspirin'). Omit when the user wants all known interactions for the primary drug. |
No output schema declared.
No examples provided.
search_pharma ~241
Search across all pharmaceutical regulatory and safety datasets by disease area, drug class, safety endpoint, indication, target, or regulatory keyword. Input: keyword for broad discovery (e.g. 'diabetes', 'antibiotic', 'hepatotoxicity', 'pregnancy', 'cancer'). Returns: cross-dataset matches from DrugBank, WHO Essential Medicines, Australian TGA ARTG, FDA FAERS, drug interactions, FDA NDI, and ChEMBL bioactivity — each with dataset labels, identifiers, and source-specific fields. Database: 7 pharmaceutical datasets totaling 45,000+ records. For pharmaceutical research and regulatory intelligence discovery. Do not use when the exact drug name is known (use check_drug, check_drug_interactions, or check_adverse_events for targeted lookups).
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Pharmaceutical keyword, disease area, drug class, safety endpoint, indication, target, or regulatory term (e.g. 'diabetes', 'antibiotic', 'cancer', 'pregnancy', 'hepatotoxicity'). Use this for broad… |
No output schema declared.
No examples provided.