BatterySnap
REMOTE · MCP.BATTERY-SNAP.COM
Real-world Android battery stats from BatterySnap users: device, model and fleet rankings.
Available components
Last scanned (21 hours ago)
Scores higher than 69% of remote servers
Reachable. Last reached 4 Nov 2026.
Category IoT and Hardware
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security66
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability76
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 4859 tokens (~323/item across 15 items; 14 tools + 1 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management63
- Stability observed for 19 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 14 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 16 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
- Supports UI / widget rendering.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “devices” rewrote its description, which is the text the model reads security
- Tool “fleet_summary” rewrote its description, which is the text the model reads security
- Tool “model_summary” rewrote its description, which is the text the model reads security
- Tool “top_devices” rewrote its description, which is the text the model reads security
- Tool “top_models” rewrote its description, which is the text the model reads security
- Schema quality: 280 → 323 ▼ functional
- New tool “region_summary” functional
- “fleet_summary” added an optional parameter “continent” cosmetic
- “fleet_summary” added an optional parameter “country” cosmetic
- “model_summary” added an optional parameter “continent” cosmetic
- “model_summary” added an optional parameter “country” cosmetic
- “top_models” added an optional parameter “continent” cosmetic
- “top_models” added an optional parameter “country” cosmetic
- “top_models” reworded the description of “min_devices” cosmetic
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 24 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Probed https://mcp.battery-snap.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=bs-report.xhelas.com | CN=YR1,O=Let's Encrypt,C=US | 27 Sept 2026 | 26 Dec 2026 | RSA 2048 | SHA256-RSA | 502cc08bdc7a55395ee26096792e5728815 |
| SANs: battery-snap.com, bs-report.xhelas.com, mcp.battery-snap.com, www.battery-snap.com | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of mcp.battery-snap.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| battery-snap.com. | present | 13106 | 8 | Verified |
| mcp.battery-snap.com. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.battery-snap.com/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.battery-snap.com/mcp | Inconclusive | 405 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
brands List brands ~378
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.
| Name | Type | Req | Description |
|---|---|---|---|
| fields | – | – | Optional whitelist of attribute names to keep in each returned entry, used to shrink the response. When omitted or empty, all attributes documented in the output schema are returned. Unknown names ar… |
| limit | – | – | Return at most this many entries. Omit for no cap — but the unbounded list can be very large, so prefer a limit. |
| max_device_count | – | – | Drop entries with more than this many recorded devices. Use to skip very common entries. Omit for no upper bound. |
| max_model_count | – | – | Drop brands with more than this many distinct models. Omit for no upper bound. |
| min_device_count | – | – | Drop entries with fewer than this many recorded devices. Defaults to 1 (keep all). |
| min_model_count | – | – | Drop brands with fewer than this many distinct models. Defaults to 0 (keep all). |
| offset | – | – | Skip this many entries before returning results — use with `limit` to page through a long list. Defaults to 0. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
device_ranking Compare a device to its peers ~318
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.
| Name | Type | Req | Description |
|---|---|---|---|
| device_uid | string | yes | Stable device UUID returned by `devices`, `top_devices` or the share flow. |
| metric | string | – | Which battery metric to rank on. One of: 'temperature_c' (mean battery temperature, C), 'max_temperature_c' / 'min_temperature_c' (hottest / coldest ever seen, C), 'battery_level_pct' (mean charge le… |
| Name | Type | Req | Description |
|---|---|---|---|
| brand | string | – | Lowercase Android brand identifier. |
| device_uid | string | – | The device that was ranked. |
| fleet | object | – | Rank against every device in the fleet, all models mixed. |
| metric | string | – | The metric that was ranked. |
| model | – | – | Resolved model name (street name). |
| model_cohort | object | – | Rank against other devices of the SAME brand + model — the fair like-for-like comparison. |
| raw_model | string | – | Raw Build.MODEL identifier. |
| snapshot_count | integer | – | Snapshots behind this device's aggregate. |
| url | string | – | Public BatterySnap page with this device's interactive battery history. |
| value | – | – | This device's value for the metric. |
No examples provided.
device_summary Device battery summary ~147
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.
| Name | Type | Req | Description |
|---|---|---|---|
| device_uid | string | yes | Stable device UUID returned by the `devices` tool. |
| Name | Type | Req | Description |
|---|---|---|---|
| android_api_level | – | – | Android SDK level (e.g. 34 = Android 14). |
| avg_battery_level_pct | – | – | Mean battery charge level across all snapshots (0-100). |
| avg_temperature_c | – | – | Mean battery temperature in Celsius across all snapshots. |
| awake_ratio | – | – | Fraction of observed time the device was awake / screen-on (0..1). |
| brand | string | – | Lowercase Android brand identifier. |
| device_uid | string | – | Stable UUID identifying this device. |
| first_seen | – | – | ISO 8601 timestamp of the earliest snapshot. |
| last_seen | – | – | ISO 8601 timestamp of the most recent snapshot. |
| max_temperature_c | – | – | Hottest battery temperature in Celsius ever observed. Sustained highs are a battery-health concern. |
| mean_ac_charge_hours_long | – | – | Hours to charge 100%% on AC over the last ~2 months. |
| mean_ac_charge_hours_recent | – | – | Hours to charge 100%% on AC (wall charger) over the last ~2 weeks. |
| mean_discharge_hours_long | – | – | Average hours to discharge 100%% over the last ~2 months. |
| mean_discharge_hours_recent | – | – | Average hours to discharge 100%% over the last ~2 weeks. Null when not enough data. |
| mean_usb_charge_hours_long | – | – | Hours to charge 100%% over USB over the last ~2 months. |
| mean_usb_charge_hours_recent | – | – | Hours to charge 100%% over USB (computer) over the last ~2 weeks. |
| mean_wireless_charge_hours_long | – | – | Hours to charge 100%% wirelessly over the last ~2 months. |
| mean_wireless_charge_hours_recent | – | – | Hours to charge 100%% wirelessly over the last ~2 weeks. |
| min_temperature_c | – | – | Coldest battery temperature in Celsius ever observed. |
| model | – | – | Human-readable resolved model name (e.g. 'Galaxy S23'). |
| observed_days | – | – | Span in days between first_seen and last_seen. |
| raw_model | string | – | Raw Build.MODEL string reported by the device. |
| snapshot_count | integer | – | Total snapshots recorded for this device. |
| url | string | – | Public BatterySnap web page showing this device's interactive battery history, e.g. https://www.battery-snap.com/device_history?device=<uid>. Locale-agnostic. |
No examples provided.
devices Find devices by model ~343
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.
| Name | Type | Req | Description |
|---|---|---|---|
| fields | – | – | Optional whitelist of attribute names to keep in each returned entry, used to shrink the response. When omitted or empty, all attributes documented in the output schema are returned. Unknown names ar… |
| pairs | array | yes | One or more {brand, model} pairs to look up. Each pair fetches devices matching that brand and model. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
fleet_summary Fleet battery summary ~248
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`.
| Name | Type | Req | Description |
|---|---|---|---|
| brand | – | – | Optional lowercase brand identifier. If set, aggregates across that brand only; otherwise across the entire fleet. |
| continent | – | – | Optional continent, case-insensitive: 'Africa', 'Antarctica', 'Asia', 'Europe', 'North America', 'Oceania' or 'South America'. Keeps only devices whose time zone lies there. Combine with `country` fo… |
| country | – | – | Optional ISO 3166 alpha-2 country code (e.g. 'FR', 'IN', 'US'), case-insensitive. Keeps only devices whose time zone belongs to that country. The region comes from the phone's time-zone setting, not… |
| Name | Type | Req | Description |
|---|---|---|---|
| ac_charge_hours | object | – | – |
| awake_ratio | object | – | – |
| battery_level_pct | object | – | – |
| device_count | integer | – | Distinct devices in scope. |
| discharge_hours | object | – | – |
| model_count | integer | – | Distinct resolved models in scope. |
| scope | string | – | 'fleet' for the whole fleet, else the comma-joined filters applied, e.g. 'brand:samsung', 'country:FR' or 'brand:samsung,continent:Asia'. |
| snapshot_count | integer | – | Sum of snapshots across all devices in scope. |
| temperature_c | object | – | – |
| usb_charge_hours | object | – | – |
| wireless_charge_hours | object | – | – |
No examples provided.
fleet_totals Fleet totals ~90
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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| device_count | integer | – | Distinct devices that have ever reported a snapshot. |
| last_snapshot_insert_count | – | – | Number of snapshots in the most recent insert batch. |
| last_snapshot_insert_time | – | – | ISO 8601 timestamp of the most recent snapshot-batch insert. |
| model_count | integer | – | Distinct resolved models (street names) across the fleet. |
| session_count | integer | – | Total reboot-bounded sessions recorded across all devices. |
| snapshot_count | integer | – | Total battery snapshots stored across all devices, taken from the running counter in the `globals` table. |
| snapshot_insert_rate | – | – | Exponentially-smoothed snapshot-ingest rate, in snapshots per second. |
No examples provided.
model_summary Model battery summary ~387
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.
| Name | Type | Req | Description |
|---|---|---|---|
| brand | string | yes | Lowercase Android brand identifier (e.g. 'samsung'). |
| continent | – | – | Optional continent, case-insensitive: 'Africa', 'Antarctica', 'Asia', 'Europe', 'North America', 'Oceania' or 'South America'. Keeps only devices whose time zone lies there. Combine with `country` fo… |
| country | – | – | Optional ISO 3166 alpha-2 country code (e.g. 'FR', 'IN', 'US'), case-insensitive. Keeps only devices whose time zone belongs to that country. The region comes from the phone's time-zone setting, not… |
| model | string | yes | Model name, matched against resolved street name (e.g. 'Galaxy S23') or raw Build.MODEL (e.g. 'SM-S911B'). |
| Name | Type | Req | Description |
|---|---|---|---|
| ac_charge_hours | object | – | – |
| awake_ratio | object | – | – |
| battery_level_pct | object | – | – |
| brand | string | – | Lowercase Android brand identifier. |
| device_count | integer | – | Distinct devices of this model that reported snapshots. |
| discharge_hours | object | – | – |
| model | string | – | Resolved model name. |
| raw_model_code | – | – | Representative raw Android Build.MODEL identifier (e.g. 'SM-S911B') — the lexicographically smallest model code among devices grouped under this street name. Null when no device has a non-empty model… |
| region | string | – | Present only when a region filter was applied, e.g. 'country:FR' or 'continent:Asia'. |
| snapshot_count | integer | – | Sum of snapshots across all devices of this model. |
| temperature_c | object | – | – |
| url | – | – | Public BatterySnap web page for this model. Built from `raw_model_code`; null when `raw_model_code` is null. Locale-agnostic. |
| usb_charge_hours | object | – | – |
| wireless_charge_hours | object | – | – |
No examples provided.
models List models ~593
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.
| Name | Type | Req | Description |
|---|---|---|---|
| brands | – | – | One or more lowercase Android device brand identifiers (e.g. ['samsung', 'xiaomi']) to fetch models for. Matched case-insensitively. Omit (or pass an empty list) to return models across all brands. |
| fields | – | – | Optional whitelist of attribute names to keep in each returned entry, used to shrink the response. When omitted or empty, all attributes documented in the output schema are returned. Unknown names ar… |
| limit | – | – | Return at most this many models (applied after filtering and sorting). Omit for no cap. |
| max_device_count | – | – | Drop entries with more than this many recorded devices. Use to skip very common entries. Omit for no upper bound. |
| min_device_count | – | – | Drop entries with fewer than this many recorded devices. Defaults to 1 (keep all). |
| offset | – | – | Skip this many entries before returning results — use with `limit` to page through a long list. Defaults to 0. |
| sort | string | – | Sort order of the returned models: 'name' (default, alphabetical by brand then model) or 'device_count' (most recorded devices first). Combine sort='device_count' with `limit` to answer 'most popular… |
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
region_summary Battery stats by region ~355
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.
| Name | Type | Req | Description |
|---|---|---|---|
| brand | – | – | Optional lowercase brand filter. |
| continent | – | – | Optional continent, case-insensitive: 'Africa', 'Antarctica', 'Asia', 'Europe', 'North America', 'Oceania' or 'South America'. Keeps only devices whose time zone lies there. Combine with `country` fo… |
| country | – | – | Optional ISO 3166 alpha-2 country code (e.g. 'FR', 'IN', 'US'), case-insensitive. Keeps only devices whose time zone belongs to that country. The region comes from the phone's time-zone setting, not… |
| group_by | string | – | 'continent' (default) or 'country' (ISO 3166 alpha-2). |
| model | – | – | Optional model filter — matches resolved street name or raw Build.MODEL, case-insensitive. |
| Name | Type | Req | Description |
|---|---|---|---|
| group_by | string | – | 'continent' or 'country'. |
| groups | array | – | One entry per region with enough devices, most devices first. |
| min_devices_per_group | integer | – | Groups with fewer devices than this are left out of `groups` and only counted below. |
| scope | string | – | 'fleet', or the comma-joined filters applied (e.g. 'brand:samsung,continent:Europe'). |
| suppressed_device_count | integer | – | Devices in those left-out regions. |
| suppressed_group_count | integer | – | Regions left out for having too few devices. |
| unlocated_device_count | integer | – | Devices whose time zone names no place (UTC, GMT, unset): in no group, only counted here. |
No examples provided.
search Search brands and models ~148
Resolve free-form user text into the canonical brand / model identifiers the other tools expect. Meant for phones named in free text: the other tools match brands and models exactly, so a guessed spelling returns an empty list. Matching is substring-based and case-insensitive over brand, resolved model name and raw Build.MODEL, ranked by exact match then popularity.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum brand hits and model hits to return (each list is capped separately). |
| query | string | yes | Free text: a brand ('samsug'), a model name ('pixel 8'), a raw Build.MODEL code ('SM-S911B'), or both ('samsung galaxy s23'). |
| Name | Type | Req | Description |
|---|---|---|---|
| brands | array | – | Matching brands, best match first. |
| models | array | – | Matching models, best match first. |
| query | string | – | The query that was resolved. |
No examples provided.
top_devices Rank devices by metric ~485
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`).
| Name | Type | Req | Description |
|---|---|---|---|
| brand | – | – | Optional lowercase brand filter. When omitted, devices from any brand are ranked together. |
| limit | integer | – | Number of devices to return, 1..100. |
| metric | string | yes | Which battery metric to rank on. One of: 'temperature_c' (mean battery temperature, C), 'max_temperature_c' / 'min_temperature_c' (hottest / coldest ever seen, C), 'battery_level_pct' (mean charge le… |
| min_snapshots | integer | – | Ignore devices with fewer snapshots than this. Defaults to 100, which filters out barely-sampled devices whose averages are meaningless. Lower it only when a query returns too few rows. |
| model | – | – | Optional model filter — matches resolved street name or raw Build.MODEL, case-insensitive. When omitted, no model filter applies. |
| order | string | – | 'desc' (default) ranks the highest values first, 'asc' the lowest. Pick the direction that matches the question: fastest charging is ac_charge_hours + asc; longest battery life is discharge_hours + d… |
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
top_devices_by_live_uptime Top devices by live uptime ~162
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.
| Name | Type | Req | Description |
|---|---|---|---|
| brand | – | – | Optional lowercase brand filter. When omitted, devices from any brand are ranked together. |
| limit | integer | – | Number of devices to return, 1..100. |
| model | – | – | Optional model filter — matches resolved street name or raw Build.MODEL, case-insensitive. When omitted, no model filter applies. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
top_devices_by_uptime Top devices by uptime ~177
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.
| Name | Type | Req | Description |
|---|---|---|---|
| brand | – | – | Optional lowercase brand filter. When omitted, devices from any brand are ranked together. |
| limit | integer | – | Number of devices to return, 1..100. |
| model | – | – | Optional model filter — matches resolved street name or raw Build.MODEL, case-insensitive. When omitted, no model filter applies. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
top_models Rank models by metric ~560
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).
| Name | Type | Req | Description |
|---|---|---|---|
| brand | – | – | Optional lowercase brand filter. When omitted, devices from any brand are ranked together. |
| continent | – | – | Optional continent, case-insensitive: 'Africa', 'Antarctica', 'Asia', 'Europe', 'North America', 'Oceania' or 'South America'. Keeps only devices whose time zone lies there. Combine with `country` fo… |
| country | – | – | Optional ISO 3166 alpha-2 country code (e.g. 'FR', 'IN', 'US'), case-insensitive. Keeps only devices whose time zone belongs to that country. The region comes from the phone's time-zone setting, not… |
| limit | integer | – | Number of devices to return, 1..100. |
| metric | string | yes | Which battery metric to rank on. One of: 'temperature_c' (mean battery temperature, C), 'max_temperature_c' / 'min_temperature_c' (hottest / coldest ever seen, C), 'battery_level_pct' (mean charge le… |
| min_devices | integer | – | Ignore models backed by fewer devices than this. Defaults to 3 so a single outlier phone cannot win a ranking. Raise it for more robust comparisons. Raised to at least 5 when a region filter is set. |
| order | string | – | 'desc' (default) ranks the highest values first, 'asc' the lowest. Pick the direction that matches the question: fastest charging is ac_charge_hours + asc; longest battery life is discharge_hours + d… |
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
How do I install the BatterySnap MCP server?
BatterySnap is a hosted endpoint at https://mcp.battery-snap.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.battery-snap.com
claude mcp add --transport http com-battery-snap-batterysnap 'https://mcp.battery-snap.com/mcp'
What is the BatterySnap MCP server?
BatterySnap is an MCP server listed in the public MCP registry as com.battery-snap/batterysnap. Real-world Android battery stats from BatterySnap users: device, model and fleet rankings. This page covers its hosted endpoint (https://mcp.battery-snap.com/mcp).
Is the BatterySnap MCP server safe to use?
BatterySnap scores 77 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the BatterySnap MCP server expose?
BatterySnap exposes 14 tools: brands, models, devices, device_summary, model_summary, and 9 more. Their descriptions and schemas cost roughly 4,391 tokens of context every time the server is loaded.
Does the BatterySnap MCP server require authentication?
No. We connected to BatterySnap without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the BatterySnap MCP server still maintained?
BatterySnap is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.