Tracked
Ask Claude about your Tracked training, nutrition, bodyweight, check-in and recovery data
- Brand
- Unknown
- Category
- Pending
- Primary Subcategory
- Pending
Integration details
Description
Connect your Tracked account to Claude to explore read-only summaries of your own training, nutrition, bodyweight, check-ins, and recovery data, including your sleep nights and, where your devices record them, your resting heart rate and heart-rate variability compared against your own recent baseline. Ask how a period went, compare it with the period before, or find out why some of your data is missing. Tracked uses explicit OAuth consent, bounded results, and separate permissions for each data domain. Claude cannot create, edit, or delete anything in your account. Photos, messages, coach notes, free-text check-in answers, raw wearable payloads, contact details, and billing information are never available through the connector. Summaries are informational, not medical advice, and Tracked publishes no readiness, recovery or strain score.
- Integration type
- Connector
- Verification status
Community connector- Platform
- Claude
- Category
- Pending
- Primary Subcategory
- Pending
- Secondary Subcategories
- None listed
- Brand
- Unknown
- Access
- Account required
- First tracked
- 2026-09-30
- Tool count
- 7
- Geography
- US
The broad Category that contains the Primary Subcategory.
The Primary Subcategory used for this profile’s headline score.
Other Subcategories where the Integration is listed.
Claude Connector discovery is coming soon
Community Connectors only appear in Claude’s registry.Once verified, organic discovery begins and we can calculate your score.Read more about Community Connector verification.
No spam. Unsubscribe any time.
No spam. Unsubscribe any time.
What discovery looks like

Claude can surface verified Connectors when they match a user’s Prompt.
How Claude Connector discovery works
Your Connector will compete to appear for users’ Prompts once Claude verifies it
Competitive lineup
7 tools agents can invoke
How do I improve a Community connector's discoverability?
The levers are the listing surface agents actually read: names, descriptions, keywords, tool metadata, and registry health. Which lever matters depends on where discovery breaks, which is what continuous measurement shows.
Where is this profile measured?
This profile uses the geography attached to the latest public registry snapshot: US. Locale tags are intentionally omitted.