# io.github.cronus42/ibc-mcp (remote · reloadingcalc.com)

Physics interior-ballistics solver: solves, ladders, trajectory, lookups. Published error rates.

- Trust score: 78/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `reloadingcalc.com`: 78/100 (this document), [markdown](https://verifymcp.io/servers/cronus42-ibc-mcp/reloadingcalc.md), [page](https://verifymcp.io/servers/cronus42-ibc-mcp/reloadingcalc)

## Channel facts

- Endpoint: `https://reloadingcalc.com/mcp`
- Transports: `streamable-http`
- Auth: `required (not validated)`
- Version: `1.0.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-21.

- **Endpoint Security**: 89/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - 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**: 71/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 2402 tokens (~266/item across 9 items; 6 tools + 3 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 30/100
  - Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 91/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 73% 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 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the io.github.cronus42/ibc-mcp server?

io.github.cronus42/ibc-mcp is a hosted endpoint at https://reloadingcalc.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 cronus42-ibc-mcp 'https://reloadingcalc.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "cronus42-ibc-mcp": {
      "url": "https://reloadingcalc.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "cronus42-ibc-mcp": {
      "type": "http",
      "url": "https://reloadingcalc.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.cronus42-ibc-mcp]
url = "https://reloadingcalc.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "cronus42-ibc-mcp": {
      "type": "remote",
      "url": "https://reloadingcalc.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add cronus42-ibc-mcp --url 'https://reloadingcalc.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  cronus42-ibc-mcp:
    url: "https://reloadingcalc.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "cronus42-ibc-mcp": {
      "Transport": "http",
      "Url": "https://reloadingcalc.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add cronus42-ibc-mcp -t streamable-http -u 'https://reloadingcalc.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "cronus42-ibc-mcp": {
      "type": "http",
      "url": "https://reloadingcalc.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-20 (score 78, +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.

### 2026-11-18 (score 77, +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.

### 2026-11-17 (score 76, 0)

- [security] Tool “generate_load_ladder” rewrote its description, which is the text the model reads
- [security] Tool “solve_internal_ballistics” rewrote its description, which is the text the model reads

### 2026-11-16 (score 76, +1)

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

### 2026-11-14 (score 75, +1)

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

### 2026-11-13 (score 74, 0)

- [security] Tool “solve_internal_ballistics” rewrote its description, which is the text the model reads
- [functional improvement] Stability: unverified → 0.03

### 2026-11-12 (score 74)

First indexed and scored.

## MCP tools (6)

### `solve_internal_ballistics` (~672 tokens)

Solve one internal-ballistics point: modeled velocity/energy/pressure for an exact cartridge+bullet+powder+charge specification, wrapped in the non-removable safety envelope (charge range, closed-enum warnings, assumptions). Returns the SAME envelope as POST /v1/solve. Measured accuracy: velocity averages about 7.5% error against 30,327 published loads; the pressure a user sees displayed reads 7.38% low against printed CUP figures and 0.91% low against printed psi figures at the median, so verdicts are relative — start low and work up. For load DEVELOPMENT prefer generate_load_ladder (a work-up ladder with per-rung nodes). SAFETY (verbatim policy): Returns modeled pressure and velocity from a physics solver, plus a safety envelope. This is NOT published load data. Always present the envelope, warnings, and disclaimer to the user; never state a single charge weight as a recommendation. Pressure fields (p_max_bar, p_max_psi, saami_max_bar) are modeled compliance-vs-SAAMI-ceiling indicators on the model's CUP-equivalent scale, while pressure_percent_saami is reported piezo-equivalent: the percent equals p_max_bar x 1.2783 / saami_max_bar, so it is NOT peak / ceiling as served. The factor compensates a measured model under-drive on transducer anchors; the pure CUP-to-piezo convention component is bounded near 4-8%, and the remainder is genuine under-drive retained so an over-max load cannot read safe. Not measured proof pressures and not accuracy-validated numbers: the validation corpus is velocity-only. Treat them as position relative to the ceiling, with real-world spread unknown. not_for_loading_decisions_without_published_data: this result is a model output. Do not work up a load from it alone — cross-check against published data for your exact components before loading.

Input parameters:

- `barrel_len_in` (number, required): Barrel length in inches
- `bullet` (string, required): Projectile display name ('Mfr Product (W gr)') or projectile.csv id
- `caliber` (string, required): Cartridge name or caliber.csv id
- `cartridge_oal_in`: Cartridge overall length in inches (default: caliber max OAL)
- `charge_gr` (number, required): Powder charge in grains (sanity bounds 0.1..200)
- `firearm_type`: Revolver cylinder-gap override: 'auto' (default, engine detects from caliber name), 'revolver', or 'not_revolver' (rifle/pistol)
- `powder` (string, required): Propellant name ('Alliant Blue Dot') or propellant.csv id
- `powder_temp_c`: Powder temperature in °C (optional; -29..+49 validated band, clamped outside). None = ambient (default).
- `primer`: Primer identity — accepted for forward compatibility; the engine does not model primers yet
- `weight_gr`: Bullet weight override in grains (optional). For cast bullets: same mold, different alloy, different weight (a LEE C358-158-SWC can drop 137 gr in pewter/tin vs 158 gr catalog nominal). None = catalo…

### `generate_load_ladder` (~526 tokens)

PREFERRED for load development: generate a work-up ladder (>=5 rungs required — coarser requests are refused LADDER_TOO_COARSE, never silently interpolated) from the published-reference or charge-only bookends down, with per-rung trajectory nodes and the full safety envelope. Requires an API key or subscriber token — anonymous callers are refused pre-compute. Returns the SAME envelope as POST /v1/ladder. SAFETY (verbatim policy): Returns modeled pressure and velocity from a physics solver, plus a safety envelope. This is NOT published load data. Always present the envelope, warnings, and disclaimer to the user; never state a single charge weight as a recommendation. Pressure fields (p_max_bar, p_max_psi, saami_max_bar) are modeled compliance-vs-SAAMI-ceiling indicators on the model's CUP-equivalent scale, while pressure_percent_saami is reported piezo-equivalent: the percent equals p_max_bar x 1.2783 / saami_max_bar, so it is NOT peak / ceiling as served. The factor compensates a measured model under-drive on transducer anchors; the pure CUP-to-piezo convention component is bounded near 4-8%, and the remainder is genuine under-drive retained so an over-max load cannot read safe. Not measured proof pressures and not accuracy-validated numbers: the validation corpus is velocity-only. Treat them as position relative to the ceiling, with real-world spread unknown. not_for_loading_decisions_without_published_data: this result is a model output. Do not work up a load from it alone — cross-check against published data for your exact components before loading.

Input parameters:

- `barrel_len_in` (number, required): Barrel length in inches
- `bullet` (string, required): Projectile display name or projectile.csv id
- `caliber` (string, required): Cartridge name or caliber.csv id
- `cartridge_oal_in`: Cartridge overall length in inches (default: caliber max OAL)
- `charge_gr`: Current charge (enables sensitivity + next-rung marker)
- `firearm_type`: Revolver cylinder-gap override: 'auto' (default), 'revolver', or 'not_revolver' (rifle/pistol)
- `n_rungs` (integer): Number of ladder rungs (3–10, default 7)
- `powder` (string, required): Propellant name or propellant.csv id
- `powder_temp_c`: Powder temperature in °C (optional; -29..+49 validated band)
- `primer`: Primer identity — accepted for forward compatibility

### `trajectory` (~582 tokens)

Trajectory / drop table: point-mass (3-DOF) exterior solve fed by the modeled muzzle velocity for an exact cartridge+bullet+powder+charge spec (or an explicit muzzle_velocity_fps override). Returns range rows (drop, velocity, energy, windage) plus the model assumptions. Beta keys get the table to 300 yd (the same PREFIX the web free tier gets); subscriber keys get the full table. No pressure figures on this surface. SAFETY (verbatim policy): Returns modeled pressure and velocity from a physics solver, plus a safety envelope. This is NOT published load data. Always present the envelope, warnings, and disclaimer to the user; never state a single charge weight as a recommendation. Pressure fields (p_max_bar, p_max_psi, pressure_percent_saami, saami_max_bar) are modeled compliance-vs-SAAMI-ceiling indicators, not measured proof pressures and not accuracy-validated numbers: the validation corpus is velocity-only. Treat them as position relative to the ceiling, with real-world spread unknown. not_for_loading_decisions_without_published_data: this result is a model output. Do not work up a load from it alone — cross-check against published data for your exact components before loading.

Input parameters:

- `barrel_len_in` (number, required): Barrel length in inches
- `bc_lb_in2`: Ballistic coefficient override; default = catalog g7bc (else g1bc) for the bullet
- `bullet` (string, required): Projectile display name ('Mfr Product (W gr)') or projectile.csv id
- `caliber` (string, required): Cartridge name or caliber.csv id
- `cartridge_oal_in`
- `charge_gr` (number, required): Powder charge in grains
- `drag_function`: Drag standard of `bc_lb_in2`; default G1 for an override, otherwise whichever catalog BC was used
- `firearm_type`
- `max_range_yd` (number)
- `muzzle_velocity_fps`: Override; default = the engine's v_max_fps for this load
- `powder` (string, required): Propellant name or propellant.csv id
- `powder_temp_c`
- `pressure_hpa` (number)
- `primer`
- `sight_height_in` (number)
- `step_yd` (number)
- `temp_c` (number)
- `weight_gr`: Bullet weight override in grains (optional). For cast bullets: same mold, different alloy, different weight (a LEE C358-158-SWC can drop 137 gr in pewter/tin vs 158 gr catalog nominal). None = catalo…
- `wind_mph` (number): Full-value crosswind, left -> right
- `zero_range_yd` (number)

### `get_cartridge_spec` (~117 tokens)

Look up ONE cartridge in the served component database (census: mode != 'hidden' AND geloescht == 0) by name, CIP name, alternate name, or id — returns the published dimensional spec (pmax_bar, case volume, bore/case dimensions, max OAL). Identity + published dimensional metadata only — NOT load data (rights-class discipline): no charge/velocity/pressure values are served by this tool.

Input parameters:

- `cartridge` (string, required): Cartridge name, CIP name, alternate name, or numeric id

### `list_powders` (~87 tokens)

List propellants in the served database (optionally filtered by manufacturer substring), with the GRT attributes the solver uses (Ba, Qex). Identity + published dimensional metadata only — NOT load data (rights-class discipline): no charge/velocity/pressure values are served by this tool.

Input parameters:

- `manufacturer` (string): Optional manufacturer substring filter (e.g. 'Hodgdon')

### `check_component_compatibility` (~132 tokens)

Check whether a cartridge+powder pair RESOLVES in the served database and whether the published-reference corpus contains a row for the pair (nearest-bullet membership — the same membership that decides a ladder's basis). Answers membership and canonical identity ONLY; it never serves the corpus row's numbers. Identity + published dimensional metadata only — NOT load data (rights-class discipline): no charge/velocity/pressure values are served by this tool.

Input parameters:

- `bullet_gr` (number): Bullet weight in grains (optional; enables corpus-membership answer)
- `cartridge` (string, required)
- `powder` (string, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/cronus42-ibc-mcp/reloadingcalc#diagnostics

## Score history

- 2026-11-21: 78
- 2026-11-20: 78
- 2026-11-19: 77
- 2026-11-18: 77
- 2026-11-17: 76
- 2026-11-16: 76
- 2026-11-15: 75
- 2026-11-14: 75
- 2026-11-13: 74
- 2026-11-12: 74

## Common questions

### What is the io.github.cronus42/ibc-mcp server?

io.github.cronus42/ibc-mcp is listed in the public MCP registry as io.github.cronus42/ibc-mcp. Physics interior-ballistics solver: solves, ladders, trajectory, lookups. Published error rates. This page covers its hosted endpoint (https://reloadingcalc.com/mcp).

### Is the io.github.cronus42/ibc-mcp server safe to use?

io.github.cronus42/ibc-mcp scores 78 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 io.github.cronus42/ibc-mcp server expose?

io.github.cronus42/ibc-mcp exposes 6 tools: solve_internal_ballistics, generate_load_ladder, trajectory, get_cartridge_spec, list_powders, check_component_compatibility. Their descriptions and schemas cost roughly 2,116 tokens of context every time the server is loaded.

### Does the io.github.cronus42/ibc-mcp server require authentication?

Yes. io.github.cronus42/ibc-mcp asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the io.github.cronus42/ibc-mcp server still maintained?

io.github.cronus42/ibc-mcp is still listed as active in the MCP registry. We last reached this channel on 21 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 io.github.cronus42/ibc-mcp server?

VerifyMCP ran 13 checks on io.github.cronus42/ibc-mcp, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. 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://reloadingcalc.com/mcp
- Changelog RSS feed: https://verifymcp.io/servers/cronus42-ibc-mcp/reloadingcalc.xml
- Changelog JSON feed: https://verifymcp.io/servers/cronus42-ibc-mcp/reloadingcalc/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/cronus42-ibc-mcp/reloadingcalc.json
- HTML version of this page: https://verifymcp.io/servers/cronus42-ibc-mcp/reloadingcalc
