Skip to content

ibc-mcp server

io.github.cronus42/ibc-mcpcronus42streamable-httpv1.0.0Scanned

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

6 tools: 4 change things and 2 only read.

Tools: 0 delete, 0 irreversible, 4 write, 2 read.
  • Reads private data · 2
  • Reads text others write · 0
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

4 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the ibc-mcp server can do

The ibc-mcp server is published by the GitHub account cronus42. It has 6 tools. It can create or change data (4 tools: solve_internal_ballistics, generate_load_ladder, trajectory and check_component_compatibility), but cannot delete data. 2 tools only read.

2 tools read private data (get_cartridge_spec and list_powders).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 12, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

6 tools

Changes things 4Claude Code: ask
  • check_component_compatibilityCheck 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 m…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.
  • generate_load_ladderPREFERRED for load development: generate a work-up ladder (>=5 rungs required — coarser requests are refused LADDER_TOO_COARSE, never silently interpolated) from the published-refe…No findings

    Why it is in this group

    • The name "generate_load_ladder" says "generate": a word for a change.
    Description, as the server wrote it
    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. 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.
  • solve_internal_ballisticsSolve one internal-ballistics point: modeled velocity/energy/pressure for an exact cartridge+bullet+powder+charge specification, wrapped in the non-removable safety envelope (charg…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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. 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. 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.
  • trajectoryTrajectory / 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 o…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.
Only reads 2Show 2 read-only tools
  • get_cartridge_specLook 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 sp…Reads private dataNo findings

    Why it is in this group

    • The name "get_cartridge_spec" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "database": it reads databases.
    Description, as the server wrote it
    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.
  • list_powdersList propellants in the served database (optionally filtered by manufacturer substring), with the GRT attributes the solver uses (Ba, Qex).Reads private dataNo findings

    Why it is in this group

    • The name "list_powders" says "list": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "list" and "database": it reads databases.
    Description, as the server wrote it
    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.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged untrusted-input or outbound.

Reads private data2
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 19, 2026, 17:21 UTC, unchanged since Nov 12, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
4
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 4 tools that change things (4 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://reloadingcalc.com/mcp: tools/list returned 6 tools to an anonymous client, including solve_internal_ballistics (write), generate_load_ladder (write), trajectory (write), check_component_compatibility (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http ibc https://reloadingcalc.com/mcp
claude mcp add --transport http ibc https://reloadingcalc.com/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__ibc__get_cartridge_spec",
      "mcp__ibc__list_powders"
    ],
    "ask": [
      "mcp__ibc__solve_internal_ballistics",
      "mcp__ibc__generate_load_ladder",
      "mcp__ibc__trajectory",
      "mcp__ibc__check_component_compatibility"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as ibc. Review it before you use it.

Capability tags behind 2 rules
  • mcp__ibc__get_cartridge_spec private-data
  • mcp__ibc__list_powders private-data

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.cronus42/ibc-mcp/verify?hash=547430b0e90079294932518c06e2634f37aafddbd09f803e4993d9586355dc9c" | jq -e '.changed == false'

Pinned hash 547430b0e900, from Nov 12, 2026, 07:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.cronus42/ibc-mcp/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.cronus42/ibc-mcp
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.cronus42/ibc-mcp.svg)](https://radar.anlyon.com/servers/io.github.cronus42/ibc-mcp)

Source: MCP Registry. Synced Nov 12, 2026, 07:18 UTC.

ibc-mcp server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the ibc-mcp server safe?

No scan can promise that. What its definitions show: 6 tools, 4 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the ibc-mcp server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the ibc-mcp server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the ibc-mcp server have?

6 tools: 4 write, 2 read. solve_internal_ballistics, generate_load_ladder, trajectory, check_component_compatibility, get_cartridge_spec and list_powders.

Does the ibc-mcp server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the ibc-mcp server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the ibc-mcp server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 12, 2026.