Battery Health

BatteryHealth — connector documentation

• MCP endpoint: https://batteryhealth.connectorbay.com/mcp
• REST API: POST https://batteryhealth.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://batteryhealth.connectorbay.com/openapi.json
• Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
• Authentication: none required. An optional Authorization: Bearer <key> raises rate limits.
• Health: https://batteryhealth.connectorbay.com/health · Tool schemas: https://batteryhealth.connectorbay.com/tools.json
• Publisher: Unify Dynamics LLC · connectorbay.com/batteryhealth · agent@connectorbay.com

General, brand-neutral battery-care education only

BatteryHealth is a device-battery-health and charging-habit reference and calculator toolkit for learning and general care guidance. It is not a diagnosis of any specific device's actual battery health or remaining lifespan — real degradation depends on the specific device, battery chemistry, usage pattern, and environment; check your device's own battery-health reporting where available. Every tool response carries a disclaimer field restating this.

What BatteryHealth is for

The questions that come up when you want to make your phone, laptop, or EV battery last longer — what actually is a charge cycle, is it bad to leave a device plugged in at 100% all the time, does heat really damage batteries, roughly how many cycles has a battery been through, and what's actually different about how phone, laptop, and EV batteries should be treated — answered with real, brand-neutral lithium-ion battery science and transparent math, with no upstream calls and nothing about the user stored.

What it does

Real lithium-ion battery science by topic — charge-cycle definition, depth-of-discharge impact on longevity, heat as a degradation factor, and the real nuance around avoiding 0%/100% extremes for daily use versus when full charges are fine (battery_science); a real charge-cycle estimator that takes days-owned and a typical day's charging pattern and correctly accumulates multiple partial charges into full cycles (charge_cycle_estimator); brief, accurate, brand-neutral nuances for phone vs laptop vs EV batteries (device_type_guide); a general charging-habits checklist (charging_habits_checklist); and a glossary of core terms (battery_glossary).

What it is not

Not a battery-health app, not a diagnostic tool, and not a reader of your device's actual battery wear — charge_cycle_estimator computes genuine arithmetic from the pattern you describe, but it is an estimate from a simplified daily pattern, not a measurement of the device's real cumulative history. Device-type notes and science explanations are general, brand-neutral education, not manufacturer-specific claims about any one product.

Tools

Science & calculator

battery_science — Real, brand-neutral lithium-ion battery science by topic: charge-cycle definition, depth-of-discharge impact on longevity, heat as a degradation factor, and the real nuance around avoiding 0%/100% extremes. Args: topic (optional).

charge_cycle_estimator — Real computed math: estimates approximate total charge-cycle count from days-owned and a typical day's charging pattern, correctly accumulating multiple partial charges into full cycles. Args: days_owned, charges.

Reference

device_type_guide — Brief, accurate, brand-neutral battery nuances by device type: phone, laptop, or EV. Args: device_type.

charging_habits_checklist — A general, brand-neutral charging-habits checklist.

battery_glossary — Plain-language definitions of core battery-health terms. Args: term (optional).

Conventions

• Read-only. Every tool reads bundled reference data or computes; nothing is written anywhere and nothing about the user is stored.
• Result envelope. ok: true with data, or ok: false with a structured error (bad_input, not_found).
• Rate limits. Free tier 60 tool calls/minute and 300/day per user (keyed on a user identifier supplied by the host agent, else client IP); Pro keys raise this. Over-limit calls return HTTP 429 with Retry-After. initialize and tools/list are never counted.

Support

agent@connectorbay.com · connectorbay.com/batteryhealth/support

BatteryHealth — Privacy Policy

Effective 28 September 2026. Unify Dynamics LLC ("we", "us"), Menlo Park, California.

What BatteryHealth is. BatteryHealth is a connector (an MCP server and REST API) that AI assistants and personal agents call on your behalf for a device-battery-health and charging-habit reference toolkit: battery science by topic, a charge-cycle estimator, device-type nuances, a charging-habits checklist, and a glossary. BatteryHealth is general, brand-neutral education only. You interact with your assistant; the assistant sends us only the arguments needed for that one lookup or calculation.

What we receive. The arguments of each tool call — for example a topic name, a device type, a glossary term, or a days-owned figure and a described daily charging pattern (percentages only, no device identifiers) — the technical headers needed to serve the request (an IP address or a client identifier supplied by the assistant, and a Pro API key if you have one), and standard server logs.

Everything is answered locally and nothing is stored. BatteryHealth makes zero upstream/network calls: every response is either bundled reference data or arithmetic computed directly from the arguments given. No request is forwarded to any third party, and no query is logged in request bodies, recorded, or used to train anything.

What we do not receive or store. We do not receive your conversation with the assistant or your name, and we do not build a profile from your queries: each request is answered independently and nothing carries over between requests. We do not know your device's make, model, or serial number, or its actual battery health. Rate-limit counters (a client identifier and timestamps) are held in memory for at most 24 hours. Hosting-provider access logs, which contain IP addresses and request paths but not request bodies, are retained for up to 30 days for security and abuse prevention.

Sub-processors. None — the entire dataset is bundled with the server and every calculation runs locally. Hosting: Vercel (United States regions).

Legal bases and your rights. Our processing is necessary to provide the service you request through your assistant. Because we store no personal data beyond short-lived logs, requests to access, correct or delete personal data are usually satisfied automatically; you can still contact agent@connectorbay.com and we will respond within 30 days. We do not sell or share personal information and do not use your data to train models.

Children. BatteryHealth is a general-audience service operated by the adult using the assistant.

Changes. We will post changes here with a new effective date.

BatteryHealth — Terms of Service

Effective 28 September 2026. These terms govern use of the BatteryHealth connector ("the Service") operated by Unify Dynamics LLC ("we", "us").

1. The Service. BatteryHealth returns a device-battery-health and charging-habit reference toolkit — brand-neutral battery science, a charge-cycle estimator, device-type nuances, a charging-habits checklist, and a glossary — from commonly-cited conventions and arithmetic computed from the arguments given. It is accessed through an AI assistant or directly over MCP or HTTP.
2. General education only — not a diagnosis. BatteryHealth is not a battery-health diagnostic app, not a device manufacturer, and does not read your device's actual battery condition. Nothing the Service returns is a measurement of any specific device's real remaining lifespan or a substitute for the device's own battery-health reporting or a manufacturer's guidance.
3. No liability. To the fullest extent permitted by law, Unify Dynamics LLC is not liable for any loss or cost arising from reliance on guidance or estimates returned by the Service, including charging habits adopted or devices bought or sold on the basis of its output. Our total liability, to the extent liability cannot be excluded, is limited to US $100.
4. Figures are general conventions. Cycle-count ranges and charging guidance reflect widely-cited, general lithium-ion battery research as of the build date stated in the Service's own data; actual results vary by device, chemistry, and usage pattern.
5. Acceptable use. Automated use within the published rate limits is welcome.
6. Availability. The Service is provided "as is" without warranty. We may change, limit or discontinue it at any time.
7. Data. Our Privacy Policy describes what we process. In short: your query is answered from bundled reference data or direct computation, and nothing is stored.
8. Pro keys. Optional Pro API keys are issued at our discretion, are personal to the holder and may be revoked for abuse.
9. Governing law. California law; venue in San Mateo County, California.
10. Contact. Unify Dynamics LLC · agent@connectorbay.com · https://connectorbay.com/batteryhealth

Battery Health support

Email agent@connectorbay.com. We answer within two business days.

• MCP endpoint: https://batteryhealth.connectorbay.com/mcp
• REST API: https://batteryhealth.connectorbay.com/openapi.json
• Live status: https://batteryhealth.connectorbay.com/health

When you report a problem, include the question you asked your agent, roughly when, and which agent you used (for example Claude, ChatGPT or Gemini). Never send us passwords, account numbers or ID numbers. Battery Health never asks for them.