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
curl https://drugs.crossgrain.xyz/v1/exposure?limit=5
One row of the answer, shortened:
{"exposure_id": "0026624dec7b6d9f",
"award_id": "SPE2DP25F109W",
"company_id": "a4fdd4a7530f4962",
"company_name": "PFIZER INC",
"shortage_id": "022c478fb3af28c4",
"confidence": "probable",
"match_method": "company_name_normalized"}
MCP
Remote, nothing to install:
{ "mcpServers": { "epitaxy": { "url": "https://drugs.crossgrain.xyz/v1/mcp" } } }
Local, stdio:
{ "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
Metadata
Release files for epitaxy-mcp 0.1.4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| epitaxy_mcp-0.1.4.tar.gz | 6.1 kB | Without provenance | Details for epitaxy_mcp-0.1.4.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| epitaxy_mcp-0.1.4-py3-none-any.whl | Python 3 | none | any | Details for epitaxy_mcp-0.1.4-py3-none-any.whl |
Total release size: 12.8 kB
Release files / epitaxy_mcp-0.1.4.tar.gz
| Download URL | epitaxy_mcp-0.1.4.tar.gz |
|---|---|
| Size | 6.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f65112a67619f8b1d70c47a94f27a8a4f3f94e1eefe8eb27ae9a8aaa0175fd1a
|
|
BLAKE2b-256 checksum How to use checksums |
1752de1b4c524db7e3068c411240672315321265dc793917d1dd94845a1f4ceb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.9.6
|
Release files / epitaxy_mcp-0.1.4-py3-none-any.whl
| Download URL | epitaxy_mcp-0.1.4-py3-none-any.whl |
|---|---|
| Size | 6.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
4986a2d1b56b378181aee37e60bf3751ee442c0175029826bf119c2ec7bceffc
|
|
BLAKE2b-256 checksum How to use checksums |
ac404c08f78c5c008aa009656566b0f32b78de71135ae65f5dfe1436b5aa22d4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.9.6
|
Security for epitaxy-mcp 0.1.4
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.