xyz.crossgrain/epitaxy
PYPI · EPITAXY-MCP · 2 COMPONENTS · SCANNED SEP 20
Federal drug shortages and recalls joined to the federal contracts that buy those drugs.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs setuptools.build_meta at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 11 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability72
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 439 tokens (~87/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management40
- Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage74
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 21% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the xyz.crossgrain/epitaxy MCP server?
xyz.crossgrain/epitaxy runs locally as a PyPI package, launched with uvx epitaxy-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · epitaxy-mcp
claude mcp add xyz-crossgrain-epitaxy -- uvx epitaxy-mcp
{
"mcpServers": {
"xyz-crossgrain-epitaxy": {
"command": "uvx",
"args": [
"epitaxy-mcp"
]
}
}
} {
"servers": {
"xyz-crossgrain-epitaxy": {
"command": "uvx",
"args": [
"epitaxy-mcp"
]
}
}
} codex mcp add xyz-crossgrain-epitaxy -- uvx epitaxy-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"xyz-crossgrain-epitaxy": {
"type": "local",
"command": [
"uvx",
"epitaxy-mcp"
],
"enabled": true
}
}
} openclaw mcp add xyz-crossgrain-epitaxy --command uvx --arg epitaxy-mcp
mcp_servers:
xyz-crossgrain-epitaxy:
command: "uvx"
args: ["epitaxy-mcp"] {
"McpServers": {
"xyz-crossgrain-epitaxy": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"epitaxy-mcp"
]
}
}
} assistant mcp add xyz-crossgrain-epitaxy -t stdio -c uvx -a epitaxy-mcp
{
"mcpServers": {
"xyz-crossgrain-epitaxy": {
"command": "uvx",
"args": [
"epitaxy-mcp"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 +4
- Stability: unverified → 0.27 ▲ functional
- 15 Sept 26 +15
- Malware scan: unverified → pass ▲ security
- 14 Sept 26 −15
- Malware scan: pass → unverified ▼ security
- 9 Sept 26 +15
- Malware scan: unverified → pass ▲ security
- 8 Sept 26 51
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Analysed pypi/epitaxy-mcp@0.1.4
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | setuptools.build_meta |
Background: Why install scripts are a supply-chain risk →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_data_freshness ~47
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_supplier_exposure ~149
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.
| Name | Type | Req | Description |
|---|---|---|---|
| award_id | string | – | federal award identifier |
| company_id | string | – | – |
| limit | integer | – | – |
| min_confidence | string | – | weak needs a paid key |
No output schema declared.
No examples provided.
list_drug_recalls ~56
FDA drug recalls and enforcement reports. Filters: classification (Class I, II, III), company_id, limit.
| Name | Type | Req | Description |
|---|---|---|---|
| classification | string | – | – |
| company_id | string | – | – |
| limit | integer | – | – |
No output schema declared.
No examples provided.
list_drug_shortages ~86
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.
| Name | Type | Req | Description |
|---|---|---|---|
| company_id | string | – | – |
| generic_name | string | – | – |
| limit | integer | – | – |
| status | string | – | for example Current or Resolved |
No output schema declared.
No examples provided.
list_federal_drug_contracts ~62
US federal contracts for drugs, product service code 6505, from USAspending. Filters: agency, company_id, limit.
| Name | Type | Req | Description |
|---|---|---|---|
| agency | string | – | – |
| company_id | string | – | – |
| limit | integer | – | – |
No output schema declared.
No examples provided.
What is the xyz.crossgrain/epitaxy MCP server?
xyz.crossgrain/epitaxy is an MCP server listed in the public MCP registry as xyz.crossgrain/epitaxy. Federal drug shortages and recalls joined to the federal contracts that buy those drugs. This page covers its PyPI package (epitaxy-mcp).
Is the xyz.crossgrain/epitaxy MCP server safe to use?
xyz.crossgrain/epitaxy scores 72 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the xyz.crossgrain/epitaxy MCP server expose?
xyz.crossgrain/epitaxy exposes 5 tools: get_data_freshness, list_drug_shortages, list_drug_recalls, list_federal_drug_contracts, get_supplier_exposure. Their descriptions and schemas cost roughly 400 tokens of context every time the server is loaded.
Is the xyz.crossgrain/epitaxy MCP server still maintained?
xyz.crossgrain/epitaxy is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the xyz.crossgrain/epitaxy MCP server under?
xyz.crossgrain/epitaxy declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.