plugin
Health Data Understanding
Health Data Understanding is a ratified StackFast Store framework listing with an agent-facing MCP handle of Health Data Understanding MCP.
Host and data posture
Where this product is meant to live.
Health data belongs in private/BYOC paths with strict non-diagnostic boundaries.
Commercial shape
Private/BYOC product
Data posture
BYOC required
Approval posture
Approval required
Best demo
StackFast UI
Best daily use
Who it is for
Agents, operators, and CleverQ users that need a governed StackFast capability instead of a generic chat answer.
Problem it solves
Organizes health inputs, flags gaps and uncertainty, and prepares doctor-ready questions and summaries.
Activation model
Store discovery is catalog-ready. Execution posture: execute-after-auth+safety-gated. Public go-live remains gated until Robert ratifies publication.
Proof and source paths
- Public job-name ratified 2026-05-27
- Two-name doctrine applied
- Proof-without-recipe disclosure boundary applied
- Callable tools are real repo MCP tool IDs
Repo evidence
specs/CLEVERQ_FRAMEWORK_WORKBENCH_AND_AGENTIC_STORE_ADDENDUM_2026-05-27.mdspecs/WO-CLEVERQ-FW-STORE-LISTINGS-P1-2026-05-27.mdlib/tool-registry/plugin-mcp-tools.tslib/framework-invocation/mcp-tools.ts
Capabilities
health data understanding
mcpA safety-gated health-data organization and doctor-brief preparation tool. Organizes health inputs, flags gaps and uncertainty, and prepares doctor-ready questions and summaries.
Agent use
Use Health Data Understanding MCP through stackfast.health.understand, stackfast.framework.route, stackfast.framework.invoke, stackfast.framework.validate_output, stackfast.framework.apply_mask, stackfast.framework.trace. Required boundaries: Execute-after-auth with server-side safety gate, MASK boundary, and doctor-ready artifact posture.. Do not request raw framework bodies or protected methodology.
Connector proof
Catalog is not the same as customer-ready.
This product only becomes market-ready after a real host mounts the entitled tools, a safe call succeeds, metering records the event, and a customer-safe receipt exists. Until then, the page shows the strongest proven status without rounding up.
Catalog
Runtime registry and product manifest are present.
Entitlement
Execution requires OAuth or storefront entitlement scope.
Callable
6 tool(s) declared with no missing V1 tools.
Metering
MCP calls are routed through the metering receipt path.
Customer validated
Pending fresh host-surface call receipt.
Runtime registry status
Primary registry
stackfast.ai/api/mcp
Status
partial public mcp
Install gate
Catalog-ready only. Do not publish publicly until Robert ratifies store go-live.
Callable tools
stackfast.health.understandstackfast.framework.routestackfast.framework.invokestackfast.framework.validate_outputstackfast.framework.apply_maskstackfast.framework.trace
Missing or gated tools
No missing tools declared for the current V1 boundary.
- Framework listing layer only; no parallel CleverQ engine introduced.
- Public surfaces must render the human job-name and proof-without-recipe card fields.
Install and activate
Connect this product through the StackFast MCP endpoint. Discovery metadata is public; execution uses OAuth and storefront entitlement checks.
MCP URL
https://stackfast.ai/api/mcpAgent subscription
This product remains request-scope until its checkout, fulfillment, and public-name gates are complete.
Client snippets
ChatGPT
Add StackFast as a custom MCP connector, then approve OAuth when prompted.
Claude
Connect a remote MCP server using the StackFast MCP URL and a tenant-scoped token or OAuth flow.
Cursor
Register StackFast as a remote MCP server for project-scoped tool use.
Grok
Add StackFast as a custom MCP connector using the StackFast MCP URL and customer entitlement auth.
Product: Health Data Understanding Product API: https://stackfast.ai/api/store/products/health-data-understanding-mcp Pricing API: https://stackfast.ai/api/store/pricing/health-data-understanding-mcp Manifest API: https://stackfast.ai/api/store/manifests/health-data-understanding-mcp MCP URL: https://stackfast.ai/api/mcp Auth: oauth_reader_or_storefront_entitlement Checkout session API: https://stackfast.ai/api/store/checkout/session Plans: - Health Data Understanding: Request scope; checkout_ready=false; checkout_url=request_scope Agent activation: - Read this product manifest and pricing API. - If a plan has checkout_ready=true, open its checkout_url or POST product_slug, plan_slug, and customer_email to the checkout session API. - After Stripe payment, the signed webhook grants storefront_entitlements for the buyer email/account. - Connect the LLM client to the MCP URL and approve OAuth so tools/list reflects the licensed reader surface. - Call only tools exposed for that entitlement; unentitled execution must fail closed.