Mirobody
Lab results to LOINC codes and UCUM units, symptoms and diagnoses to ICPC-3. Offline, no API key.
Descripción del creador (original en inglés)
RxLocal pharmacy portal MCP — prescriptions, messages, confirm-gated refill requests
Estos tres nunca se combinan en una sola puntuación: las opiniones, las mediciones y la popularidad son cosas distintas.
Todavía no escribimos un resumen sencillo para este. Abajo están los datos que leímos del registro.
Elige la app de IA que usas y copia la configuración.
RXLOCAL_DISABLE_FETCHPROXY, FETCHPROXY_WS_PORT, FETCHPROXY_WS_HOST, FETCHPROXY_IDENTITY_DIRNecesitas
¿Qué app usas?
Elige tu app arriba. La recordamos, así que la próxima vez el botón dirá “Instalar en …”.
Abre Claude Desktop → Settings → Developer → Edit Config y pega esto en claude_desktop_config.json
{
"mcpServers": {
"rxlocal": {
"command": "npx",
"args": [
"-y",
"rxlocal-mcp"
],
"env": {
"RXLOCAL_DISABLE_FETCHPROXY": "your-value",
"FETCHPROXY_WS_PORT": "your-value",
"FETCHPROXY_WS_HOST": "your-value",
"FETCHPROXY_IDENTITY_DIR": "your-value"
}
}
}
}Ejecuta esto en tu terminal
claude mcp add rxlocal --env RXLOCAL_DISABLE_FETCHPROXY=your-value --env FETCHPROXY_WS_PORT=your-value --env FETCHPROXY_WS_HOST=your-value --env FETCHPROXY_IDENTITY_DIR=your-value -- npx -y rxlocal-mcpCompleta los valores vacíos antes de ejecutarlo.
Pégalo en .cursor/mcp.json de tu proyecto, o en ~/.cursor/mcp.json
{
"mcpServers": {
"rxlocal": {
"command": "npx",
"args": [
"-y",
"rxlocal-mcp"
],
"env": {
"RXLOCAL_DISABLE_FETCHPROXY": "your-value",
"FETCHPROXY_WS_PORT": "your-value",
"FETCHPROXY_WS_HOST": "your-value",
"FETCHPROXY_IDENTITY_DIR": "your-value"
}
}
}
}Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.
Pégalo en .vscode/mcp.json de tu proyecto
{
"servers": {
"rxlocal": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"rxlocal-mcp"
],
"env": {
"RXLOCAL_DISABLE_FETCHPROXY": "your-value",
"FETCHPROXY_WS_PORT": "your-value",
"FETCHPROXY_WS_HOST": "your-value",
"FETCHPROXY_IDENTITY_DIR": "your-value"
}
}
}
}Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.
Este se ejecuta en tu computadora, y ChatGPT solo puede conectarse a servidores en internet. Elige otra app.
Tu elección se guarda en una cookie en este dispositivo; no necesitas cuenta.
RXLOCAL_DISABLE_FETCHPROXY envFETCHPROXY_WS_PORT envFETCHPROXY_WS_HOST envFETCHPROXY_IDENTITY_DIR envEsta configuración se genera a partir de la ficha del creador en el registro. Si el README dice otra cosa, sigue el README.
Se ejecuta en tu computadora; la lista de herramientas aparece en tu app de IA después de instalarlo.
Revisamos información que cualquiera puede ver; no hemos leído el código. Las revisiones que no aplican no se cuentan. · Revisado el 7 nov 2026
El nombre en el registro se verificó con la cuenta de GitHub chrischall, dueña del repo
Todavía no hemos leído este repo en GitHub
Todavía no hemos leído este repo en GitHub
Este se ejecuta en tu computadora; no hay endpoint en internet
Se ejecuta en tu computadora y usa ajustes locales en su lugar
Se ejecuta en tu computadora; solo podemos leer listas de herramientas de endpoints en internet
Comparado con todos los servidores activos de esta categoría en el registro. Las estrellas solo cuentan cuando quien lo publica es dueño del repo.
Superó 1 de 1 revisiones básicas aplicables. No hemos leído el código. Antes de agregar una clave o un token, revisa qué acceso pide el servidor y usa una clave que tenga solo los permisos que necesitas.
El registro no indica ninguna clave obligatoria, aunque algunos servidores te piden iniciar sesión la primera vez que los usas.
Se ejecuta en tu computadora. Tu app de IA lo inicia cuando hace falta, y los datos no pasan por los servidores del creador (a menos que el propio servidor llame a un servicio en línea).
El repo de GitHub cambió por última vez –, y la última versión (0.3.1) llegó al registro hace 3 días.
Las apps compatibles con MCP, como Claude Desktop, Claude Code, Cursor y VS Code. También necesitas Node.js en tu computadora.
En la misma categoría: Mirobody, FHIR MCP Server, Google Health MCP
Servidores de la misma categoría hechos por otros creadores, ordenados por estrellas.
Cómo leer una tarjeta:★ Estrellas de GitHubiTres pilares: reseñas · revisiones · usoiActualizado = fecha en que se publicó la última versión en el registroi
Lab results to LOINC codes and UCUM units, symptoms and diagnoses to ICPC-3. Offline, no API key.
MCP server providing seamless access to FHIR APIs for AI tools and healthcare applications
Privacy-first unofficial Google Health API v4 MCP server for health, sleep, activity, HR agents
Copiado tal cual del repo del creador. PopNx MCP no lo ha revisado ni lo respalda. Se quitaron HTML, imágenes y scripts. Los enlaces llevan fuera de este sitio.
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/ /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. The first call reads the portal to validate, sends nothing, and returns a preview + a `confirmToken`. Only a second call carrying that token sends, and only after you approve the preview. The exact request body and the shown preview are bound into the token, so an argument or portal state that changed since the preview is refused as DRAFT_CHANGED. MCP_CONFIRM_MODE / MCP_CONFIRM_ELICITATION tune this (see the env table).
No credential is configured in the environment — the server reads the short-lived Keycloak token from the signed-in tab via the ContextMint Bridge browser extension. Install the extension, sign in to patient.rxlocal.com, keep that tab open, and approve the one-time pair code the first tool call prints.
// .mcp.json
{ "mcpServers": { "rxlocal": { "command": "npx", "args": ["-y", "rxlocal-mcp"] } } }
| Variable | Purpose |
|---|---|
RXLOCAL_DISABLE_FETCHPROXY | Set to 1 to refuse the browser-bridge read (CI/headless). Every tool then fails, since there is no other credential path. |
FETCHPROXY_WS_PORT | Localhost port of the fetchproxy concentrator the extension connects to (default 37149). Shared by every MCP on the machine. |
FETCHPROXY_WS_HOST | Bind interface for the concentrator, a literal IP (default 127.0.0.1). |
FETCHPROXY_IDENTITY_DIR | Where the fetchproxy identity keypair is stored (default ~/.fetchproxy/identity/). |
MCP_CONFIRM_MODE | Confirm-gate mode for every write (default ask-user). ask-user = preview + confirmToken round-trip; auto lets a capable host confirm in one step; an unrecognised value fails closed (refuse). |
MCP_CONFIRM_ELICITATION | on (default) lets the host confirm a write interactively; off forces the confirmToken round-trip. |
A lightweight fpx skill ships under skills/rxlocal-fpx/, with no MCP process required. It covers the reads: profile, age gate, prescriptions, refill options, messages and notifications. It sends nothing.
npm install
npm run build npm test # typecheck + vitest, fully mocked, no network