MCP.Market

Epitaxy MCP server

not responding
by crossgrain.xyz·xyz.crossgrain/epitaxy·v0.1.4
No reviews yet

Federal drug shortages and recalls joined to the federal contracts that buy those drugs.

C60/100grade C
Write a reviewRun it
What users say
No reviews yet
Be the first
Safety scan
C60/100

full report

Adoption
Growing

0 stars34 downloads/wk

Reviews

Write one

Nobody has reviewed Epitaxy yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Epitaxy tools (5)

write = sends, deletes, buys or posts
  • get_data_freshnessFree

    Returns when the data was last activated, how many segments are live, and the state of the last run. Call this first when you need to know whether the data is fresh.

  • get_supplier_exposureFree

    The join: a federal contract whose supplier has an FDA shortage or recall. Every row carries company_name, confidence (exact, probable or weak) and match_method. A cross source join is NEVER exact, because FDA and USAspending share no identifier. The claim is: this government supplier has an active FDA shortage or recall. It does NOT claim that this contract delivers that drug. Without a key you get exact and probable matches only, at most 20 rows, without the evidence field.

  • list_drug_recallsFree

    FDA drug recalls and enforcement reports. Filters: classification (Class I, II, III), company_id, limit.

  • list_drug_shortagesFree

    Current and resolved US drug shortages as reported by the FDA. Each row carries the generic name, the reporting company and its company_id. Filters: status, generic_name, company_id, limit.

  • list_federal_drug_contractsFree

    US federal contracts for drugs, product service code 6505, from USAspending. Filters: agency, company_id, limit.

Public scan report

scanner v0.1.10 · 2026-10-29 · same rubric, same numbers if you re-run it

1 high
  • Code scan3 source files scanned25/25
  • Live reliabilityremote unreachable: TypeError: fetch failed0/20
  • –Tool poisoningtools not inspected (endpoint requires auth); not countedn/a
  • Auth qualitystatic API keys via environment variables6/15
  • Maintenancelast push 50 days ago12/15
  • Maintainer identityendpoint served from the registry-verified namespace domain8/10

Findings (1)

  • highRemote endpoint did not respondreliability.unreachable

    TypeError: fetch failed

Overall 60/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Epitaxy compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
60/100
higher than 15% of 48,243 servers
Tools
5
the typical server has 7
Tools that change things
0%
typical: 0%. Fewer write tools means less an agent can break
Uptime
11%
of our recent checks; the typical remote server answers 100%
Response time
204 ms
faster than 66% of 30,027 servers
Downloads a week
34
more than 23% of 12,306 servers with a package

What its tools let an agent do: 5 read

Install Epitaxy in Claude Code, Cursor or VS Code

claude mcp add --transport http epitaxy https://drugs.crossgrain.xyz/v1/mcp
Add to Cursor

What the publisher says

From the Epitaxy repository's README, as published. We do not edit it. Read it on GitHub

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": "TEVA PHARMACEUTICALS USA, INC.",
 "company_key": "teva pharmaceuticals usa",
 "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: getdatafreshness, listdrugshortages, listdrugrecalls, listfederaldrugcontracts, getsupplier_exposure.

Read the confidence field, always

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 segmentnotlive, it never returns another segment's data. An address that has been published is never withdrawn.

Paid

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

Nothing above is checked by us. What we check is on the safety report.

Grade history

  • 2026-10-29downgradeA → Cscore 60: Remote endpoint did not respond

Epitaxy: common questions

Is Epitaxy MCP server safe?
With care: it is graded C, so read the findings first (60/100). Read the Epitaxy safety report
How do I install Epitaxy?
It runs remotely at drugs.crossgrain.xyz. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does Epitaxy need an API key?
Yes. The registry entry asks for EPITAXY_API_KEY.
Is Epitaxy maintained?
The last commit was 58 days ago (2026-09-08). The latest release is v0.1.4.
Is Epitaxy up?
11% of our last 28 checks got an answer. We check remote servers about four times a day.
How does Epitaxy compare with other MCP servers?
safety score 60/100 (higher than 15% of 48,243 servers); tools 5 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.