loupe

loupe

Unifies five public US-government drug datasets into a single sourced page per GLP-1/cardiometabolic drug, providing cost, shortage, label, and alternatives. The MCP server exposes the same Drug contract as the UI for agent-native access.

Category
Visit Server

README

loupe

Appraise the real value. One canonical, sourced page per GLP-1 / cardiometabolic drug — real acquisition cost, live FDA shortage status, verbatim label facts, and same-class alternatives — unified from five free, keyless, public-domain US-government datasets. Built agent-native: deep-links, copy-as-API on every panel, and an MCP server return the same Drug contract the human UI renders.

Not medical advice. loupe is not affiliated with the FDA, NLM, or CMS. Drug-PRODUCT reference data only — zero PHI.

What it does

loupe unifies five public-domain US-government drug datasets into one sourced page per GLP-1 / cardiometabolic drug: the NADAC acquisition cost, current FDA shortage status, verbatim label facts, and same-class alternatives — each value carrying its source and as-of date.

Guardrails

A guardrail that isn't enforced by the type system, a runtime guard, and a test does not exist.

  1. Never dose-advise, never recommend a switch — alternatives are clinician-gated.
  2. Cost ≠ copay — NADAC is acquisition cost; every price carries cost_basis.
  3. FAERS = reports, not rates — never an incidence rate, never a denominator.
  4. Labels are quoted verbatim with source + as-of date. No paraphrase, ever.
  5. Honest loading / empty / error / stale states on all data.
  6. Explicit "not medical advice / not affiliated" disclosure across UI, API, and MCP.

Architecture — one contract, three faces

A build-time prefetch (scripts/prefetch.ts) fans out to all upstreams, validates each record with Drug.parse(), and commits a static catalog (src/data/snapshot/*.json). The SPA, the Hono read API, and the MCP server all read that one Drug contract (src/core/schema.ts) — nobody live-hits the upstreams at request time, so the demo is deterministic and no rate-limit budget bites. Snapshots omit the guardrail literals; Drug.parse() back-fills them on read, so a snapshot can never ship a tampered disclaimer (enforced by src/core/literals.test.ts).

upstreams ──prefetch──▶ src/data/snapshot/*.json ──▶ Drug (src/core/schema.ts)
  openFDA ×4                                            │      │       │
  RxNorm/RxClass                                      SPA   Hono /v1  MCP (stdio)
  CMS NADAC + Part D                            (bundled)  (agents)  (agents)
  DailyMed                                  toApiCall(DrugQuery) → curl/python/ts + deep-link

Run it

npm install
npm run prefetch     # rebuild the catalog from live upstreams (committed; optional)
npm run dev          # SPA  → http://localhost:3001
npm run api          # API  → http://localhost:8787  (also serves the built SPA)
npm run mcp:smoke    # spawns the MCP server and runs the "can I afford Zepbound?" example
npm test             # vitest: contract, snapshot-literal invariant, guardrail-render, UI
npm run test:coverage # the above + a coverage gate on the request-time logic (CI-enforced)
npm run build        # tsc --noEmit && vite build

Agent surfaces

  • Read API (keyless): GET /v1/drugs, /v1/drugs/{slug}, /v1/drugs/{slug}/{panel}, /v1/search?q= · OpenAPI at /openapi.json · docs at /docs.
  • Discovery: /llms.txt and /.well-known/navigator.json.
  • MCP (stdio) — add to an MCP client:
    { "mcpServers": { "loupe": { "command": "npx", "args": ["tsx", "src/mcp/server.ts"] } } }
    
    Tools: get_drug, list_drugs, search_drugs, get_drug_cost, get_drug_shortage, get_drug_label, get_drug_alternatives.

Deploy

One container serves both faces (the SPA bundles its own catalog; the API serves /v1):

docker build -t loupe . && docker run -p 8787:8787 loupe
# → http://localhost:8787  (SPA at /, API at /v1, docs at /docs)

Snapshots are committed, so the image builds with no network. To refresh, run npm run prefetch and redeploy.

Example

/?drug=tirzepatide-zepbound&view=cost opens the cost view for Zepbound. The same data is available without the UI — GET /v1/drugs/tirzepatide-zepbound/cost, the get_drug_cost MCP tool, or a panel's "copy as API" snippet — each returns the same Drug projection.

Key decisions

  • Build-time static catalog, not live per-request fetch — fixes deterministic demo + the openFDA 1000/day shared-IP wall + Lambda cold-cache in one move.
  • est. $/mo only when it needs no clinical assumption (oral, dose-countable). For mL-priced injectables it's withheld; the factual package cost is shown instead.
  • Approval = "an SPL exists" + has_boxed_warning — we never algorithmically infer off-label/withdrawn (that would manufacture a regulatory claim).
  • NDC normalized to 11-digit 5-4-2 before the NADAC join (classic silent-fail point).

See docs/SPEC.md for the full data contract and rationale.

License

Apache License 2.0. The underlying datasets are public-domain US-government works (FDA, NLM, CMS); loupe is not affiliated with those agencies.

Recommended Servers

playwright-mcp

playwright-mcp

A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.

Official
Featured
TypeScript
Magic Component Platform (MCP)

Magic Component Platform (MCP)

An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.

Official
Featured
Local
TypeScript
Audiense Insights MCP Server

Audiense Insights MCP Server

Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.

Official
Featured
Local
TypeScript
VeyraX MCP

VeyraX MCP

Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.

Official
Featured
Local
graphlit-mcp-server

graphlit-mcp-server

The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.

Official
Featured
TypeScript
Kagi MCP Server

Kagi MCP Server

An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.

Official
Featured
Python
E2B

E2B

Using MCP to run code via e2b.

Official
Featured
Neon Database

Neon Database

MCP server for interacting with Neon Management API and databases

Official
Featured
Exa Search

Exa Search

A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.

Official
Featured
Qdrant Server

Qdrant Server

This repository is an example of how to create a MCP server for Qdrant, a vector search engine.

Official
Featured