mcp-registry/io.github.theluckystrike/maintenance-log · v0.22.6
As of 2026-10-17 06:20 UTC, the Theluckystrike Maintenance Log MCP server is down with a Glimind reliability score of 27/100 (grade F). Over the last 30 days it answered 34.4% of Glimind's liveness checks. It had 701 outages in 90 days, with a median recovery of 39 minutes.
Equipment maintenance log: assets, service entries with costs, and a due report from stored dates.
Point your MCP client at this streamable-http endpoint: https://mcp.zovo.one/mcp/maintenance-log
The endpoint did not complete an MCP handshake.
Check the URL, TLS certificate and that the server answers a JSON-RPC "initialize" POST.
Reachable 34.4% of the time over the last 30 days; median recovery 39 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.
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably.
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/io.github.theluckystrike/maintenance-log"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/io.github.theluckystrike/maintenance-log"}) over MCP.
maintenance_log ~420 tokensasset_add ~311 tokensmaintenance_export ~225 tokensasset_remove ~202 tokensasset_history ~160 tokensStatic 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:
[](https://glimind.com/server/mcp-registry%2Fio.github.theluckystrike%2Fmaintenance-log?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fio.github.theluckystrike%2Fmaintenance-log?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.theluckystrike%2Fmaintenance-log.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.theluckystrike%2Fmaintenance-log.svg :target: https://glimind.com/server/mcp-registry%2Fio.github.theluckystrike%2Fmaintenance-log?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:165be05203433661…, first seen 2026-10-17, included at leaf 10578 of 17,017. Version history · verify what your client received.
Compare: most reliable data servers · most reliable files servers · most reliable other servers
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.
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"
}
}
}
As of 2026-10-17 06:20 UTC, the Theluckystrike Maintenance Log MCP server is down with a Glimind reliability score of 27/100 (grade F). Over the last 30 days it answered 34.4% of Glimind's liveness checks. It had 701 outages in 90 days, with a median recovery of 39 minutes.
Theluckystrike Maintenance Log MCP server advertises 8 tools, including asset_add, asset_history, asset_remove, license_activate, license_status.
Point your MCP client at this streamable-http endpoint: https://mcp.zovo.one/mcp/maintenance-log
Glimind scanned all 8 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.
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.
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.