Skip to content

Fitbit MCP by usefulapi

io.usefulapi/fitbitusefulapi.iostreamable-httpv1.40.4Scanned

Read Fitbit profile, activity, sleep, heart rate and device data.

17 tools: 10 change things and 7 only read.

Tools: 0 delete, 0 irreversible, 10 write, 7 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 0
  • No findings

The remote endpoint did not answer the last look. Remote posture

Anlyon alternative

10 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

What the Fitbit MCP by usefulapi can do

The Fitbit MCP by usefulapi is published by usefulapi.io, a domain the MCP Registry verified. It has 17 tools. It can create or change data (10 tools: fitbit_daily_activity_summary, fitbit_activity_time_series, fitbit_activity_goals, fitbit_lifetime_stats and 6 more), but cannot delete data. 7 tools only read.

None of its tools reads private data, brings in text other people write, or sends data out.

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Last scanned Oct 25, 2026, version 1.40.4.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

17 tools

Changes things 10Claude Code: ask
  • fitbit_activity_goalsThe user's activity goals (steps/distance/calories/active-minutes) for the daily or weekly period.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    The user's activity goals (steps/distance/calories/active-minutes) for the daily or weekly period. Fitbit REST: GET /1/user/-/activities/goals/{period}.json.

    Annotations the server declares

    • title: Activity goals
    • readOnlyHint: true
  • fitbit_activity_time_seriesActivity metric time series over a date range (e.g.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Activity metric time series over a date range (e.g. daily steps for a week). Max 1095 days. Fitbit REST: GET /1/user/-/activities/{resource}/date/{startDate}/{endDate}.json.

    Annotations the server declares

    • title: Activity time series
    • readOnlyHint: true
  • fitbit_breathing_rateBreathing (respiratory) rate summary for a date or range.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Breathing (respiratory) rate summary for a date or range. Fitbit REST: GET /1/user/-/br/date/{date}[/{endDate}].json.

    Annotations the server declares

    • title: Breathing rate
    • readOnlyHint: true
  • fitbit_cardio_scoreCardio fitness score (VO2 max estimate) for a date or range.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Cardio fitness score (VO2 max estimate) for a date or range. Fitbit REST: GET /1/user/-/cardioscore/date/{date}[/{endDate}].json.

    Annotations the server declares

    • title: Cardio score
    • readOnlyHint: true
  • fitbit_daily_activity_summaryDaily activity summary for a date — steps, distance, floors, calories, active minutes, and the day's logged activities.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Daily activity summary for a date — steps, distance, floors, calories, active minutes, and the day's logged activities. Fitbit REST: GET /1/user/-/activities/date/{date}.json.

    Annotations the server declares

    • title: Daily activity summary
    • readOnlyHint: true
  • fitbit_heart_rateHeart-rate time series — resting HR and time in each HR zone.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Heart-rate time series — resting HR and time in each HR zone. Give a single date + period, OR a date + endDate range. Fitbit REST: GET /1/user/-/activities/heart/date/{date}/{period|endDate}.json.

    Annotations the server declares

    • title: Heart rate
    • readOnlyHint: true
  • fitbit_hrvHeart rate variability (HRV) summary for a date or range.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Heart rate variability (HRV) summary for a date or range. Fitbit REST: GET /1/user/-/hrv/date/{date}[/{endDate}].json.

    Annotations the server declares

    • title: HRV
    • readOnlyHint: true
  • fitbit_lifetime_statsLifetime and best-ever activity statistics (total steps, distance, floors; personal bests).No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Lifetime and best-ever activity statistics (total steps, distance, floors; personal bests). Fitbit REST: GET /1/user/-/activities.json.

    Annotations the server declares

    • title: Lifetime stats
    • readOnlyHint: true
  • fitbit_skin_temperatureSkin temperature (relative to baseline) for a date or range.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Skin temperature (relative to baseline) for a date or range. Fitbit REST: GET /1/user/-/temp/skin/date/{date}[/{endDate}].json.

    Annotations the server declares

    • title: Skin temperature
    • readOnlyHint: true
  • fitbit_spo2Blood oxygen saturation (SpO2) summary for a date or range.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Blood oxygen saturation (SpO2) summary for a date or range. Fitbit REST: GET /1/user/-/spo2/date/{date}[/{endDate}].json.

    Annotations the server declares

    • title: SpO2
    • readOnlyHint: true
Only reads 7Show 7 read-only tools
  • fitbit_body_fat_logBody fat percentage log entries for a date.No findings

    Why it is in this group

    • The name "fitbit_body_fat_log" says "log": a word for reading.
    Description, as the server wrote it
    Body fat percentage log entries for a date. Fitbit REST: GET /1/user/-/body/log/fat/date/{date}.json.

    Annotations the server declares

    • title: Body fat log
    • readOnlyHint: true
  • fitbit_food_logFood/nutrition log for a date — logged foods and daily nutrition totals (calories, macros).No findings

    Why it is in this group

    • The name "fitbit_food_log" says "log": a word for reading.
    Description, as the server wrote it
    Food/nutrition log for a date — logged foods and daily nutrition totals (calories, macros). Fitbit REST: GET /1/user/-/foods/log/date/{date}.json.

    Annotations the server declares

    • title: Food log
    • readOnlyHint: true
  • fitbit_get_devicesList the user's Fitbit devices/trackers (battery, last sync, version).No findings

    Why it is in this group

    • The name "fitbit_get_devices" says "get": a word for reading.
    Description, as the server wrote it
    List the user's Fitbit devices/trackers (battery, last sync, version). Fitbit REST: GET /1/user/-/devices.json.

    Annotations the server declares

    • title: Get devices
    • readOnlyHint: true
  • fitbit_get_profileThe current user's Fitbit profile (name, age, gender, height, timezone, member since, avatar, etc.).No findings

    Why it is in this group

    • The name "fitbit_get_profile" says "get": a word for reading.
    Description, as the server wrote it
    The current user's Fitbit profile (name, age, gender, height, timezone, member since, avatar, etc.). Fitbit REST: GET /1/user/-/profile.json.

    Annotations the server declares

    • title: Get profile
    • readOnlyHint: true
  • fitbit_sleep_logSleep logs for a date (or date range) — stages/levels, duration, efficiency, start/end times.No findings

    Why it is in this group

    • The name "fitbit_sleep_log" says "log": a word for reading.
    Description, as the server wrote it
    Sleep logs for a date (or date range) — stages/levels, duration, efficiency, start/end times. Fitbit REST: GET /1.2/user/-/sleep/date/{date}[/{endDate}].json.

    Annotations the server declares

    • title: Sleep log
    • readOnlyHint: true
  • fitbit_water_logWater intake log for a date.No findings

    Why it is in this group

    • The name "fitbit_water_log" says "log": a word for reading.
    Description, as the server wrote it
    Water intake log for a date. Fitbit REST: GET /1/user/-/foods/log/water/date/{date}.json.

    Annotations the server declares

    • title: Water log
    • readOnlyHint: true
  • fitbit_weight_logBody weight log entries for a date.No findings

    Why it is in this group

    • The name "fitbit_weight_log" says "log": a word for reading.
    Description, as the server wrote it
    Body weight log entries for a date. Fitbit REST: GET /1/user/-/body/log/weight/date/{date}.json.

    Annotations the server declares

    • title: Weight log
    • readOnlyHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

The remote endpoint did not answer the last look

Looked at Nov 20, 2026, 19:35 UTC, unchanged since Oct 29, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
no
HTTP status of an anonymous initialize
not observed
tools/list served without credentials
no
Tools that change things, listed without credentials
0
Protocol version
not observed
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed

The probe stopped: The server redirected a POST to a different request.

Posture changes

  1. Oct 29, 2026
    • Reachable: yes to no
    • HTTP status of an anonymous initialize: 200 to none
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 10 to 0
    • Protocol version: 2025-06-18 to none
    • RFC 9728 protected resource metadata: https://fitbit.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
    • Authorization servers: https://fitbit.usefulapi.io to none
    • Dynamic client registration: yes to not observed
    • Client ID metadata documents: no to not observed

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. Reachable: yes -> no; HTTP status of an anonymous initialize: 200 -> none; tools/list served without credentials: yes -> no (and 6 more).View diff
    • Reachable: yes to no
    • HTTP status of an anonymous initialize: 200 to none
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 10 to 0
    • Protocol version: 2025-06-18 to none
    • RFC 9728 protected resource metadata: https://fitbit.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
    • Authorization servers: https://fitbit.usefulapi.io to none
    • Dynamic client registration: yes to not observed
    • Client ID metadata documents: no to not observed

Install

Pinned to version 1.40.4. Values in angle brackets are yours to fill in.

claude mcp add --transport http fitbit https://fitbit.usefulapi.io/mcp
claude mcp add --transport http fitbit https://fitbit.usefulapi.io/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__fitbit__fitbit_get_profile",
      "mcp__fitbit__fitbit_get_devices",
      "mcp__fitbit__fitbit_sleep_log",
      "mcp__fitbit__fitbit_weight_log",
      "mcp__fitbit__fitbit_body_fat_log",
      "mcp__fitbit__fitbit_food_log",
      "mcp__fitbit__fitbit_water_log"
    ],
    "ask": [
      "mcp__fitbit__fitbit_daily_activity_summary",
      "mcp__fitbit__fitbit_activity_time_series",
      "mcp__fitbit__fitbit_activity_goals",
      "mcp__fitbit__fitbit_lifetime_stats",
      "mcp__fitbit__fitbit_heart_rate",
      "mcp__fitbit__fitbit_spo2",
      "mcp__fitbit__fitbit_hrv",
      "mcp__fitbit__fitbit_breathing_rate",
      "mcp__fitbit__fitbit_cardio_score",
      "mcp__fitbit__fitbit_skin_temperature"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as fitbit. Review it before you use it.

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.usefulapi/fitbit/verify?hash=46c8c9042c4e5afc56393059430608e66ac0d7a8c20795e5b14cbdaae384a8c4" | jq -e '.changed == false'

Pinned hash 46c8c9042c4e, from Oct 25, 2026, 23:19 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.usefulapi/fitbit/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.usefulapi/fitbit
[![Anlyon Radar](https://radar.anlyon.com/badge/io.usefulapi/fitbit.svg)](https://radar.anlyon.com/servers/io.usefulapi/fitbit)

Source: MCP Registry · repository. Synced Nov 18, 2026, 11:18 UTC.

Fitbit MCP by usefulapi: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Fitbit MCP by usefulapi safe?

No scan can promise that. What its definitions show: 17 tools, 10 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Fitbit MCP by usefulapi delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Fitbit MCP by usefulapi do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Fitbit MCP by usefulapi have?

17 tools: 10 write, 7 read. fitbit_daily_activity_summary, fitbit_activity_time_series, fitbit_activity_goals, fitbit_lifetime_stats, fitbit_heart_rate, fitbit_spo2, fitbit_hrv, fitbit_breathing_rate and 9 more.

Does the Fitbit MCP by usefulapi need sign-in or OAuth?

Its remote endpoint did not answer the last anonymous look.

Does the Fitbit MCP by usefulapi send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Fitbit MCP by usefulapi changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Oct 25, 2026.