xyz.crossgrain/epitaxy
REMOTE · DRUGS.CROSSGRAIN.XYZ · 2 COMPONENTS
Federal drug shortages and recalls joined to the federal contracts that buy those drugs.
Available components
Last scanned (2 days ago)
Scores higher than 0% of remote servers
Unreachable for 7 days in a row. Last reached 27 Oct 2026.
Category Health and Science
Recent critical change
TLS certificate (28 Oct 2026). See the changelog before you install this server.
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security11
- TLS check failed: the certificate doesn't match the endpoint's hostname. See how to fix → View diagnostics → Fail
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS not yet verified: we couldn't read the response headers to check for it. View diagnostics → Unverified
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but the TLS certificate failed verification. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
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.
- 3 Nov 26 −15
The score moved with no change recorded against any check. We would rather say so than guess.
- 2 Nov 26 −15
The score moved with no change recorded against any check. We would rather say so than guess.
- 1 Nov 26 −14
The score moved with no change recorded against any check. We would rather say so than guess.
- 31 Oct 26 −15
The score moved with no change recorded against any check. We would rather say so than guess.
- 30 Oct 26 −15
The score moved with no change recorded against any check. We would rather say so than guess.
- 28 Oct 26 0
- TLS certificate: pass → fail ▼ critical
- Score status: scored → failed ▼ critical
- Endpoint reachability: reachable → unreachable ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- HSTS header: fail → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Tool coverage: 100 → unverified ▼ functional
- Capabilities: fail → unverified ▼ functional
- First check of Schema quality: unverified functional
- 9 Oct 26 +2
- Stability: 0.87 → pass security
- 3 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
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 3 Nov 2026 · Probed https://drugs.crossgrain.xyz/v1/mcp
TLS invalid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
Chain error: hostname_mismatch
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.up.railway.app | CN=YE2,O=Let's Encrypt,C=US | 27 Sept 2026 | 26 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 618edc56941aa1165ddb080bf9f799eb7c1 |
| SANs: *.up.railway.app, up.railway.app | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of drugs.crossgrain.xyz. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| xyz. | present | 3599, 18130 | 8, 8 | Verified |
| crossgrain.xyz. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://drugs.crossgrain.xyz/v1/mcp | TLS failed | ||
| http (plaintext) | http://drugs.crossgrain.xyz/v1/mcp | HTTPS enforced | 301 | https://drugs.crossgrain.xyz/v1/mcp |
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.
How do I install the xyz.crossgrain/epitaxy MCP server?
xyz.crossgrain/epitaxy is a hosted endpoint at https://drugs.crossgrain.xyz/v1/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · drugs.crossgrain.xyz
claude mcp add --transport http xyz-crossgrain-epitaxy 'https://drugs.crossgrain.xyz/v1/mcp'
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 hosted endpoint (https://drugs.crossgrain.xyz/v1/mcp).
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.
Does the xyz.crossgrain/epitaxy MCP server require authentication?
Its publisher declares no required credentials for xyz.crossgrain/epitaxy. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the xyz.crossgrain/epitaxy MCP server still maintained?
xyz.crossgrain/epitaxy has been unreachable for long enough that we treat it as dead, and its score is pinned to zero. We last reached this channel on 27 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.