RxLocal pharmacy portal MCP — prescriptions, messages, confirm-gated refill requests
MCPpedia last refreshed this data
io.github.chrischall/rxlocal-mcp is an MCP server that RxLocal pharmacy portal MCP — prescriptions, messages, confirm-gated refill requests. Its tool list has not been published yet over stdio, sse and http, requires no API key, and scores 58/100 on MCPpedia's security, maintenance and efficiency rubric.
Config is the same across clients - only the file and path differ.
{
"mcpServers": {
"io-github-chrischall-rxlocal-mcp": {
"args": [
"-y",
"rxlocal-mcp"
],
"command": "npx"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
RxLocal pharmacy portal MCP — prescriptions, messages, confirm-gated refill requests
Run this in your terminal to verify the server starts. Then let us know if it worked - your result helps other developers.
npx -y 'rxlocal-mcp' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories - click any category to see the underlying evidence.
No known CVEs.
Checked rxlocal-mcp against OSV.dev.
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.
BioMCP: Biomedical Model Context Protocol
Control FL Studio with Claude: in-DAW mixing, diagnosis, routing, and composition.
MCP Security Weekly
Get CVE alerts and security updates for io.github.chrischall/rxlocal-mcp and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
MCP server for the RxLocal pharmacy patient portal (patient.rxlocal.com,
PioneerRx / RedSail Technologies). It reads your prescriptions, refill options
and pharmacy messages, and can request refills and message the pharmacy behind a
confirm gate, through your signed-in browser tab, reusing your authenticated
session via the fetchproxy bridge.
This project was developed and is maintained by AI. Use at your own discretion.
| Tool | Returns |
|---|---|
rxlocal_list_prescriptions | Prescriptions on file: drug, Rx number, rxID, pharmacy, last fill, refills remaining, days supply, expiration, prescriber, and whether a refill can be requested now (canRequestRefill) or needs a renewal (requiresRenewal). view: full adds NDC, imprint and ids; view: raw is the whole response. |
rxlocal_get_refill_options | What a refill request can choose at a pharmacy location: pickup / delivery / mail, pickup times, the pickup calendar, the pharmacy's address, phone and hours, and its refill disclaimers. Your own addresses and phone are only in view: full/raw. |
rxlocal_list_messages | Recent secure messages with the pharmacy, newest first. Never marks anything read; recipient email/phone are always removed. |
rxlocal_profile | Account holder's name, email, phone, account type, patient + user IDs |
rxlocal_age_gate | Whether the account holder is under the portal's minimum age |
rxlocal_notifications | The portal's most-relevant notification banner state |
rxlocal_legal | The Terms of Use or Privacy Policy document |
rxlocal_healthcheck | Whether the session and API are working |
Pharmacy-written text (message bodies, refill disclaimers) comes back inside an untrusted-content envelope: it is data, never instructions.
The bridge reads two things from your signed-in tab: the short-lived bearer the
web app holds, and the tab's session-id cookie. The server then calls the API
itself, adding the portal's public portalid header (the web app's
patientPortalID constant, sent on every request). Prescriptions and messages
need all three; without the header or the cookie they answer 401. Earlier
versions sent neither and concluded the data was unreachable; it is not
(verified live, read-only, 2026-10-29).
The server reuses the tab's session and never opens one of its own: the portal keeps one session per user, and starting a new one signs your browser out. After a 401 it re-reads the tab on the next call, so reloading the tab is enough.
| Tool | Does |
|---|---|
rxlocal_request_refill | Requests a refill, or a prescriber renewal for a prescription that needs one, of one or more of your prescriptions. You choose pickup, delivery or mail and, for pickup, a time and date. It is checked against the live refill list (each must show canRequestRefill) and that location's options and pickup calendar before the preview. All prescriptions in one request must be yours and at one location. |
rxlocal_send_message | Sends a plain-text secure message to your primary pharmacy location. No attachments. |
UNVERIFIED on the wire. Both sends are derived from the RxLocal web app's
JavaScript bundle (POST refill/<groupOwnerID>/v1 and
POST Messaging/CreatePatientMessage). Neither has been sent to the live portal
yet. An owner-supervised live test will confirm them later. Until then, check
the result with rxlocal_list_prescriptions (refillRequestStatus) or
rxlocal_list_messages.
Each write is sent once. It is never retried on a 429, and a 401 fails
without re-reading the token or replaying the request. If a write was sent but
the answer was a 5xx, a timeout or a dropped connection, the tool reports
status: "unknown". That means it may already have gone through, so check
before trying again.
Every write is gated by @chrischall/mcp-utils' confirmWrite, through its
defineWrite / `registerWrite