Skip to content

BatterySnap MCP server

com.battery-snap/batterysnapbattery-snap.comstreamable-httpv1.0.1Scanned

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

14 tools: 7 change things and 7 only read.

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

Tools listed without sign-in. Remote posture

With Anlyon

7 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the BatterySnap MCP server can do

The BatterySnap MCP server is published by battery-snap.com, a domain the MCP Registry verified. It has 14 tools. It can create or change data (7 tools: model_summary, fleet_totals, fleet_summary, top_devices_by_live_uptime and 3 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.

Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 12, 2026, version 1.0.1.

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.

14 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, optionally restricted to one `country` / `continent`.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, optionally restricted to one `country` / `continent`. 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. A region scope with fewer than 5 devices is refused; to compare several regions at once use `region_summary`.

    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. Pass `country` and / or `continent` to restrict to devices of that region; the call fails when fewer than 5 devices of the model remain.

    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. There is no region filter here: regional questions go to the aggregates (`region_summary`, `top_models`, `fleet_summary`).

    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. `country` / `continent` rank the models as they behave in one region (e.g. heat in hot climates).

    Annotations the server declares

    • title: Rank models by metric
    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: false
Only reads 7Show 7 read-only tools
  • 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, 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
  • region_summaryCompare battery behaviour across regions in one call: one entry per continent or per country, each with the same mean / median / p25 / p75 / min / max blocks as `fleet_summary` (te…No findings

    Why it is in this group

    • The description's first verb is "compare": a word for reading.
    Description, as the server wrote it
    Compare battery behaviour across regions in one call: one entry per continent or per country, each with the same mean / median / p25 / p75 / min / max blocks as `fleet_summary` (temperature, level, discharge and charge hours, awake ratio). Narrow with `brand` / `model` (e.g. how one model fares per continent) or with `continent` (e.g. group_by='country' within 'Africa'). The region is derived from the time zone the phone is set to (not GPS / IP), so travellers and manual settings blur it. Regions with fewer than 5 devices are left out and only counted (`suppressed_*`), as are devices whose time zone names no place (`unlocated_device_count`); check each group's `device_count` before comparing — small groups are noisy.

    Annotations the server declares

    • title: Battery stats by region
    • 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.

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.

Tools listed without sign-in

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

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
7
Protocol version
2025-06-18
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
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 7 tools that change things (7 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://mcp.battery-snap.com/mcp: tools/list returned 14 tools to an anonymous client, including model_summary (write), fleet_totals (write), fleet_summary (write), top_devices_by_live_uptime (write), top_devices (write) and 2 more

    What this check looks for

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. Tools1 added, 5 changed.+1 added~5 changedView diff

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
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 or a way out, 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__region_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. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as batterysnap. 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/com.battery-snap/batterysnap/verify?hash=98615a5a579b887dd8a6001c923d9e733680d215998c6a02b0449a5a2cb98858" | jq -e '.changed == false'

Pinned hash 98615a5a579b, from Nov 12, 2026, 17:17 UTC.

Watch

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

https://radar.anlyon.com/servers/com.battery-snap/batterysnap/changes.xml

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

Badge

Anlyon Radar badge for com.battery-snap/batterysnap
[![Anlyon Radar](https://radar.anlyon.com/badge/com.battery-snap/batterysnap.svg)](https://radar.anlyon.com/servers/com.battery-snap/batterysnap)

Source: MCP Registry. Synced Oct 21, 2026, 17:51 UTC.

BatterySnap MCP server: questions and answers

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

Is the BatterySnap MCP server safe?

No scan can promise that. What its definitions show: 14 tools, 7 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 BatterySnap MCP server delete data?

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

Can the BatterySnap MCP server 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 BatterySnap MCP server have?

14 tools: 7 write, 7 read. model_summary, fleet_totals, fleet_summary, top_devices_by_live_uptime, top_devices, top_models, device_ranking, brands and 6 more.

Does the BatterySnap MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the BatterySnap MCP server send data to outside services?

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

Has the BatterySnap MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Nov 12, 2026. Every change is on this page and in its Atom feed.