io.github.theluckystrike/currency

Is the io.github.theluckystrike/currency MCP server down? It gave no valid answer in the probe of 2026-11-11: install failed. One failed probe is not an outage.

Convert currencies on the daily European Central Bank reference rates. No API key, no signup.

install failed no valid answer since 2026-11-11 · probed 2026-11-15 · unchanged since 2026-11-11

the bundle does not match the SHA-256 in the registry entry

Bundle: https://github.com/theluckystrike/mcp-servers/releases/download/v0.22.0/currency.mcpb (MCPB, for a client that installs bundles; probed in a container with the network off)
Host: github.com
Repository: https://github.com/theluckystrike/mcp-servers
Website: https://mcp.zovo.one/s/currency
Registry: active, updated 2026-10-14 · registry entry

Compare this server with others.

More servers

Other registry entries on github.com, the ones next to this name; all of them.

io.github.theluckystrike/career · install failed
io.github.theluckystrike/cash-float · install failed
io.github.theluckystrike/cashflow · install failed
io.github.theluckystrike/clauses · install failed
io.github.theluckystrike/delegacja · install failed
io.github.theluckystrike/delivery-schedule · install failed
io.github.theluckystrike/deposit · install failed
io.github.theluckystrike/documents · install failed

Servers that mention currency.

ai.smithery/anirbanbasu-frankfurtermcp · not found
ai.smithery/jessicayanwang-test · not found
ai.smithery/truss44-mcp-crypto-price · needs auth
FlatCash — Native Currency for AI Agents cash.flat/flatcash · needs auth
Exchange Rate MCP cn.pianam.mcp/exchange-rate-mcp · alive
com.abundanceapis/abundance-apis · alive
CryptoQuant com.cryptoquant/mcp-server · needs auth
CurrencyGuard Guard Pricing com.currencyguard/guard-pricing · alive

Badge for the README

The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.

Atom feed

A mail when this server changes

Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.

For the publisher

The package did not start as an MCP server at its probe on 2026-11-11. One failed probe is not an outage: the board calls a package down when it fails again at its next probe, a week later.
npx or uvx could not install the package. The package name in the registry entry is wrong, the package is not published, or the install needs a build step.