Maintenance Log MCP server

• asset_addFree

  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.

• asset_historyFree

  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.

• asset_removewrite actionFree

  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.

• license_activateFree

  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.

• license_statusFree

  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.

• maintenance_dueFree

  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.

• maintenance_exportFree

  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.

• maintenance_logFree

  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.

• –Code scanpackage could not be scannedn/a
• Live reliabilityremote reachable in 1008ms20/20
• Tool poisoning8 tool descriptions checked15/15
• Auth qualityAPI key sent as a header8/15
• Maintenancelast push 1 days ago15/15
• Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10

Grade history

• 2026-09-19restoreC → Ascore 88

Maintenance Log: common questions

Is Maintenance Log MCP server safe?

Yes, by our scan: it is graded A (88/100). Read the Maintenance Log safety report

How do I install Maintenance Log?

It runs remotely at mcp.zovo.one. Add it to Claude Code, Claude Desktop or Cursor with the snippets above, or call it through the mcp.market gateway without installing anything.

Does Maintenance Log need an API key?

Yes. The registry entry asks for MCP_LICENSE_KEY, Authorization.

Is Maintenance Log maintained?

The last commit was in the last day (2026-09-19). The latest release is v0.22.0.

Is Maintenance Log up?

100% of our last 3 checks got an answer. We check remote servers about four times a day.