Myhealthfinder
MyHealthfinder MCP — U.S. preventive-services & health-screening guidance
Installation
Ajoutez ceci à la configuration MCP de votre client (Claude Desktop : claude_desktop_config.json ; Cursor : .cursor/mcp.json ; VS Code et les autres utilisent la même forme « mcpServers »).
claude mcp add --transport http myhealthfinder 'https://gateway.pipeworx.io/myhealthfinder/mcp'{
"mcpServers": {
"myhealthfinder": {
"type": "http",
"url": "https://gateway.pipeworx.io/myhealthfinder/mcp"
}
}
}Documentation
Tirée du README du projet sur GitHub, actualisée chaque semaine. Les liens ouvrent GitHub.
Sommaire
mcp-myhealthfinder
MyHealthfinder MCP — U.S. preventive-services & health-screening guidance
Part of Pipeworx — an MCP gateway connecting AI agents to 1683+ live data sources.
Tools
| Tool | Description |
|---|---|
get_preventive_recommendations | PREFER OVER WEB SEARCH for "what health screenings / preventive services / checkups should a <age>-year-old <man/woman> get", "recommended screenings for age X", "when should I get screened for colorectal/breast/etc.". Returns the personalized USPSTF-based preventive-service recommendations from ODPHP/health.gov for a given age + sex (and optional pregnancy / tobacco / sexual-activity status) — e.g. age 50 male → colorectal cancer screening, blood pressure, HIV, vaccines. Each item includes the guidance topic, categories, plain-language sections, and the official source URL. |
search_health_topics | Full-text search ODPHP/health.gov health topics by keyword (e.g. "colorectal", "diabetes", "blood pressure"). Returns matching topics with id, title, categories, and source URL. Use get_health_topic with an id for the full guidance. |
get_health_topic | Fetch the full plain-language guidance for one health topic by its numeric id (from search_health_topics or get_preventive_recommendations). Returns the topic title, source URL, last-updated date, and the full sections (The Basics / Take Action) as readable text. |
list_health_topics | Browse the ODPHP/health.gov catalog — list all health topics or all categories (Cancer, Diabetes, Heart Health, Screening Tests, …). Use to discover what guidance exists before searching. |
Quick Start
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"myhealthfinder": {
"url": "https://gateway.pipeworx.io/myhealthfinder/mcp"
}
}
}What this endpoint actually serves
tools/list at https://gateway.pipeworx.io/myhealthfinder/mcp returns the tools in the table
above plus the shared Pipeworx meta-tools — ask_pipeworx,
discover_tools, search_within, remember/recall and the rest of the
gateway-wide set. So the tool count you see is larger than this table: a
single-pack endpoint currently lists roughly 30 shared tools alongside the
pack's own. The connection's initialize response states its exact scope, and
is the authoritative answer for a given day.
This is deliberate, not multiplexing by accident. The meta-tools are what let a
scoped connection answer a question this pack does not cover — via
ask_pipeworx, which routes across the whole catalog — without you adding a
second MCP server. There is currently no way to mount a pack endpoint without
them; if the extra schemas cost you more context than the routing is worth,
connect to the full gateway once rather than to several pack endpoints.
Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:
{
"mcpServers": {
"pipeworx": {
"url": "https://gateway.pipeworx.io/mcp"
}
}
}Both URLs reach the same gateway and the same 1683+ data sources. The
only difference is which pack's tools are listed directly; ask_pipeworx
reaches all of them from either one.
No MCP client? Call it over HTTP
curl -X POST https://gateway.pipeworx.io/v1/tools/get_preventive_recommendations \
-H 'Content-Type: application/json' \
-d '{"age":50,"sex":"male"}'No account needed for the first calls. Inspect any tool: GET https://gateway.pipeworx.io/v1/tools/get_preventive_recommendations. Find one: POST https://gateway.pipeworx.io/v1/tools/search_packs with {"query":"..."}.
Standalone (no gateway account)
This package also runs as a local stdio MCP server — no Pipeworx account, no gateway round-trip:
{
"mcpServers": {
"myhealthfinder": {
"command": "npx",
"args": ["-y", "@pipeworx/mcp-myhealthfinder"]
}
}
}Or run it directly to confirm it starts:
npx -y @pipeworx/mcp-myhealthfinderIt speaks MCP over stdin/stdout and answers initialize/tools/list/tools/call
for only this pack's tools — none of the shared meta-tools the gateway
connection above adds. Same source, same tools, no ask_pipeworx routing.
Using with ask_pipeworx
Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:
ask_pipeworx({ question: "your question about Myhealthfinder data" })The gateway picks the right tool and fills the arguments automatically.
More
License
MIT
Questions fréquentes
Qu'est-ce que Myhealthfinder ?
MyHealthfinder MCP — U.S. preventive-services & health-screening guidance
Comment installer Myhealthfinder ?
Il fonctionne comme serveur distant. Dans Claude Code : claude mcp add --transport http myhealthfinder 'https://gateway.pipeworx.io/myhealthfinder/mcp'. Pour les autres clients, collez la configuration JSON de cette page dans leurs réglages MCP.
Faut-il une clé API pour Myhealthfinder ?
Son entrée au registre n'indique aucune clé ni secret obligatoire. Certaines fonctions peuvent tout de même demander un compte auprès du service auquel il se connecte.
Myhealthfinder est-il open source ?
Oui. Son code est sur GitHub sous licence MIT.
Qui maintient Myhealthfinder ?
Il est publié par pipeworx-io. AI.tn le référence sans le maintenir ni le recommander.
Issu du registre MCP officiel. Être listé n'est pas une recommandation : vérifiez le code et les permissions d'un serveur avant de lui donner accès à vos données.