HyppoHealth MCP Server
A free, public, no-auth remote MCP server that lets AI agents query US health-insurance data directly. It speaks the Streamable HTTP transport and is built from a small set of focused tools designed to be token-efficient.
https://www.hyppohealth.com/api/mcp
Connecting
Any MCP client that supports remote (Streamable HTTP) servers can connect with just the URL. Add this to your client configuration:
{
"mcpServers": {
"hyppohealth": {
"url": "https://www.hyppohealth.com/api/mcp"
}
}
}For stdio-only clients, bridge to the remote server with mcp-remote:
{
"mcpServers": {
"hyppohealth": {
"command": "npx",
"args": ["mcp-remote", "https://www.hyppohealth.com/api/mcp"]
}
}
}Or list the tools directly with curl:
curl -s https://www.hyppohealth.com/api/mcp \
-H "Content-Type: application/json" \
-H "Accept: application/json, text/event-stream" \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/list","params":{}}'Tools
search_insurance_plans
Find ACA/Marketplace plans for a US ZIP. Returns name, issuer, metal tier, premium, and deductible; State-Based Marketplace ZIPs return the official enrollment URL.
Input: zipCode: string (5 digits), limit?: number (1-25)
search_hospitals
Find hospitals near a coordinate, nearest first, with name, address, rating, and distance.
Input: lat: number, lng: number, radiusMiles?: number (1-50), limit?: number
lookup_medical_term
Plain-language definition of a medical or insurance term, or spelling suggestions when not found.
Input: term: string (2-80 chars)
find_drug_alternatives
Brand names, generic ingredients, and related drugs from NIH RxNav. Informational only; not medical advice.
Input: drug: string (2-80 chars)
Low-token design
Every tool definition a server exposes is loaded into the model context up front and stays there for the whole session - so the tool surface is a fixed token tax paid on every request. Following Cloudflare's guidance on token-efficient MCP servers, this server is built to keep that tax small:
- A small, fixed tool surface. Four tools, not one per upstream endpoint. The cost of an MCP server scales with the number of tool definitions, not the size of the data behind it.
- Tight, one-line descriptions and schemas. Each description states what the tool returns and its key constraint - no marketing prose, no schema restated in English.
- Responses shaped server-side. Tools field-select and limit results before returning, so full upstream payloads never enter the model context.
- Work composed in code. Multi-step lookups happen inside a single tool call rather than bouncing intermediate results through the model.
Discovery
- Server card: /.well-known/mcp/server-card.json
- AI index: /llms.txt
Notes and limits
This server is informational and not medical, legal, or financial advice. Plan and pricing data come from the CMS Marketplace API and may differ from a final enrollment quote. Drug data comes from NIH RxNav. Always verify coverage details during enrollment.