xyz.crossgrain/epitaxy
# epitaxy
mcp-name: xyz.crossgrain/epitaxy
Federal drug shortages and recalls, joined to the federal contracts that
buy those drugs. One call, no signup.
**What it claims:** this government supplier has an active FDA shortage
or recall. **What it does not claim:** that a specific contract supplies
a specific drug. Federal contract descriptions average 47 characters and
almost never name the drug, so we say so instead of pretending otherwise.
## Try it now, no key
```bash
curl https://drugs.crossgrain.xyz/v1/exposure?limit=5
```
One row of the answer, shortened:
```json
{"exposure_id": "0026624dec7b6d9f",
"award_id": "SPE2DP25F109W",
"company_id": "a4fdd4a7530f4962",
"company_name": "TEVA PHARMACEUTICALS USA, INC.",
"company_key": "teva pharmaceuticals usa",
"shortage_id": "022c478fb3af28c4",
"confidence": "probable",
"match_method": "company_name_normalized"}
```
## MCP
Remote, nothing to install:
```json
{ "mcpServers": { "epitaxy": { "url": "https://drugs.crossgrain.xyz/v1/mcp" } } }
```
Local, stdio:
```json
{ "mcpServers": { "epitaxy": { "command": "uvx", "args": ["epitaxy-mcp"] } } }
```
Tools: `get_data_freshness`, `list_drug_shortages`, `list_drug_recalls`,
`list_federal_drug_contracts`, `get_supplier_exposure`.
## Read the confidence field, always
| value | meaning |
| --- | --- |
| `exact` | match on a shared identifier, here an NDC inside FDA data |
| `probable` | normalized company name, or a drug name token in the contract text |
| `weak` | anything softer, an indication only |
Matching on both company and drug at once is **not** promoted to
`exact`. Cross source joins are never `exact`, because FDA and
USAspending share no identifier. Anyone claiming otherwise has a
different source or is guessing.
## Free tier
Works forever, no key, no signup. Returns at most 20 rows, without the
`evidence` field, without `weak` matches, and with data delayed by 24
hours. Nothing is stored: no counters, no IP addresses. If a version
that old does not exist yet, you get the oldest one available, so the
free tier is never empty while data exists.
## Addressing
These two addresses are the same segment and both work permanently:
```
https://drugs.crossgrain.xyz/v1/exposure
https://drugs.crossgrain.xyz/drugs/v1/exposure
```
Later segments arrive as `/devices/v1/...`, `/food/v1/...` and so on. A
path whose segment is reserved but not live yet answers `404` with
`segment_not_live`, it never returns another segment's data. An address
that has been published is never withdrawn.
## Paid
| plan | price | contents |
| --- | --- | --- |
| Starter | 29 USD/mo | 10 000 calls |
| Pro | 99 USD/mo | 100 000 calls plus daily delta feed |
| x402 | 0.004 USD/call | USDC on Base, no signup |
| Bulk dump | 199 USD | one off, Stripe only |
## Sources and licence
- openFDA, public domain, CC0 1.0 Universal
- USAspending, public domain, code under CC0
Data is unvalidated and must not be used for medical decisions.
This project is MIT licensed. Docs: https://drugs.crossgrain.xyz/docs
TDQS
Scored across 5 tools
Each tool targets a clear, distinct concern: shortages, recalls, federal contracts, cross-source supplier exposure, and data freshness. There is no meaningful overlap in purpose, and get_supplier_exposure is explicitly a join/view rather than another list endpoint.
Tool names follow a consistent list_/get_ + noun pattern in snake_case. Collections use list_, single objects and metadata use get_, making the API predictable and easy to navigate.
With 5 tools, the server is tightly scoped to pharmaceutical supply chain risk. Each tool supports a distinct part of the workflow, and none feel redundant or missing enough to make the set feel thin.
The core workflow of finding shortages, recalls, contracts, and supplier exposure is covered well. A minor gap is the lack of a company/detail lookup to discover valid company_id values, and no individual record retrieval, but these are workarounds via filters rather than dead ends.