Is the Calc MCP server down?

mcp-registry/engineer.calc/calc · v1.0.0

down
Last checked 2026-10-23 20:35 UTC · handshake 431ms

As of 2026-10-23 20:35 UTC, the Calc MCP server is down with a Glimind reliability score of 38/100 (grade F). Over the last 30 days it answered 95% of Glimind's liveness checks. It had 57 outages in 90 days, with a median recovery of 25.5 hours.

uptime (30d checks)
95%
checks observed
2,204
outages (90d)
57
tools
89

88 free engineering calculators: RF link budgets, LoRa/Meshtastic, PCB, solar, homelab. Keyless.

Point your MCP client at this streamable-http endpoint: https://calc.engineer/mcp

Agent-readiness: D (68/100)

D (68/100): 1 error(s), 6 warning(s) across 89 tool(s); ~32,482 tokens of tool definitions.
Scores higher than 3% of 15,594 MCP servers Glimind has audited.
Its tool list costs an agent ~32,482 tokens per session — more than 95% of servers.
71 → 71 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions100
Safety hints16
Token cost35
Client compatibility100
Protocol100
Reliability0
Stability100

What to fix (7)

The endpoint did not complete an MCP handshake.

Check the URL, TLS certificate and that the server answers a JSON-RPC "initialize" POST. How to fix →

89 of 89 tool(s) carry no readOnlyHint/destructiveHint annotations.

Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →

Tools: attenuator_pi, attenuator_tee, battery_autonomy, battery_charge_time, battery_life and 84 more

89 tools on one server. Tool-selection accuracy drops as the menu grows, and some clients (e.g. Cursor) cap the number of active tools.

Group tools by task into smaller servers or toolsets, and merge near-duplicates behind one tool with a mode parameter. How to fix →

4 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.

Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →

Tools: battery_charge_time, capacitor_charge, ups_runtime, voltage_drop

Loading this server's tool list costs an agent ~32,482 tokens before any work — more than 95% of MCP servers.

Split rarely-used tools into a separate server or a toolset the client can enable, or expose one "search tools" entry point. Many agents load every connected server's tools into every request. How to fix →

Reachable 95.0% of the time over the last 30 days; median recovery 1531 min.

Agents fail over to an alternative the first time a call fails. Add health checks and restart-on-failure, and avoid cold starts on serverless hosts.

Handshake + tools/list takes ~2,525 ms.

Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.

Auto-fix: 9 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fengineer.calc%2Fcalc/fixes

battery_charge_time 1 change
{
  "name": "battery_charge_time",
  "description": "Estimates battery charge time given capacity in mAh, charge current in mA, charger efficiency, and initial state of charge. Accounts for real-world charging losses (typically 80-90% efficient) to produce time in hours and minutes, energy required in Wh (at an optional voltage, default 3.7V for Li-ion), and the C-rate of the charge. Useful for solar charge controller sizing, USB charging time estimation, lead-acid float charging, and EV battery planning. The C-rate output helps verify the charge ",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "capacity_mah",
      "charge_current_ma"
    ],
    "properties": {
      "voltage_v": {
        "type": "number",
        "default": 3.7,
        "description": "Nominal battery voltage for energy calculation (V), default 3.7 for Li-ion",
        "exclusiveMinimum": 0
      },
      "efficiency": {
        "type": "number",
        "default": 0.85,
        "maximum": 1,
        "minimum": 0,
        "description": "Charger efficiency factor (0-1), default 0.85"
      },
      "capacity_mah": {
        "type": "number",
        "description": "Total battery capacity in milliamp-hours (mAh)",
        "exclusiveMinimum": 0
      },
      "initial_soc_pct": {
        "type": "number",
        "default": 0,
        "maximum": 100,
        "minimum": 0,
        "description": "Initial state of charge as percentage (0-100), default 0 (empty)"
      },
      "charge_current_ma": {
        "type": "number",
        "description": "Charge current in milliamps (mA)",
        "exclusiveMinimum": 0
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  },
  "title": "battery charge time"
}
capacitor_charge 1 change
{
  "name": "capacitor_charge",
  "description": "Calculates RC capacitor charge timing, energy storage, and transient voltages. Given resistance, capacitance, supply voltage, and optional initial voltage, computes the RC time constant (τ = R×C), time to reach standard charge thresholds (63%, 86%, 95%, 99%), voltage at key time points, energy stored (E = ½CV²), and peak charging current. Optionally calculates time to reach a specific target voltage using t = -τ × ln((Vsupply - Vtarget) / (Vsupply - Vinitial)). Essential for timing circuits, pow",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "resistance_ohm",
      "capacitance_f",
      "v_supply"
    ],
    "properties": {
      "v_supply": {
        "type": "number",
        "description": "Supply voltage in volts. The voltage the capacitor charges toward.",
        "exclusiveMinimum": 0
      },
      "v_target": {
        "type": "number",
        "description": "Target voltage to reach in volts (optional). When provided, calculates time to reach this voltage. Must be between v_initial and v_supply."
      },
      "v_initial": {
        "type": "number",
        "default": 0,
        "description": "Initial capacitor voltage in volts (default 0 for fully discharged)."
      },
      "capacitance_f": {
        "type": "number",
        "description": "Capacitance in farads (C). Use scientific notation, e.g. 1e-6 for 1 µF.",
        "exclusiveMinimum": 0
      },
      "resistance_ohm": {
        "type": "number",
        "description": "Series resistance in ohms (R). Controls charge/discharge rate.",
        "exclusiveMinimum": 0
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  },
  "title": "capacitor charge"
}
dbm_convert 1 change
{
  "name": "dbm_convert",
  "description": "Convert a power level in dBm to milliwatts, watts, dBW, and RMS voltage across a given impedance. dBm is the standard unit for RF power referenced to 1 milliwatt. This tool is essential when interfacing datasheets (which use dBm) with circuit analysis (which uses volts and watts). Default impedance is 50 ohms, matching most RF systems. Use this to quickly verify power amplifier output, receiver sensitivity, or regulatory EIRP limits.",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "dbm"
    ],
    "properties": {
      "dbm": {
        "type": "number",
        "description": "Power level in dBm (decibels relative to 1 milliwatt)"
      },
      "impedance_ohm": {
        "type": "number",
        "default": 50,
        "description": "Load impedance in ohms for Vrms calculation (default 50)",
        "exclusiveMinimum": 0
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": true
  },
  "title": "dbm convert"
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/engineer.calc/calc"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/engineer.calc/calc"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

Markdown
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fengineer.calc%2Fcalc.svg)](https://glimind.com/server/mcp-registry%2Fengineer.calc%2Fcalc?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fengineer.calc%2Fcalc?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fengineer.calc%2Fcalc.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fengineer.calc%2Fcalc.svg
   :target: https://glimind.com/server/mcp-registry%2Fengineer.calc%2Fcalc?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:59fc1d69185bdb4a…, first seen 2026-10-17, included at leaf 119 of 54,527. Version history · verify what your client received.

Working alternatives

Tools (89)

Compare: most reliable other servers · most reliable data servers · most reliable finance servers · most reliable ml servers · most reliable code servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Calc MCP server down right now?

As of 2026-10-23 20:35 UTC, the Calc MCP server is down with a Glimind reliability score of 38/100 (grade F). Over the last 30 days it answered 95% of Glimind's liveness checks. It had 57 outages in 90 days, with a median recovery of 25.5 hours.

How many tools does Calc MCP server provide?

Calc MCP server advertises 89 tools, including attenuator_pi, attenuator_tee, battery_autonomy, battery_charge_time, battery_life.

How do I install Calc MCP server?

Point your MCP client at this streamable-http endpoint: https://calc.engineer/mcp

Is the Calc MCP server safe to connect to an AI agent?

Glimind scanned all 89 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Calc MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.

Feedback
Help us improve