Skip to content

BatterySnap

by battery-snap.com · remote · no sign-in to list tools · v1.0.1 · published by com.battery-snap

Real-world Android battery stats from BatterySnap users: device, model and fleet rankings.

Changes · 7

13 tools: 7 change things and 6 only read.

Scanned Oct 21, 2026

No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.

claude mcp add --transport http batterysnap https://mcp.battery-snap.com/mcp

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

13 tools

Changes things 7Claude Code: ask
  • device_rankingAnswer 'is MY phone normal?' — rank one device's metric against other devices of the same model AND against the whole fleet, in one call.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
    Answer 'is MY phone normal?' — rank one device's metric against other devices of the same model AND against the whole fleet, in one call. Returns the device's value, its 1-based rank, its percentile, and the cohort median / mean / min / max for both cohorts. Prefer this over fetching `device_summary` + `model_summary` and comparing by hand: it is a single call and gives the percentile directly. The model cohort is the meaningful one for 'is this device degraded'; the fleet cohort puts the model itself in context.

    Annotations the server declares

    • title: Compare a device to its peers
    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: false
  • fleet_summaryAggregate battery metrics across the entire fleet, or across one brand when `brand` is provided.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
    Aggregate battery metrics across the entire fleet, or across one brand when `brand` is provided. Returns mean / median / p25 / p75 / min / max for the same set of metrics as `model_summary`. Use this for fleet-wide baselines that a single device or model can be compared against.

    Annotations the server declares

    • title: Fleet battery summary
    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: false
  • fleet_totalsLive fleet-wide counters: total devices, models, snapshots, sessions, the running snapshot-ingest rate (snapshots/sec) and the timing of the last insert batch.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
    Live fleet-wide counters: total devices, models, snapshots, sessions, the running snapshot-ingest rate (snapshots/sec) and the timing of the last insert batch. Use this for one-shot 'how big is the dataset / how fast is it growing' questions. Unlike `fleet_summary`, no per-device aggregation is involved — these are raw running counts from the database.

    Annotations the server declares

    • title: Fleet totals
    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: false
  • model_summaryAggregate battery metrics across ALL devices of a given brand+model.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
    Aggregate battery metrics across ALL devices of a given brand+model. Returns mean / median / p25 / p75 / min / max for: temperature (C), battery level (%), discharge speed (hours per 100%%), AC / USB / wireless charge speed (hours per 100%%), and awake ratio. Use this to characterize how a model behaves in the field, or to compare a single device against its model average. Also includes: * `raw_model_code`: representative raw Android Build.MODEL identifier (smallest among devices grouped under this street name), or null if none recorded. * `url`: public BatterySnap web page for the model (https://www.battery-snap.com/brands/<brand>/models/<raw_model_code>); null when `raw_model_code` is null.

    Annotations the server declares

    • title: Model battery summary
    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: false
  • top_devicesRank INDIVIDUAL devices by any battery metric — the general-purpose leaderboard.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
    Rank INDIVIDUAL devices by any battery metric — the general-purpose leaderboard. Use it for 'which phones run hottest / last longest / charge fastest', optionally narrowed to one brand and/or model. Returns at most `limit` rows, so it answers superlative questions in a single small call instead of enumerating the fleet. Ranking is over each device's own lifetime aggregate. Pair the metric with the right `order`: e.g. hottest = temperature_c + desc, fastest AC charging = ac_charge_hours + asc, best battery life = discharge_hours + desc.

    Annotations the server declares

    • title: Rank devices by metric
    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: false
  • top_devices_by_live_uptimeSame as `top_devices_by_uptime`, but restricted to devices that have not yet rebooted past their recorded maximum — meaning the uptime is currently still climbing.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
    Same as `top_devices_by_uptime`, but restricted to devices that have not yet rebooted past their recorded maximum — meaning the uptime is currently still climbing. These are the devices that are 'live' champions right now, as opposed to historical record-holders. Each entry includes a `url` pointing at the device's interactive battery history page on https://www.battery-snap.com.

    Annotations the server declares

    • title: Top devices by live uptime
    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: false
  • top_modelsRank device MODELS by any battery metric, aggregating across every device of that model.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
    Rank device MODELS by any battery metric, aggregating across every device of that model. This is the tool for 'which phone model has the best battery life', 'which models charge fastest', 'which run hottest' — questions that would otherwise need one `model_summary` call per model. Ordering is by the per-model MEDIAN of the metric (outlier-resistant); the mean is returned alongside. Use `brand` to rank within one manufacturer and `min_devices` to require a minimum sample size.

    Annotations the server declares

    • title: Rank models by metric
    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: false
Only reads 6Claude Code: allow
  • brandsReturn the mobile devices brands for which we have battery statistics, along with the number of distinct models, the number of devices recorded per brand, and the largest single-mo…No findings

    Why it is in this group

    • The description's first verb is "return": a word for reading.
    Description, as the server wrote it
    Return the mobile devices brands for which we have battery statistics, along with the number of distinct models, the number of devices recorded per brand, and the largest single-model device count within the brand (`max_devices_per_model`). Each entry also includes a `url` to the public BatterySnap web page for the brand (e.g. https://www.battery-snap.com/brands/samsung). Pass `min_device_count` / `max_device_count` and `min_model_count` / `max_model_count` to filter brands by recorded-device and distinct-model counts. Pass `fields` to keep only specific attributes in each entry. The full list is long: pass `limit` (and `offset` to page) unless you really need every brand, and prefer `search` when resolving one brand by name.

    Annotations the server declares

    • title: List brands
    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: false
  • device_summaryReturn aggregated battery metrics for ONE specific device: average / min / max temperature, average battery level, mean charge time per power source (AC, USB, wireless) and mean di…No findings

    Why it is in this group

    • The description's first verb is "return": a word for reading.
    Description, as the server wrote it
    Return aggregated battery metrics for ONE specific device: average / min / max temperature, average battery level, mean charge time per power source (AC, USB, wireless) and mean discharge time over a recent (~2 weeks) and a long (~2 months) window, plus awake ratio and basic device info. Also includes `url`: the public BatterySnap web page for this device's interactive battery history (https://www.battery-snap.com/device_history?device=<uid>). All values are pre-computed from the device's full snapshot history — no raw timeseries is returned.

    Annotations the server declares

    • title: Device battery summary
    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: false
  • devicesReturn the list of individual physical devices matching one or more (brand, model) pairs for which we have battery statistics.No findings

    Why it is in this group

    • The description's first verb is "return": a word for reading.
    Description, as the server wrote it
    Return the list of individual physical devices matching one or more (brand, model) pairs for which we have battery statistics. Each entry in the returned list describes ONE specific device (identified by its own `device_uid`) and the metrics on that entry are aggregates computed only from THAT device's own snapshot history — they are not aggregated across devices. Two devices of the same brand and model will appear as two separate entries with their own independent metrics. Per-device fields include: brand, resolved model (street name), raw Android model, snapshot count, activity window (first / last seen), average battery level, average / min / max battery temperature in Celsius, awake-ratio, discharge speed and AC / USB / wireless charge speed (hours per full 100% swing), Android SDK level, IANA time zone, and a `url` pointing at the public BatterySnap web page for the device's interactive battery history (https://www.battery-snap.com/device_history?device=<uid>). Each pair's model is matched case-insensitively against either the resolved street name (e.g. 'Galaxy S23') or the raw Android model identifier (e.g. 'SM-S911B'). Pass `fields` to keep only specific attributes per device and avoid bloated responses.

    Annotations the server declares

    • title: Find devices by model
    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: false
  • modelsReturn the mobile devices models of the given brands for which we have battery statistics, along with the brand each model belongs to, the number of devices recorded, the average b…No findings

    Why it is in this group

    • The description's first verb is "return": a word for reading.
    Description, as the server wrote it
    Return the mobile devices models of the given brands for which we have battery statistics, along with the brand each model belongs to, the number of devices recorded, the average battery temperature in Celsius, and the min/max Android SDK level per model. Each entry is grouped by the resolved street name (e.g. 'Galaxy S23'), which may cover several raw Android Build.MODEL identifiers (carrier variants, regional SKUs, …). For URL building, every entry also exposes: * `raw_model_code`: a representative raw Build.MODEL identifier (the lexicographically smallest one among devices grouped under this street name), or null if no device reported a non-empty model code. * `url`: the public BatterySnap web page for the model, e.g. https://www.battery-snap.com/brands/samsung/models/SM-S911B. Built from `brand` + `raw_model_code`; null when either is null; `raw_model_code` is null. The page lists all devices reporting that exact raw model. Pass `min_device_count` / `max_device_count` to filter models by how many devices were recorded. For 'which models have the most devices' questions, pass sort='device_count' with a small `limit` (and typically fields=['brand', 'model', 'device_count', 'url']) instead of fetching and sorting the full list. Pass `fields` to keep only specific attributes in each entry. Omit `brands` (or pass an empty list) to return models across every brand.

    Annotations the server declares

    • title: List models
    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: false
  • top_devices_by_uptimeReturn the devices with the longest single uptime ever recorded between reboots (max_elapsed_time).No findings

    Why it is in this group

    • The description's first verb is "return": a word for reading.
    Description, as the server wrote it
    Return the devices with the longest single uptime ever recorded between reboots (max_elapsed_time). Optionally filter by brand and/or model. Useful to find which physical phones in the fleet are champions of staying powered on for weeks/months at a time. Each entry includes a `device_uid` you can feed into `device_summary` for deeper analysis, and a `url` pointing at the device's interactive battery history page on https://www.battery-snap.com.

    Annotations the server declares

    • title: Top devices by uptime
    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: false

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.

Install

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

claude mcp add --transport http batterysnap https://mcp.battery-snap.com/mcp

Run in a terminal.

Claude Code permissions

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

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__batterysnap__brands",
      "mcp__batterysnap__models",
      "mcp__batterysnap__devices",
      "mcp__batterysnap__device_summary",
      "mcp__batterysnap__top_devices_by_uptime",
      "mcp__batterysnap__search"
    ],
    "ask": [
      "mcp__batterysnap__model_summary",
      "mcp__batterysnap__fleet_totals",
      "mcp__batterysnap__fleet_summary",
      "mcp__batterysnap__top_devices_by_live_uptime",
      "mcp__batterysnap__top_devices",
      "mcp__batterysnap__top_models",
      "mcp__batterysnap__device_ranking"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as batterysnap. Review it before you use it.