Maintenance Schedule MCP Server

by theluckystrike Your server? Claim it

answering

Maintenance Schedule is answering right now. Last checked 13 min ago. It exposes 8 tools. Last commit 8 Oct 2026.

An equipment maintenance schedule and log: service entries, costs, and what is due or overdue.

Uptime history 19 days of history · worst day 94%

19 days agonow

100.0%

Uptime 24h

91 of 91 checks

Tools

read from the server

135 ms

Response time

average over 24h

Stars

last commit 8 Oct 2026

Nothing serious here today

Today is the operative word: we check Maintenance Schedule every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 13 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add maintenance-schedule --transport http https://mcp.zovo.one/mcp/maintenance-schedule

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "maintenance-schedule": {
      "url": "https://mcp.zovo.one/mcp/maintenance-schedule"
    }
  }
}

~/.codex/config.toml

[mcp_servers.maintenance-schedule]
url = "https://mcp.zovo.one/mcp/maintenance-schedule"

.cursor/mcp.json

{
  "mcpServers": {
    "maintenance-schedule": {
      "url": "https://mcp.zovo.one/mcp/maintenance-schedule"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "maintenance-schedule": {
      "url": "https://mcp.zovo.one/mcp/maintenance-schedule"
    }
  }
}

Available tools 8

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

asset

asset_add

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_history

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_remove

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.

maintenance

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

maintenance_export

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_log

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.

license

license_activate

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

Endpoints

URL	Transport	State	Latency	Checked
https://mcp.zovo.one/mcp/maintenance-schedule	streamable-http	answering	45 ms	13 min ago

Alternatives to Maintenance Schedule

same job, measured the same way

Maintenance Log

by theluckystrike

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

8 tools answering

Maintenance

by rowb-septic-log

Septic maintenance record: log inspections and pump-outs; next due date under EPA intervals. No AI.

6 tools answering

Jira Alerts (JSM Operations)

by rrvrs

MCP server for Jira Service Management Operations — alerts, on-call schedules and responders

56 installs/wk local only

Status.io MCP by usefulapi

by usefulapi

Read Status.io components, incidents, maintenance; post incidents, schedule maintenance, set status.

20 tools answering

Dobby

by gil-dobby

Connect, monitor, and control AI agents — tasks, approvals, schedules, and governance.

38 installs/wk answering

Sparkforensics MCP

by shuffle-works

MCP server for diagnosing Apache Spark event-log performance issues and comparing runs.

506 installs/wk local only

three.ws Provenance

by nirholas

Append-only, signed, on-chain-verifiable agent action log — record and audit what agents did.

44 installs/wk local only

ControlDrill

by controldrill

List, schedule, and retrieve evidence for ControlDrill incident-response tabletop exercises.

answering

Maintenance Schedule — questions

Answers built from our own checks of this server.

What can Maintenance Schedule do?

It exposes 8 tools, read directly from the server on our last check. Among them: asset_add, asset_history, asset_remove, license_activate, license_status, maintenance_due and 2 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

What is Maintenance Schedule mostly used for?

Its tools cluster around maintenance, asset and license. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.

Is Maintenance Schedule working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 135 ms. The bar chart above shows every period we have measured.

How do I connect Maintenance Schedule?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Maintenance Schedule need an API key?

No. Maintenance Schedule completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 8 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Maintenance Schedule?

It answers our handshake in 135 ms on average, which is faster than 75% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.

Is Maintenance Schedule open source?

Yes — it is published under the MIT licence, written in JavaScript and 1 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.