Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Battery Figures: used Tesla battery health by VIN

REMOTE · API.BATTERYFIGURES.COM

Used Tesla battery health (SoH) by VIN: pack, original kWh, typical capacity left. Model S, 3, X, Y.

74 Trust /100

Last scanned (5 hours ago)

Scores higher than 62% of remote servers

Reachable. Last reached 5 Nov 2026.

Trust breakdown (7 categories)

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 Security80
Transport & Reachability100
Schema Quality & AI Usability79
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 71 tokens (~71/item across 1 items; 1 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 1 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass

Unverified: 1 category

A category scored 0 because we could not verify it: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

Changelog

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.

  • 5 Nov 26 74

    First indexed and scored.

Diagnostics

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 5 Nov 2026 · Probed https://api.batteryfigures.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=api.batteryfigures.com CN=WE1,O=Google Trust Services,C=US 10 Oct 2026 8 Jan 2027 ECDSA 256 ECDSA-SHA256 63369cdd660404030ef7aeef3baac07a
SANs: api.batteryfigures.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of api.batteryfigures.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
batteryfigures.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
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
Header Value
strict-transport-security max-age=31536000; includeSubDomains
x-content-type-options nosniff

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://api.batteryfigures.com/mcp Verified 200
http (plaintext) http://api.batteryfigures.com/mcp HTTPS enforced 301 https://api.batteryfigures.com/mcp
MCP tools · 1 exposed · ~71 tokens

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 →

Tool Tokens
preview_vin ~71

Free preview of a used Tesla’s battery by VIN. Never calls Tesla. Returns the pack, its original capacity, the normal capacity left at this age and next.url where the user buys Tesla’s own figure for this exact car.

NameTypeReqDescription
vinstringyesThe 17-character VIN of the used Tesla.

No output schema declared.

No examples provided.

Install

How do I install the Battery Figures: used Tesla battery health by VIN MCP server?

Battery Figures: used Tesla battery health by VIN is a hosted endpoint at https://api.batteryfigures.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 · api.batteryfigures.com

# add to Claude Code
claude mcp add --transport http zyberse-batteryfigures 'https://api.batteryfigures.com/mcp'
Common questions

What is the Battery Figures: used Tesla battery health by VIN MCP server?

Battery Figures: used Tesla battery health by VIN is an MCP server listed in the public MCP registry as io.github.ZyberSE/batteryfigures. Used Tesla battery health (SoH) by VIN: pack, original kWh, typical capacity left. Model S, 3, X, Y. This page covers its hosted endpoint (https://api.batteryfigures.com/mcp).

Is the Battery Figures: used Tesla battery health by VIN MCP server safe to use?

Battery Figures: used Tesla battery health by VIN scores 74 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 Battery Figures: used Tesla battery health by VIN MCP server expose?

Battery Figures: used Tesla battery health by VIN exposes 1 tool: preview_vin. Their descriptions and schemas cost roughly 71 tokens of context every time the server is loaded.

Does the Battery Figures: used Tesla battery health by VIN MCP server require authentication?

No. We connected to Battery Figures: used Tesla battery health by VIN without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Battery Figures: used Tesla battery health by VIN MCP server still maintained?

Battery Figures: used Tesla battery health by VIN is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.