io.github.theluckystrike/maintenance-log
REMOTE · MCP.ZOVO.ONE · 2 COMPONENTS · SCANNED SEP 20
Equipment maintenance log: assets, service entries with costs, and a due report from stored dates.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security89
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token. See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability86
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1103 tokens (~122/item across 9 items; 8 tools + 1 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management10
- Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "asset_remove" implies "remove" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.theluckystrike/maintenance-log MCP server?
io.github.theluckystrike/maintenance-log is a hosted endpoint at https://mcp.zovo.one/mcp/maintenance-log, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.zovo.one
claude mcp add --transport http theluckystrike-maintenance-log 'https://mcp.zovo.one/mcp/maintenance-log'
{
"mcpServers": {
"theluckystrike-maintenance-log": {
"url": "https://mcp.zovo.one/mcp/maintenance-log"
}
}
} {
"servers": {
"theluckystrike-maintenance-log": {
"type": "http",
"url": "https://mcp.zovo.one/mcp/maintenance-log"
}
}
} [mcp_servers.theluckystrike-maintenance-log] url = "https://mcp.zovo.one/mcp/maintenance-log"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"theluckystrike-maintenance-log": {
"type": "remote",
"url": "https://mcp.zovo.one/mcp/maintenance-log",
"enabled": true
}
}
} openclaw mcp add theluckystrike-maintenance-log --url 'https://mcp.zovo.one/mcp/maintenance-log' --transport streamable-http
mcp_servers:
theluckystrike-maintenance-log:
url: "https://mcp.zovo.one/mcp/maintenance-log" {
"McpServers": {
"theluckystrike-maintenance-log": {
"Transport": "http",
"Url": "https://mcp.zovo.one/mcp/maintenance-log"
}
}
} assistant mcp add theluckystrike-maintenance-log -t streamable-http -u 'https://mcp.zovo.one/mcp/maintenance-log'
{
"mcpServers": {
"theluckystrike-maintenance-log": {
"type": "http",
"url": "https://mcp.zovo.one/mcp/maintenance-log"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 0
- Stability: unverified → 0.03 ▲ functional
- 17 Sept 26 78
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Probed https://mcp.zovo.one/mcp/maintenance-log
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=zovo.one | CN=WE1,O=Google Trust Services,C=US | 2 Sept 2026 | 1 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | ef74739bd6e575bb13db69661e215324 |
| SANs: zovo.one, mcp.zovo.one, *.mcp.zovo.one | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.zovo.one. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| one. | present | 64939 | 8 | Verified |
| zovo.one. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer realm="mcp.zovo.one", error="invalid_token"
Bearer realm="mcp.zovo.one", error="invalid_token"| Header | Value |
|---|---|
| strict-transport-security | max-age=15552000; includeSubDomains; preload |
| x-content-type-options | nosniff |
Protected resource metadata
| Retrieved | No |
|---|---|
| Problem | no_resource_metadata |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.zovo.one/mcp/maintenance-log | Verified | 200 | |
| http (plaintext) | http://mcp.zovo.one/mcp/maintenance-log | HTTPS enforced | 301 | https://mcp.zovo.one/mcp/maintenance-log |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
asset_add Add an asset to the register ~206
Add one piece of equipment to the maintenance register: its name, its serial or asset tag, where it lives, and the currency its costs are in. Returns the AST-YYYY-NNNN id. Free tier: 3 assets; logging work on the assets you have is never metered.
| Name | Type | Req | Description |
|---|---|---|---|
| currency | string | – | ISO code the costs are in. Default USD |
| location | string | – | Where the asset lives, e.g. Workshop bay 2, or 14 Nowa Street, flat 3 |
| name | string | yes | What the asset is called, e.g. Lathe, Combi boiler, Van 2, or Studio camera A |
| notes | string | – | Anything worth keeping with the asset, e.g. Model, warranty end, supplier |
| tag | string | – | The serial number or asset tag, e.g. SN-88-4412. Unique across the register: a second asset with the same tag is refused |
No output schema declared.
No examples provided.
asset_history Read one asset's log and total spend ~95
Read one asset in full by id, tag or name: every log entry in chronological order, the total spend as integer cents with a formatted amount, the last service date, and the next-due date the asset currently lives under. Reads only.
| Name | Type | Req | Description |
|---|---|---|---|
| asset | string | yes | The asset id, e.g. AST-2026-0003, its serial or asset tag, or its name when only one asset has it |
No output schema declared.
No examples provided.
asset_remove Remove an asset from the register ~121
Remove an asset entered by mistake or sold off. One that carries a maintenance log is refused unless confirm is true, naming what would be lost, because removing it loses the record of work done. The AST number is never reissued.
| Name | Type | Req | Description |
|---|---|---|---|
| asset | string | yes | The asset id, e.g. AST-2026-0003, its serial or asset tag, or its name when only one asset has it |
| confirm | boolean | – | Pass true to remove an asset that carries a maintenance log. The log goes with it; this cannot be undone |
No output schema declared.
No examples provided.
license_activate Activate license ~76
Turn Pro on for this connection with key, an MCPL1.<payload>.<signature> issued at checkout for this server or the bundle. Data under your token stays; a wrong or expired key changes nothing. license_status confirms it.
| Name | Type | Req | Description |
|---|---|---|---|
| key | string | yes | License key from checkout, MCPL1.<payload>.<signature> |
No output schema declared.
No examples provided.
license_status License status ~55
Report this endpoint's licence state for your token as JSON: the product, the tier free or pro, why it is not Pro, and the checkout URL. Call it to explain a free-tier refusal. No arguments, nothing changes.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
maintenance_due Report what is overdue and what is coming due ~89
The due report across every asset: what is overdue and by how many days, what falls due within the next N days (default 30), what is scheduled later, and what has no schedule at all. Computed from the stored next-due dates against today, at call time. Pro feature.
| Name | Type | Req | Description |
|---|---|---|---|
| within_days | integer | – | How far ahead to look, in days. Default 30 |
No output schema declared.
No examples provided.
maintenance_export Export the log as CSV or Markdown ~129
Export maintenance entries dated inside a range. CSV (free): one row per entry, ready for a spreadsheet. Markdown (Pro): one section per asset with its entries, total spend and next due date, ready to paste into notes or a report. Writes nothing.
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | – | csv (default) or markdown. Markdown summaries are a Pro feature |
| from | string | – | Only entries dated on or after this, YYYY-MM-DD. Default: no lower bound |
| to | string | – | Only entries dated on or before this, YYYY-MM-DD. Default: no upper bound |
No output schema declared.
No examples provided.
maintenance_log Log maintenance on an asset ~281
Log work done on an asset: the day, what was done, the cost in whole cents, who did it, and when the next service falls due -- as a date (next_due) or as an interval in days (interval_days), never both. A repair that sets no schedule takes neither. A future work date is refused.
| Name | Type | Req | Description |
|---|---|---|---|
| asset | string | yes | The asset id, e.g. AST-2026-0003, its serial or asset tag, or its name when only one asset has it |
| cost_cents | integer | – | What the work cost in whole cents. 12000 is 120.00. Default 0, for in-house work |
| date | string | yes | The day the work was done, YYYY-MM-DD. A future date is refused |
| interval_days | integer | – | Days after the work date the next service falls due, e.g. 90 for quarterly. Turned into a date once, at log time |
| next_due | string | – | The date the next service falls due, YYYY-MM-DD. Pass either this or interval_days, not both |
| technician | string | – | Who did the work, e.g. Anna, or Acme Heating Ltd |
| work | string | yes | What was done, e.g. Oil and filter change, or Annual boiler service |
No output schema declared.
No examples provided.
What is the io.github.theluckystrike/maintenance-log MCP server?
io.github.theluckystrike/maintenance-log is an MCP server listed in the public MCP registry as io.github.theluckystrike/maintenance-log. Equipment maintenance log: assets, service entries with costs, and a due report from stored dates. This page covers its hosted endpoint (https://mcp.zovo.one/mcp/maintenance-log).
Is the io.github.theluckystrike/maintenance-log MCP server safe to use?
io.github.theluckystrike/maintenance-log scores 79 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.theluckystrike/maintenance-log MCP server expose?
io.github.theluckystrike/maintenance-log exposes 8 tools: asset_add, maintenance_log, maintenance_due, asset_history, maintenance_export, and 3 more. Their descriptions and schemas cost roughly 1,052 tokens of context every time the server is loaded.
Does the io.github.theluckystrike/maintenance-log MCP server require authentication?
Yes. io.github.theluckystrike/maintenance-log asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the io.github.theluckystrike/maintenance-log MCP server still maintained?
io.github.theluckystrike/maintenance-log is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.