Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.ayeongo/pharmasync

NPM · @PHARMASYNC/MCP

Read-only NHS medicine supply data: shortages, SSPs, price concessions and dm+d lookups.

Available components

0 this week 66 Trust /100

Last scanned (20 hours ago)

Scores higher than 38% of npm servers

Category Health and Science

Trust breakdown (7 categories)

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 → Why this is hard to score →

Supply Chain Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 31 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
  • Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
  • 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 13 days ago).Pass
  • Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability81
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 635 tokens (~127/item across 5 items; 5 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 Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

What we tested

Checks we ran (14)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Schema quality
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (2)

These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Security disclosure in Provenance & TransparencySecurity-disclosure policy not yet verified: we couldn't inspect the source repository.
  • Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 8 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 7 Nov 26 51

    First indexed and scored.

Diagnostics

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 21 Nov 2026 · Analysed npm/@pharmasync/mcp@0.2.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 92 packages
Packages resolved 92
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 5 exposed · ~635 tokens

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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
changes_since ~106

Return detected supply changes from the delta feed. Pass the `cursor` you last stored to get only newer changes; omit it for the full feed. Each response includes `latest_cursor` — store it and pass it next time. The feed is not retrospective: events predating change detection carry no change record (see the feed limitations).

NameTypeReqDescription
cursorstring–The `latest_cursor` from a previous call (e.g. "2026-08"). Omit for all changes.

No output schema declared.

No examples provided.

concessions_for ~112

Return the price-concession events for a medicine, by exact dm+d code or a substring of its name, newest first. A concession is a financial-exposure and market-stress signal, published as the source states it. Provide `code` or `name`.

NameTypeReqDescription
codestring–An exact dm+d code (VMP identifier), e.g. "42381011000001106".
namestring–A case-insensitive substring of the medicine name, e.g. "ramipril".

No output schema declared.

No examples provided.

current_shortages ~105

List the UK medicines with a government severity tier currently in force — WATCH (a Medicine Supply Notification), CONCERN (a restricted-export designation) or CRITICAL (a Serious Shortage Protocol) — ranked highest first, each with the citing act and its date. Optionally filter to one tier. Every tier is a citation of a public act, reproducible without trusting Pharmasync.

NameTypeReqDescription
tierstring–Restrict to a single tier. Omit for all tiers.

No output schema declared.

No examples provided.

lookup_product ~122

Look up a UK medicine by exact dm+d code or by a substring of its name. Returns the dm+d product, its current severity tier (the highest government act in force, with citation), and its supply events (MSN / SSP / price concession), newest first. Provide `code` or `name`.

NameTypeReqDescription
codestring–An exact dm+d code (VMP identifier), e.g. "42381011000001106".
namestring–A case-insensitive substring of the medicine name, e.g. "ramipril".

No output schema declared.

No examples provided.

workforce_stats ~190

The second supply chain: medicines and the people who dispense them. Returns published workforce indicators — vacancy rate by role and region, GPhC registrant counts, pharmacy network change by region, and shortage designation status — newest period first. Optionally filter by metric, role and/or region (filters combine; omit all for the full ledger). Not a jobs board: no listings, no applications, no salary benchmarking — observed aggregate data only, provenance on every row.

NameTypeReqDescription
metricstring–Restrict to one indicator. Omit for every metric currently populated.
regionstring–An exact ICS name (vacancy rate) or Health-and-Wellbeing-Board name (pharmacy count / network change). Omit for every region.
rolestring–e.g. "PHARMACIST" or "PHARMACY_TECHNICIAN". Omit for every role.

No output schema declared.

No examples provided.

Install

How do I install the io.github.ayeongo/pharmasync MCP server?

io.github.ayeongo/pharmasync runs locally as an npm package, launched with npx -y @pharmasync/mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @pharmasync/mcp

# add to Claude Code
claude mcp add ayeongo-pharmasync -- npx -y @pharmasync/mcp
Common questions

What is the io.github.ayeongo/pharmasync MCP server?

io.github.ayeongo/pharmasync is an MCP server listed in the public MCP registry as io.github.ayeongo/pharmasync. Read-only NHS medicine supply data: shortages, SSPs, price concessions and dm+d lookups. This page covers its npm package (@pharmasync/mcp).

Is the io.github.ayeongo/pharmasync MCP server safe to use?

io.github.ayeongo/pharmasync scores 66 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the io.github.ayeongo/pharmasync MCP server expose?

io.github.ayeongo/pharmasync exposes 5 tools: lookup_product, current_shortages, changes_since, concessions_for, workforce_stats. Their descriptions and schemas cost roughly 635 tokens of context every time the server is loaded.

Is the io.github.ayeongo/pharmasync MCP server still maintained?

io.github.ayeongo/pharmasync is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the io.github.ayeongo/pharmasync MCP server under?

io.github.ayeongo/pharmasync declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

What did VerifyMCP test on the io.github.ayeongo/pharmasync MCP server?

VerifyMCP ran 14 checks on io.github.ayeongo/pharmasync, covering Malware scan, Known CVEs, Install scripts, Dependency health and 10 more. 2 items could not be completed, a gap on our side rather than a finding about io.github.ayeongo/pharmasync: Security disclosure and Stability. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.