# Oxbox Energy product catalogue (remote · mcp.oxboxenergy.com)

The Oxbox 48 V battery energy storage system: specifications, certifications and how to get a quote.

- Trust score: 69/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `mcp.oxboxenergy.com`: 69/100 (this document), [markdown](https://verifymcp.io/servers/com-oxboxenergy-product-catalog/mcp.md), [page](https://verifymcp.io/servers/com-oxboxenergy-product-catalog/mcp)

## Channel facts

- Endpoint: `https://mcp.oxboxenergy.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.2.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 75/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 720 tokens (~120/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 20/100
  - Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 97/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 91% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Oxbox Energy product catalogue MCP server?

Oxbox Energy product catalogue is a hosted endpoint at https://mcp.oxboxenergy.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.

### Claude

```bash
claude mcp add --transport http com-oxboxenergy-product-catalog 'https://mcp.oxboxenergy.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-oxboxenergy-product-catalog": {
      "url": "https://mcp.oxboxenergy.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-oxboxenergy-product-catalog": {
      "type": "http",
      "url": "https://mcp.oxboxenergy.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-oxboxenergy-product-catalog]
url = "https://mcp.oxboxenergy.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-oxboxenergy-product-catalog": {
      "type": "remote",
      "url": "https://mcp.oxboxenergy.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-oxboxenergy-product-catalog --url 'https://mcp.oxboxenergy.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-oxboxenergy-product-catalog:
    url: "https://mcp.oxboxenergy.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-oxboxenergy-product-catalog": {
      "Transport": "http",
      "Url": "https://mcp.oxboxenergy.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-oxboxenergy-product-catalog -t streamable-http -u 'https://mcp.oxboxenergy.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-oxboxenergy-product-catalog": {
      "type": "http",
      "url": "https://mcp.oxboxenergy.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-02 (score 68, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-31 (score 67, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-30 (score 66)

First indexed and scored.

## MCP tools (6)

### `search` (~89 tokens)

Search Oxbox Energy

Search the Oxbox Energy website for stationary batteries, chargers and DC power: product pages, datasheets, discharge tables, manuals, SDS and technical articles. Ask in plain words, e.g. "12 V gel battery for solar" or "OPzS 2V cell SDS". Returns ids, titles and source links; read one with fetch.

Input parameters:

- `query` (string, required): What to look for.

### `fetch` (~73 tokens)

Read a page or document

Read the full text of one result from search (a web page, a PDF, or a product series) with its link. A discharge table returns its figures once it has been checked against its datasheet, otherwise the link and page.

Input parameters:

- `id` (string, required): An id returned by search, find_series or get_documents.

### `find_series` (~185 tokens)

Find a battery series

Find a stationary battery or product series that Oxbox Energy offers by chemistry (VRLA gel, AGM, flooded, pure lead, lithium), nominal voltage (2 V, 6 V, 12 V, 48 V ...) or application (telecom, utility, solar, UPS, switchgear). Returns each series with its product page and documents.

Input parameters:

- `application` (string): e.g. telecom, utility, solar, UPS, switchgear
- `chemistry` (string): e.g. gel, AGM, flooded, pure lead, lithium
- `include_discontinued` (boolean): Include series the site marks as discontinued (default false).
- `text` (string): Words from the series name or model, e.g. "OPzV" or "NSB 190FT"
- `voltage` (string): Nominal voltage, e.g. "12 V"

### `get_documents` (~83 tokens)

List datasheets, manuals and SDS

List the documents Oxbox Energy publishes for a series, or of one type across the site: datasheet, discharge_table, manual, sds, certificate, standard, brochure, technical_paper, warranty. Third-party documents are linked at their source.

Input parameters:

- `series` (string): A series id from find_series, or its name
- `type` (string)

### `quote_request` (~82 tokens)

How to request a quote

How to ask Oxbox Energy for a quote or price: the address to write to, and what to include so the engineers can answer without a round of questions. It sends nothing; the customer sends the request themselves.

Input parameters:

- `application` (string): Optional: what it is for
- `series` (string): Optional: the series or product the quote is for

### `sizing_tool` (~52 tokens)

How to get a system sized

Oxbox Energy has NO online sizing tool, and this connector cannot size a system. This says how to get one sized: the customer sends the load, runtime and voltage with a quote request and the engineers size it.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-oxboxenergy-product-catalog/mcp#diagnostics

## Score history

- 2026-11-05: 69
- 2026-11-04: 69
- 2026-11-03: 68
- 2026-11-02: 68
- 2026-11-01: 67
- 2026-10-31: 67
- 2026-10-30: 66

## Common questions

### What is the Oxbox Energy product catalogue MCP server?

Oxbox Energy product catalogue is an MCP server listed in the public MCP registry as com.oxboxenergy/product-catalog. The Oxbox 48 V battery energy storage system: specifications, certifications and how to get a quote. This page covers its hosted endpoint (https://mcp.oxboxenergy.com/mcp).

### Is the Oxbox Energy product catalogue MCP server safe to use?

Oxbox Energy product catalogue scores 69 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 Oxbox Energy product catalogue MCP server expose?

Oxbox Energy product catalogue exposes 6 tools: search, fetch, find_series, get_documents, quote_request, sizing_tool. Their descriptions and schemas cost roughly 564 tokens of context every time the server is loaded.

### Does the Oxbox Energy product catalogue MCP server require authentication?

No. We connected to Oxbox Energy product catalogue without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Oxbox Energy product catalogue MCP server still maintained?

Oxbox Energy product catalogue 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.

### What did VerifyMCP test on the Oxbox Energy product catalogue MCP server?

VerifyMCP ran 12 checks on Oxbox Energy product catalogue, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Oxbox Energy product catalogue: HTTPS. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://mcp.oxboxenergy.com/mcp
- Website: https://oxboxenergy.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-oxboxenergy-product-catalog/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-oxboxenergy-product-catalog/mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-oxboxenergy-product-catalog/mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-oxboxenergy-product-catalog/mcp