freddy

coach.freddyPublished by freddy.coachOfficial publisherv1.0.0Updated Oct 24, 2026

Connect your wearables, rings and training apps, then ask your AI about your own health data.

VerifiedStreamable HTTPWeb executableLocation & Lifestyle

Overview

AI-generated overview

Remote MCP server that connects wearables, rings and training apps so an assistant can answer questions about your own health data.

What you can do
  • Connects data from wearables, rings and training apps to the assistant.
  • Lets the assistant answer questions about your own health and training data.
  • No individual tools are documented in the listing, so the exact queries and actions available are not described.
When to use it
Useful when you want an AI assistant to discuss your personal health, recovery or training data gathered from wearables and fitness apps, instead of exporting it manually.
Requirements
A remote MCP endpoint at freddy.coach reached over streamable HTTP; OAuth sign-in is required. No environment variables or headers are declared. A Freddy account linked to your wearable and training data is implied.
Before you install
It handles sensitive personal health and training data, which is shared with a third-party service and its AI queries. Access is granted through OAuth, so review which scopes and data sources you authorize. No tool list is published, so what it can read or change cannot be verified in advance.

Installation

In SourceWeft

  1. Open freddy in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/coach.freddy%2Ffreddy/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "freddy": {
      "type": "http",
      "url": "https://freddy.coach/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

56% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.