Skip to main content
ClaudeWave
TemplatesOfficial Registry0 stars0 forksPythonMITUpdated today
ClaudeWave Trust Score
77/100
Trusted
Passed
  • Open-source license (MIT)
  • Actively maintained (<30d)
  • Documented (README)
Flags
  • !No description
Last scanned: 9/9/2026
Use as a project template
Method: Clone
Terminal
git clone https://github.com/vor-bot/epitaxy-mcp my-project && cd my-project
1. Clone the template into a new project directory.
2. Follow the README setup (install dependencies, set environment variables).
3. Open it with Claude Code and start building.
Use cases

Templates overview

# 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

What people ask about epitaxy-mcp

What is vor-bot/epitaxy-mcp?

+

vor-bot/epitaxy-mcp is templates for the Claude AI ecosystem with 0 GitHub stars.

How do I install epitaxy-mcp?

+

You can install epitaxy-mcp by cloning the repository (https://github.com/vor-bot/epitaxy-mcp) or following the README instructions on GitHub. ClaudeWave also provides quick install blocks on this page.

Is vor-bot/epitaxy-mcp safe to use?

+

Our security agent has analyzed vor-bot/epitaxy-mcp and assigned a Trust Score of 77/100 (tier: Trusted). See the full breakdown of passed checks and flags on this page.

Who maintains vor-bot/epitaxy-mcp?

+

vor-bot/epitaxy-mcp is maintained by vor-bot. The last recorded GitHub activity is dated 2026-09-08, with 0 open issues.

Are there alternatives to epitaxy-mcp?

+

Yes. On ClaudeWave you can browse similar templates at /categories/templates, sorted by popularity or recent activity.

Deploy epitaxy-mcp to your cloud

Ship this repo to production in minutes. Each platform spins up its own environment with editable env vars.

Maintain this repo? Add a badge to your README

Drop the badge into your GitHub README to show it's tracked on ClaudeWave. Each badge links back to this page and reflects the live Trust Score.

Featured on ClaudeWave: vor-bot/epitaxy-mcp
[![Featured on ClaudeWave](https://claudewave.com/api/badge/vor-bot-epitaxy-mcp)](https://claudewave.com/repo/vor-bot-epitaxy-mcp)
<a href="https://claudewave.com/repo/vor-bot-epitaxy-mcp"><img src="https://claudewave.com/api/badge/vor-bot-epitaxy-mcp" alt="Featured on ClaudeWave: vor-bot/epitaxy-mcp" width="320" height="64" /></a>

More Templates

epitaxy-mcp alternatives