io.github.theluckystrike/aging
io.github.theluckystrike/aging
Is the io.github.theluckystrike/aging MCP server down? Yes. It has given no valid answer since 2026-10-31: install failed.
Age your receivables into 0-30, 31-60, 61-90 and over 90 day buckets by due date.
install failed down since 2026-10-31 · probed 2026-11-15 · unchanged since 2026-11-07
the bundle does not match the SHA-256 in the registry entry
- Bundle
- https://github.com/theluckystrike/mcp-servers/releases/download/v0.22.0/statement-of-account.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/statement-of-account
- 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.
- Limoni io.github.thebanri/limoni-mcp · alive
- io.github.thecolourfoundation/rune · needs env
- battlemap-mcp io.github.thekannen/battlemap-mcp · alive
- el-mcp-server io.github.thekuwayama/el-mcp-server · crashed on start
- io.github.theluckystrike/agreement · install failed
- io.github.theluckystrike/application · install failed
- io.github.theluckystrike/appointment · install failed
- io.github.theluckystrike/archive · install failed
Servers that mention aging.
- AgentDM: Agent to Agent Communication Platform ai.agentdm/agentdm · needs auth
- ai.izap/whatsapp · needs auth
- ai.oddsockets/remote-mcp · alive
- Relaystation ai.relaystation/relaystation · alive
- ai.smithery/Funding-Machine-ghl-mcp-fundingmachine · not found
- Pixly app.pixly/pixly · alive
- Tonebook Palette app.tonebook/palette · alive
- WaAPI app.waapi/waapi · needs auth
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.
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
- No valid answer since 2026-10-31, in every probe since then.
- 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.