Remote MCP · Endpoint

xyz.crossgrain/epitaxy MCP server

Yes, as of 2 hours ago: the TLS certificate could not be verified.

DownLast checked 2 hours ago

Server URL

https://drugs.crossgrain.xyz/v1/mcp

The last check failed: the TLS certificate could not be verified.

Registry name
xyz.crossgrain/epitaxy
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
5 tools
Uptime, last 30 days
57.9% from 19 checks
Described by its publisher as
Federal drug shortages and recalls joined to the federal contracts that buy those drugs.
Website
https://drugs.crossgrain.xyz/docs
Repository
https://github.com/vor-bot/epitaxy-mcp
Listing
From the official MCP registry (active).
Recent checks of xyz.crossgrain/epitaxy
CheckedResultHandshake
2 hours agoFailed - the TLS certificate could not be verified—
1 day agoFailed - the TLS certificate could not be verified—
2 days agoFailed - the TLS certificate could not be verified—
3 days agoFailed - the TLS certificate could not be verified—
4 days agoFailed - the TLS certificate could not be verified—
5 days agoFailed - the TLS certificate could not be verified—
6 days agoFailed - the TLS certificate could not be verified—
8 days agoFailed - the TLS certificate could not be verified—
11 days agoHandshake completed133 ms
13 days agoHandshake completed152 ms
15 days agoHandshake completed136 ms
18 days agoHandshake completed149 ms
20 days agoHandshake completed141 ms
22 days agoHandshake completed147 ms
24 days agoHandshake completed166 ms
26 days agoHandshake completed141 ms
27 days agoHandshake completed142 ms
29 days agoHandshake completed146 ms
29 days agoHandshake completed135 ms

The last 19 checks. Full history is kept for 30 days; the all-time counter stands at 21 responding of 29.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with xyz.crossgrain/epitaxy and makes no claim about it beyond what these checks measured.