# io.github.ayeongo/pharmasync (npm · @pharmasync/mcp)

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

- Trust score: 66/100 (medium)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- npm · `@pharmasync/mcp`: 66/100 (this document), [markdown](https://verifymcp.io/servers/ayeongo-pharmasync/pharmasync-mcp.md), [page](https://verifymcp.io/servers/ayeongo-pharmasync/pharmasync-mcp)

## Channel facts

- Registry: `npm`
- Package: `@pharmasync/mcp`
- Version: `0.2.0`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 31 of 92 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 19/100
  - Repository check failed: the declared repository URL returned HTTP 404.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 13 days ago).
  - Security-disclosure policy not yet verified: we couldn't inspect the source repository.
- **Schema Quality & AI Usability**: 81/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

**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.

## 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.

### Claude

```bash
claude mcp add ayeongo-pharmasync -- npx -y @pharmasync/mcp
```

### Cursor

```json
{
  "mcpServers": {
    "ayeongo-pharmasync": {
      "command": "npx",
      "args": [
        "-y",
        "@pharmasync/mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "ayeongo-pharmasync": {
      "command": "npx",
      "args": [
        "-y",
        "@pharmasync/mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add ayeongo-pharmasync -- npx -y @pharmasync/mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ayeongo-pharmasync": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@pharmasync/mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ayeongo-pharmasync --command npx --arg -y --arg @pharmasync/mcp
```

### Hermes

```yaml
mcp_servers:
  ayeongo-pharmasync:
    command: "npx"
    args: ["-y", "@pharmasync/mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "ayeongo-pharmasync": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@pharmasync/mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add ayeongo-pharmasync -t stdio -c npx -a -y @pharmasync/mcp
```

### Other

```json
{
  "mcpServers": {
    "ayeongo-pharmasync": {
      "command": "npx",
      "args": [
        "-y",
        "@pharmasync/mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-08 (score 66, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-11-07 (score 51)

First indexed and scored.

## MCP tools (5)

### `lookup_product` (~122 tokens)

Look up a medicine

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`.

Input parameters:

- `code` (string): An exact dm+d code (VMP identifier), e.g. "42381011000001106".
- `name` (string): A case-insensitive substring of the medicine name, e.g. "ramipril".

### `current_shortages` (~105 tokens)

Current shortages by tier

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.

Input parameters:

- `tier` (string): Restrict to a single tier. Omit for all tiers.

### `changes_since` (~106 tokens)

Supply changes since a cursor

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).

Input parameters:

- `cursor` (string): The `latest_cursor` from a previous call (e.g. "2026-08"). Omit for all changes.

### `concessions_for` (~112 tokens)

Price concessions for a medicine

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`.

Input parameters:

- `code` (string): An exact dm+d code (VMP identifier), e.g. "42381011000001106".
- `name` (string): A case-insensitive substring of the medicine name, e.g. "ramipril".

### `workforce_stats` (~190 tokens)

The Workforce Panel ledger

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.

Input parameters:

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

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/ayeongo-pharmasync/pharmasync-mcp#diagnostics

## Score history

- 2026-11-21: 66
- 2026-11-20: 66
- 2026-11-19: 66
- 2026-11-18: 66
- 2026-11-17: 66
- 2026-11-16: 66
- 2026-11-15: 66
- 2026-11-14: 66
- 2026-11-13: 66
- 2026-11-12: 66
- 2026-11-11: 66
- 2026-11-10: 66
- 2026-11-09: 66
- 2026-11-08: 66
- 2026-11-07: 51

## 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.

## Links

- npm package: https://www.npmjs.com/package/@pharmasync/mcp
- Socket report: https://socket.dev/npm/package/@pharmasync/mcp
- Changelog RSS feed: https://verifymcp.io/servers/ayeongo-pharmasync/pharmasync-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/ayeongo-pharmasync/pharmasync-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/ayeongo-pharmasync/pharmasync-mcp.json
- HTML version of this page: https://verifymcp.io/servers/ayeongo-pharmasync/pharmasync-mcp
