MHRA (UK Medicines and Healthcare products Regulatory Agency) — the public products register…
MCPpedia last refreshed this data
io.github.pipeworx-io/mhra-uk is an MCP server that MHRA (UK Medicines and Healthcare products Regulatory Agency) — the public products register…. Its tool list has not been published yet over http, requires no API key, and scores 87/100 on MCPpedia's security, maintenance and efficiency rubric.
Config is the same across clients - only the file and path differ.
{
"mcpServers": {
"mhra-uk": {
"url": "https://gateway.pipeworx.io/mhra-uk/mcp"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
MHRA (UK Medicines and Healthcare products Regulatory Agency) — the public products register…
This server supports HTTP transport. Be the first to test it - help the community know if it works.
Five weighted categories - click any category to see the underlying evidence.
No known CVEs.
Checked @pipeworx/mcp-mhra-uk against OSV.dev.
Click any tool to inspect its schema.
Be the first to review
Have you used this server?
Share your experience - it helps other developers decide.
Sign in to write a review.
Others in health
MCP server for the ClinicalTrials.gov v2 API. Search trials, retrieve study details and results, and match patients to eligible trials.
Search ClinicalTrials.gov: find studies, retrieve results, match patients to candidate trials.
Control FL Studio with Claude: in-DAW mixing, diagnosis, routing, and composition.
MCP server providing seamless access to FHIR APIs for AI tools and healthcare applications
MCP Security Weekly
Get CVE alerts and security updates for io.github.pipeworx-io/mhra-uk and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
UK medicines register — the MHRA products database behind products.mhra.gov.uk. Post-Brexit the EMA register no longer covers the UK, so this is the UK authorisation surface.
Part of Pipeworx — an MCP gateway connecting AI agents to 1865+ live data sources. This is an independent, unofficial integration — not affiliated with, endorsed by, or published by the upstream provider.
It is an index of documents — Summaries of Product Characteristics, patient information leaflets and public assessment reports, as PDFs — with metadata about each. It is not a register of structured product records. There is no indication field, no pathway field and no authorisation-status field in it.
That shapes every tool here. mhra_product returns the document metadata and
the authoritative PDF URL rather than a summary of the document, because the
authorised indication text is written in section 4.1 of the SmPC and nowhere
else. authorisation_status is always unknown, with a note saying why: the
only status-shaped field is release_state, which is Y on all 79,112 released
documents and means "published", not "currently authorised". Reporting it as
authorisation status would be a guess wearing a field name.
mhra_search(query, doc_type?, territory?, limit?, offset?) — by product,
brand or active substance. One row per document.mhra_product(pl_number) — every document for one licence, grouped by type.
Accepts PL 29831/0798, PL29831/0798, PL298310798 and the PLGB / PLNI
forms.mhra_recent_changes(since, doc_type?, limit?) — documents added or revised
since a date, newest first. Idempotent on replay.mhra_snapshot() — total count, counts per document type, newest document
date, and the paging recipe. Counts, never documents.PL is UK-wide, PLGB is Great Britain only, PLNI is Northern Ireland only.
Measured 2026-09-07: UK 64,126 documents, GB 8,428, NI 48. Treating them as
interchangeable answers "is this authorised in the UK?" with a licence that may
cover a small fraction of it.
There is no bulk download. Walk the register with
mhra_search({query: "*", limit: 50, offset: N}), stepping offset by 50.
mhra_snapshot() returns the current total so you know when to stop.
The register records documents, and a withdrawal is not published as an event.
covers on every response says so. Do not read an absence as a withdrawal.
Search runs on Azure Cognitive Search using MHRA's own client key — the one
shipped to every browser that loads products.mhra.gov.uk. No account, payment or
agreement stands between anyone and this data. But if MHRA rotates that key this
pack stops working, and the fix is to read the current one out of their public
bundle again. medicines.api.mhra.gov.uk/graphql also appears in their bundle
and 503s on every request; do not build on it.
created is sortable but not filterable on this index, which is why
recent_changes orders newest-first and stops at the cutoff rather than pushing
a date filter upstream.
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"mhra-uk": {
"url": "https://gateway.pipeworx.io/mhra-uk/mcp"
}
}
}
tools/list at https://gateway.pipeworx.io/mhra-uk/mcp returns the tools in the table
above plus the shared Pipeworx meta-tools — ask_pipeworx,
discover_tools, search_within, remember/recall and the rest of the
gateway-wide set. So the tool count you see is larger than this table: a
single-pack endpoint currently lists roughly 30 shared tools alongside the
pack's own. The connection's initialize response states its exact scope, and
is the authoritative answer for a giv