Remote MCP · Endpoint

IronLedger strength calculators MCP server

No. IronLedger strength calculators answered an MCP handshake 4 hours ago.

UpLast checked 4 hours ago

Server URL

https://www.ironledger.app/mcp

The last check completed an MCP handshake.

Registry name
app.ironledger/strength-calculators
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
80 ms
Tools exposed
9 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Free strength-training calculators, plus a checker for program files you import into IronLedger.
Listing
From the official MCP registry (active).
Recent checks of IronLedger strength calculators
CheckedResultHandshake
4 hours agoHandshake completed80 ms
10 days agoHandshake completed106 ms
11 days agoHandshake completed102 ms
11 days agoHandshake completed260 ms
13 days agoHandshake completed97 ms
14 days agoHandshake completed68 ms
15 days agoHandshake completed100 ms
16 days agoHandshake completed87 ms
17 days agoHandshake completed69 ms
19 days agoHandshake completed110 ms
22 days agoHandshake completed68 ms
24 days agoHandshake completed102 ms
26 days agoHandshake completed102 ms
29 days agoHandshake completed123 ms

The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 15 responding of 15.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with IronLedger strength calculators and makes no claim about it beyond what these checks measured.