# io.github.theluckystrike/maintenance-log (remote · mcp.zovo.one)

Equipment maintenance log: assets, service entries with costs, and a due report from stored dates.

- Trust score: 79/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `mcp.zovo.one`: 79/100 (this document), [markdown](https://verifymcp.io/servers/theluckystrike-maintenance-log/mcp-maintenance-log.md), [page](https://verifymcp.io/servers/theluckystrike-maintenance-log/mcp-maintenance-log)
- mcpb · `maintenance-log.mcpb`: 46/100, [markdown](https://verifymcp.io/servers/theluckystrike-maintenance-log/https-github-com-theluckystrike-mcp-servers-releases-download-v0-22-0-maintenanc.md), [page](https://verifymcp.io/servers/theluckystrike-maintenance-log/https-github-com-theluckystrike-mcp-servers-releases-download-v0-22-0-maintenanc)

## Channel facts

- Endpoint: `https://mcp.zovo.one/mcp/maintenance-log`
- Transports: `streamable-http`
- Auth: `required`
- Version: `0.22.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Endpoint Security**: 89/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 86/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 10/100
  - Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 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.
  - An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http theluckystrike-maintenance-log 'https://mcp.zovo.one/mcp/maintenance-log'
```

### Cursor

```json
{
  "mcpServers": {
    "theluckystrike-maintenance-log": {
      "url": "https://mcp.zovo.one/mcp/maintenance-log"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "theluckystrike-maintenance-log": {
      "type": "http",
      "url": "https://mcp.zovo.one/mcp/maintenance-log"
    }
  }
}
```

### Codex

```toml
[mcp_servers.theluckystrike-maintenance-log]
url = "https://mcp.zovo.one/mcp/maintenance-log"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "theluckystrike-maintenance-log": {
      "type": "remote",
      "url": "https://mcp.zovo.one/mcp/maintenance-log",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add theluckystrike-maintenance-log --url 'https://mcp.zovo.one/mcp/maintenance-log' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  theluckystrike-maintenance-log:
    url: "https://mcp.zovo.one/mcp/maintenance-log"
```

### Netclaw

```json
{
  "McpServers": {
    "theluckystrike-maintenance-log": {
      "Transport": "http",
      "Url": "https://mcp.zovo.one/mcp/maintenance-log"
    }
  }
}
```

### Vellum

```bash
assistant mcp add theluckystrike-maintenance-log -t streamable-http -u 'https://mcp.zovo.one/mcp/maintenance-log'
```

### Other

```json
{
  "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.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-19 (score 79, +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.

### 2026-09-18 (score 78, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-09-17 (score 78)

First indexed and scored.

## MCP tools (8)

### `asset_add` (~206 tokens)

Add an asset to the register

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.

Input parameters:

- `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, required): 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

### `maintenance_log` (~281 tokens)

Log maintenance on an asset

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.

Input parameters:

- `asset` (string, required): 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, required): 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, required): What was done, e.g. Oil and filter change, or Annual boiler service

### `maintenance_due` (~89 tokens)

Report what is overdue and what is coming due

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.

Input parameters:

- `within_days` (integer): How far ahead to look, in days. Default 30

### `asset_history` (~95 tokens)

Read one asset's log and total spend

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.

Input parameters:

- `asset` (string, required): The asset id, e.g. AST-2026-0003, its serial or asset tag, or its name when only one asset has it

### `maintenance_export` (~129 tokens)

Export the log as CSV or Markdown

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.

Input parameters:

- `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

### `asset_remove` (~121 tokens)

Remove an asset from the register

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.

Input parameters:

- `asset` (string, required): 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

### `license_status` (~55 tokens)

License status

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.

### `license_activate` (~76 tokens)

Activate license

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.

Input parameters:

- `key` (string, required): License key from checkout, MCPL1.<payload>.<signature>

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/theluckystrike-maintenance-log/mcp-maintenance-log#diagnostics

## Score history

- 2026-09-20: 79
- 2026-09-19: 79
- 2026-09-18: 78
- 2026-09-17: 78

## Common questions

### 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.

## Links

- Remote endpoint: https://mcp.zovo.one/mcp/maintenance-log
- Authorisation metadata: https://mcp.zovo.one/.well-known/oauth-protected-resource/mcp/maintenance-log
- Repository: https://github.com/theluckystrike/mcp-servers
- Website: https://mcp.zovo.one/s/maintenance-log
- Changelog RSS feed: https://verifymcp.io/servers/theluckystrike-maintenance-log/mcp-maintenance-log.xml
- Changelog JSON feed: https://verifymcp.io/servers/theluckystrike-maintenance-log/mcp-maintenance-log.json
- HTML version of this page: https://verifymcp.io/servers/theluckystrike-maintenance-log/mcp-maintenance-log