Function Health

Read a summary of your Function Health lab results and nutrition protocol.

Add to Agentman Studio

Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.

Paste it into any MCP client. Setup docs

Resources

What the Function Health connector does

The Function Health MCP server connects a Function membership — a consumer lab-testing programme covering 160-plus tests a year — to Claude, ChatGPT and any MCP-compatible agent. It offers three read-only tools: an overall lab-result summary, a per-category breakdown, and your nutrition protocol. Sign-in is OAuth 2.0 through Auth0, with three named read scopes.

Verified connector

Listed by Anthropic as a partner connector in its Connectors Directory.

Connection checked by Agentman on .

Anthropic states this reflects the level of review a connector received, not a security audit.

Function Health tools (3)

  • Health Summary
  • Biomarkers
  • Health Action Plan / Meal Plan

Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.

Limits

  • The connector returns counts, not values. Function states individual lab results are never sent. An agent cannot tell you what your LDL actually was, only that it fell outside range. For numbers, open Function.
  • We read no tool schemas or annotations from the server. The endpoint 403'd every anonymous request, so every parameter and annotation on this page comes from Function's documentation rather than a tools/list response.
  • Neither published list gives the wire identifiers. Anthropic lists display labels, Function's docs give descriptive headings plus three call names in prose. The two sets share no string.
  • The published surface has no history tool. includeTrends is documented as a parameter on the overall summary rather than a separate longitudinal tool, so trend depth is whatever that flag returns — the docs do not say how far back it reaches.
  • No clinician notes, imaging or diagnoses are in scope. MRI & CT Scans appears only as one of 24 biomarker *categories*. Nothing in the surface returns a report, an image, or a physician's interpretation.
  • HIPAA coverage is conditional and Function says so. Its privacy policy states HIPAA does not apply to all personal information it processes. Which regime applies depends on whether you or an employer bought the membership.
  • The free-text context parameter is undocumented in substance. Function describes it only as additional context for personalization and does not state retention or storage.
  • No rate limits are published. Function's documentation names none, and we could not observe any behind the edge block.
  • The documentation is a single page with no version history beyond 1.0.0, dated January 2026. There is no changelog to watch for surface changes.
  • The connector is not medical advice, and Function's own site states it does not provide medical advice, diagnosis or treatment. An agent reasoning over out-of-range counts is generating text, not practising medicine.

Frequently asked questions

Does the Function Health connector expose my individual lab values?

Function's documentation says it does not. The docs state that individual lab test values or specific results, biomarker IDs, email addresses and detailed personal health information are never sent through the connector, and that it retrieves summary-level data only — counts of in-range and out-of-range biomarkers, category names, and nutrition goals. We could not independently verify this, because the endpoint is auth-gated.

Can the Function Health connector change anything in my Function account?

No write path exists in the published surface. All three tools read, all three OAuth scopes begin with read, and Function's documentation states the connector has read-only access and cannot modify your information. It also publishes readOnlyHint true and destructiveHint false. We could not read those annotations off the wire ourselves, so they are Function's claim rather than our observation.

Is the Function Health MCP connector covered by HIPAA?

Not uniformly, and Function says so directly. Its privacy policy states Function may operate as a HIPAA business associate but that HIPAA does not apply to all personal information it processes. For a consumer membership bought directly, the data is generally consumer health data under state law rather than HIPAA-protected. Function publishes a separate Consumer Health Data Privacy Policy covering that path.

What OAuth permissions does the Function Health connector request?

Three named read scopes, one per tool. The server's RFC 9728 descriptor advertised read:health_summary, read:biomarkers and read:action_plan on 2026-08-22. Each maps to one tool, so the consent screen genuinely separates the three surfaces. No scope grants writing anything, and the identity-only scopes on Function's Auth0 tenant are separate from these three.

What do I need before connecting Function Health to Claude?

A Function membership with completed lab results, and a paid Claude plan. Function's documentation lists both as prerequisites and notes that connectors require a Pro or Max subscription. If your lab results are still being processed the tools return nothing, which Function documents as a distinct troubleshooting case rather than an error condition.

Why does the Function Health MCP endpoint return 403 instead of 401?

Because an edge layer blocks the request before authentication is evaluated. On 2026-08-22 the endpoint returned a generic Google 403 HTML page to an anonymous handshake, with no www-authenticate header, and returned the same body to a plain GET. That is a WAF block rather than an auth challenge, so it says nothing about the server's auth posture.

Does the Function Health connector send data to Claude that I did not ask for?

One parameter deserves attention. The nutrition tool accepts a free-text context parameter for personalization, which Function's docs describe only as additional context. Everything else is a filter over data you already hold. Treat that field as the one place where text you supply, rather than summary counts, leaves the conversation.

Can I disconnect the Function Health connector after using it?

Yes, from either side independently. Function's documentation states you can revoke authorization from your Function account settings and separately disconnect or remove the connector from Claude at any time. It also notes you may request data deletion under applicable privacy laws. Function recommends disconnecting when you are not actively using the connector.

Sources

More Healthcare connectors

  • AdisInsight

    Query Springer Nature's drug-pipeline and trial database from an AI agent.

  • AdvancedMD

    Look up patients, find open slots, book appointments, and work denials and remittances in AdvancedMD from your AI agent.

  • AllTrails

    Search AllTrails' trails by place, map bounds or name and pull details and a 7-day trailhead forecast from your AI…

Browse all MCP connectorsClaude and ChatGPT setup guideBrowse AI skills

Product names and logos belong to their owners. Agentman is not affiliated with a connector's maker unless the page says the connector is built and run by Agentman.

Use it in an agent

Put Function Health to work.

Connect Function Health once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.

Open in Agentman Studio