Evidence-first
MCP service

Source-linked supplement evidence, claim-level citations, and a DOI-backed dataset for MCP-compatible agents. Product and affiliate tools remain available in a separate, clearly labeled family.

5 evidence tools5 compatible commerce tools2025-11-25 current protocol
https://healthyagingatlas.com/api/mcp/

Streamable HTTP over JSON-RPC 2.0 · official TypeScript SDK · stateless JSON responses · public evidence access without authentication.

Current revision: 2025-11-25Compatible revisions: 2025-06-18, 2025-03-26, 2024-11-05, 2024-10-07
View discovery metadata

Use a standard MCP client

1

Initialize

The client proposes a supported protocol revision and declares its capabilities.

2

Discover

Call tools/list. Evidence tools include outputSchema; older clients may ignore this field.

3

Invoke

Call tools/call. Evidence tools return both structuredContent and matching JSON text for older clients.

Raw initialize example

curl -s -X POST 'https://healthyagingatlas.com/api/mcp/' \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  --data '{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "initialize",
  "params": {
    "protocolVersion": "2025-11-25",
    "capabilities": {},
    "clientInfo": {
      "name": "example-client",
      "version": "1.0.0"
    }
  }
}'

Evidence and provenance first

These read-only tools never return affiliate links. Canonical HAA source URLs are clean and untracked. Citation metadata is emitted only after the repository PubMed audit passes with zero flags; mismatched, conflicting, or unverifiable citations are withheld and counted. Stored finding prose is withheld because the current PubMed metadata cache does not independently establish claim-level interpretation. Evidence density is not proof of efficacy and all outputs remain educational.

01search_evidenceevidence · no affiliate links

Search published supplement-goal evidence records by supplement, goal, population, PubMed publication type, and year. Returns clean HAA canonical sources and no affiliate links.

Parameters: supplement?, goal?, population?, study_type?, year_from?, year_to?, limit?

02get_evidence_summaryevidence · no affiliate links

Get one citable evidence summary with grade, mapped study counts, limitations, safety boundary, review date, reviewer, and canonical source.

Parameters: supplement, goal

03get_citationsevidence · no affiliate links

Get PubMed-cache-verified citations for a supplement-goal pair. Records with mismatched metadata, conflicting sources, or unverifiable identifiers are counted and withheld; stored claim prose is not emitted without claim-level verification.

Parameters: supplement, goal, study_type?, year_from?, year_to?, limit?

04query_evidence_mapevidence · no affiliate links

Query the DOI-backed Supplement Evidence Density Map 2026 and receive its version, denominator, methods URL, canonical citation, and filtered CSV rows.

Parameters: supplement?, goal?, cluster?, evidence_strength?, minimum_rct_count?, limit?

05compare_evidenceevidence · no affiliate links

Compare mapped evidence strength and limitations for two to five supplements for one goal. This is not a product ranking or purchase recommendation.

Parameters: supplements[2..5], goal

Evidence tool call

curl -s -X POST 'https://healthyagingatlas.com/api/mcp/' \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  --data '{"jsonrpc":"2.0","id":2,"method":"tools/call","params":{"name":"get_evidence_summary","arguments":{"supplement":"ashwagandha","goal":"sleep"}}}'

Products and prices stay separate

The original five tool names remain available so existing clients continue to work. Their descriptions and results explicitly identify commerce, product-scoring boundaries, and affiliate links. They are not the source for clinical-evidence questions.

01search_supplementscommerce

Legacy catalog search. May return affiliate purchase URLs.

Parameters: query, goal?, demographic?, limit?

02get_productcommerce

Legacy product-quality, certification, availability, and price lookup. May return an affiliate purchase URL.

Parameters: product_id

03compare_supplementscommerce

Legacy editorial or catalog comparison. Use compare_evidence when commerce-free clinical evidence is required.

Parameters: supplement_a, supplement_b

04get_price_historycommerce

Legacy retailer price observations and freshness. Price data is not clinical evidence.

Parameters: product_id

05recommend_for_goalcommerce

Legacy catalog/product ranking. May return affiliate URLs and is not a clinical-evidence grade or personalized advice.

Parameters: goal, budget_usd?, demographic?, limit?

Public, rate-limited, and aggregate-only

Public access is limited to 100 requests per 24-hour counter window by default. Every request, including discovery, consumes one slot. Responses include X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset, and X-RateLimit-Tier; throttled requests return HTTP 429 and Retry-After. Provisioned API keys may have higher limits.

Rate limiting uses a server-secret HMAC of the network identifier; raw IP addresses and API keys are not used as counter keys. Counter identifiers expire after up to 24 hours. Operational telemetry stores only aggregate tool, coarse client family, success/error, latency bucket, and clean HAA source-path counts. It does not store prompts, tool arguments, raw IPs, API keys, full user agents, or error text.

Do not send names, contact details, medical records, symptoms, medication lists, or other personal or sensitive health information in tool arguments. See the Privacy Policy and Terms of Service.

Troubleshooting

Redirect or route mismatch

Use the exact trailing-slash endpoint: https://healthyagingatlas.com/api/mcp/

HTTP 406 or media-type error

For raw clients send both accepted Streamable HTTP media types: Accept: application/json, text/event-stream. Standard SDK clients do this automatically.

HTTP 403 Forbidden Origin

Browser requests must use an explicitly allowed Origin. Requests without an Origin remain supported for standard non-browser MCP clients.

Unsupported protocol version

Use one of the documented compatible revisions. Subsequent HTTP requests should send the negotiated revision in MCP-Protocol-Version. Unsupported headers return HTTP 400.

GET or DELETE returns 405

The service is stateless and does not expose a standalone server-initiated SSE stream or client-terminated sessions. Tool traffic uses POST.

Old client does not read structuredContent

Every evidence result also contains the same object serialized as JSON in a text content block for backward compatibility.

Tool validation error

Inspect the inputSchema from tools/list. Invalid tool arguments are returned as tool execution errors so an agent can correct them.

Integration support or data correction

Email hello@healthyagingatlas.com with a reproducible request and the canonical source URL.

Contact support

Last updated: July 18, 2026