Health · Remote MCP server
Hormonaly Clinical Intelligence
24 tools for evidence-graded clinical queries, hormones, peptides, longevity & drug interactions.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.Hormonaly-ai/hormonaly- Version
- 1.0.4
- Status
- Active
- Category
- health
- Transport
- Streamable HTTP, SSE (HTTP + Server-Sent Events)
- Published
- 2026-05-27
- Updated
- 2026-05-27
- Publisher
- Hormonaly-ai (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/Hormonaly-ai) · how
- Website
- hormonaly.ai
- Repository
- github.com/Hormonaly-ai/hormonaly-public
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://mcp.hormonaly.ai/mcp | x-api-key (required, secret) |
| SSE (HTTP + Server-Sent Events) | https://mcp.hormonaly.ai/sse | x-api-key (required, secret) |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Endpoint
https://mcp.hormonaly.ai/mcp(HTTP)- Reachable
- Yes (HTTP 403)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 403
- Checked on
- 2026-10-05
- Endpoint
https://mcp.hormonaly.ai/sse(SSE)- Reachable
- Yes (HTTP 403)
- SSE stream
- Not opened: sign-in required
- Sign-in required
- Yes - HTTP 403
- Checked on
- 2026-10-05
How to connect Hormonaly Clinical Intelligence
Hormonaly Clinical Intelligence is a remote MCP server: there is nothing to install. Its endpoint is https://mcp.hormonaly.ai/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
It also lists an endpoint on the older SSE transport https://mcp.hormonaly.ai/sse. Clients that support remote servers generally still accept SSE endpoints, though the protocol now favours Streamable HTTP.
The registry entry declares an HTTP header for the connection: x-api-key (required, secret). A secret header usually carries an API key or token issued by the service; clients that accept custom headers set it with the server's URL.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More health servers
| Server | Runs |
|---|---|
| Hevy MCP (Remote)Hosted/gateway-ready Hevy fitness MCP: workouts, routines, templates. | Local · HTTP |
| Hevy MCP ServerMCP server for managing workouts, routines, and exercise data through the Hevy API. | Local · stdio |
| Hl7 Fhir Bridge MCPHL7 v2 / FHIR healthcare bridge - parse, map, validate, govern PHI (HIPAA/MDR). | Local · stdio |
| HLA-VerifyHLA nomenclature and match checks against a pinned IPD-IMGT/HLA release. No patient identifiers. | Remote · HTTPLive check: ✓ handshake |
| hypokratesPharmacovigilance hypothesis generation from 15 public drug safety databases. | Local · stdio |
| Icf MCPWHO ICF codes: lookup, search, hierarchy, qualifiers, and 11 scored clinical assessment instruments. | Remote · HTTPLive check: ✓ handshake |
| IdkRxReport pharmacy stock, and post a pharmacy's verified status, from your AI assistant. | Remote · HTTPLive check: sign-in required |
| Igpsport MCPIGPSport cycling data with training metrics (NP/IF/TSS/CTL/ATL/TSB) and workout generation. | Local · stdio |