Koskamo

theluckystrike McpStamp Maintenance Log MCP

Registers equipment assets and logs service entries including costs, technicians, and due dates. It provides overdue reports, chronological history with total spend, and exports data to CSV or Markdown summaries for maintenance tracking.

Endpoint and access

No sign-in to connect and list tools. Individual tools may still need a vendor account, credentials, or permissions; check the documented prerequisites.

theluckystrike McpStamp Maintenance Log MCP logo, by theluckystrikeCommunity listingStreamable HTTPNo sign-inEndpoint checked 2026-11-07Published by theluckystrike
MCP endpoint (Streamable HTTP)
https://mcp.zovo.one/mcp/maintenance-log
Vendor documentation

What its tools do

8 tools, grouped by the hints the server advertises. Hints are self-declared, not verified behavior.

8 of 8 have a description · 8 of 8 declare behavior hints · 7 of 7 with parameters document them all

Checks and signals

Each line is separate evidence, not a trust score.

  • Passed Endpoint answered the live check ·
  • Availability 1 of 1 checks passed in 30 days

What you can do with it

  • Register equipment with asset tags and location
  • Log service entries with cost and technician
  • Check for overdue or upcoming maintenance
  • Export maintenance history to CSV

Source and maintenance

Community listingRegistry 0.23.0
Maintenance checked

Protocol and capabilities

Server
mcp-maintenance-log 0.22.6
MCP protocol negotiated in check
2025-11-25
Tools
8 advertised
Resources
1 advertised
Resource templates
0 advertised
Prompts
1 advertised
Server-advertised capabilities
{
  "tools": {
    "listChanged": true
  },
  "prompts": {
    "listChanged": true
  },
  "resources": {
    "listChanged": true
  }
}

Server-provided instructions

Untrusted server output shown for inspection. It is not Koskamo guidance and is excluded from knowledge search.

Equipment maintenance records. It covers a register of equipment with serial or asset tag and location, work done with date, cost, who did it and when the next service is due, each asset's full history and total spend, what is overdue or coming due, and exports as CSV or Markdown. Costs are integer cents. Records are stored per user account on McpStamp's hosted service. The free tier holds 3 assets with unmetered logging; the due-date view and Markdown export need Pro. One lifetime key unlocks this server and all 58 others: https://mcp.zovo.one/buy/bundle?src=instr.maintenance-log

Tools

8 advertised

asset_add — Add an asset to the register
Advertised by the server during the last successful anonymous check.

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_add input schema
{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "name"
  ],
  "properties": {
    "tag": {
      "type": "string",
      "maxLength": 200,
      "description": "The serial number or asset tag, e.g. SN-88-4412. Unique across the register: a second asset with the same tag is refused"
    },
    "name": {
      "type": "string",
      "maxLength": 200,
      "description": "What the asset is called, e.g. Lathe, Combi boiler, Van 2, or Studio camera A"
    },
    "notes": {
      "type": "string",
      "maxLength": 2000,
      "description": "Anything worth keeping with the asset, e.g. Model, warranty end, supplier"
    },
    "currency": {
      "type": "string",
      "pattern": "^[A-Za-z]{3}$",
      "description": "ISO code the costs are in. Default USD"
    },
    "location": {
      "type": "string",
      "maxLength": 400,
      "description": "Where the asset lives, e.g. Workshop bay 2, or 14 Nowa Street, flat 3"
    }
  },
  "additionalProperties": false
}
asset_add annotations
{
  "readOnlyHint": false,
  "openWorldHint": false,
  "idempotentHint": false,
  "destructiveHint": false
}
maintenance_log — Log maintenance on an asset
Advertised by the server during the last successful anonymous check.

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.

maintenance_log input schema
{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "asset",
    "date",
    "work"
  ],
  "properties": {
    "date": {
      "type": "string",
      "maxLength": 10,
      "description": "The day the work was done, YYYY-MM-DD. A future date is refused"
    },
    "work": {
      "type": "string",
      "maxLength": 2000,
      "description": "What was done, e.g. Oil and filter change, or Annual boiler service"
    },
    "asset": {
      "type": "string",
      "maxLength": 200,
      "description": "The asset id, e.g. AST-2026-0003, its serial or asset tag, or its name when only one asset has it"
    },
    "next_due": {
      "type": "string",
      "maxLength": 10,
      "description": "The date the next service falls due, YYYY-MM-DD. Pass either this or interval_days, not both"
    },
    "cost_cents": {
      "type": "integer",
      "maximum": 100000000000000,
      "minimum": 0,
      "description": "What the work cost in whole cents. 12000 is 120.00. Default 0, for in-house work"
    },
    "technician": {
      "type": "string",
      "maxLength": 200,
      "description": "Who did the work, e.g. Anna, or Acme Heating Ltd"
    },
    "interval_days": {
      "type": "integer",
      "maximum": 36500,
      "minimum": 1,
      "description": "Days after the work date the next service falls due, e.g. 90 for quarterly. Turned into a date once, at log time"
    }
  },
  "additionalProperties": false
}
maintenance_log annotations
{
  "readOnlyHint": false,
  "openWorldHint": false,
  "idempotentHint": false,
  "destructiveHint": false
}
maintenance_due — Report what is overdue and what is coming due
Advertised by the server during the last successful anonymous check.

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_due input schema
{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "within_days": {
      "type": "integer",
      "maximum": 3650,
      "minimum": 0,
      "description": "How far ahead to look, in days. Default 30"
    }
  },
  "additionalProperties": false
}
maintenance_due annotations
{
  "readOnlyHint": false,
  "openWorldHint": false,
  "idempotentHint": false,
  "destructiveHint": false
}
asset_history — Read one asset's log and total spend
Advertised by the server during the last successful anonymous check.

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_history input schema
{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "asset"
  ],
  "properties": {
    "asset": {
      "type": "string",
      "maxLength": 200,
      "description": "The asset id, e.g. AST-2026-0003, its serial or asset tag, or its name when only one asset has it"
    }
  },
  "additionalProperties": false
}
asset_history annotations
{
  "readOnlyHint": false,
  "openWorldHint": false,
  "idempotentHint": false,
  "destructiveHint": false
}
maintenance_export — Export the log as CSV or Markdown
Advertised by the server during the last successful anonymous check.
Advertised read-only

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_export input schema
{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "to": {
      "type": "string",
      "maxLength": 10,
      "description": "Only entries dated on or before this, YYYY-MM-DD. Default: no upper bound"
    },
    "from": {
      "type": "string",
      "maxLength": 10,
      "description": "Only entries dated on or after this, YYYY-MM-DD. Default: no lower bound"
    },
    "format": {
      "enum": [
        "csv",
        "markdown"
      ],
      "type": "string",
      "description": "csv (default) or markdown. Markdown summaries are a Pro feature"
    }
  },
  "additionalProperties": false
}
maintenance_export annotations
{
  "readOnlyHint": true,
  "openWorldHint": false,
  "idempotentHint": true,
  "destructiveHint": false
}
asset_remove — Remove an asset from the register
Advertised by the server during the last successful anonymous check.
Advertised destructive

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.

asset_remove input schema
{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "asset"
  ],
  "properties": {
    "asset": {
      "type": "string",
      "maxLength": 200,
      "description": "The asset id, e.g. AST-2026-0003, its serial or asset tag, or its name when only one asset has it"
    },
    "confirm": {
      "type": "boolean",
      "description": "Pass true to remove an asset that carries a maintenance log. The log goes with it; this cannot be undone"
    }
  },
  "additionalProperties": false
}
asset_remove annotations
{
  "readOnlyHint": false,
  "openWorldHint": false,
  "idempotentHint": false,
  "destructiveHint": true
}
license_status — License status
Advertised by the server during the last successful anonymous check.
Advertised read-only

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_status input schema
{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {}
}
license_status annotations
{
  "readOnlyHint": true,
  "openWorldHint": false,
  "idempotentHint": true,
  "destructiveHint": false
}
license_activate — Activate license
Advertised by the server during the last successful anonymous check.

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_activate input schema
{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "key"
  ],
  "properties": {
    "key": {
      "type": "string",
      "description": "License key from checkout, MCPL1.<payload>.<signature>"
    }
  },
  "additionalProperties": false
}
license_activate annotations
{
  "readOnlyHint": false,
  "openWorldHint": false,
  "idempotentHint": false,
  "destructiveHint": false
}

Prompts

1 advertised

upgrade_to_pro — Explain the upgrade

Advertised by the server during the last successful anonymous check.

Explain what Pro on the maintenance-log server costs and exactly what the user has to do, without leaving the conversation.

feature
The capped feature that prompted this, if there was one

Resources

1 advertised

pricing — Pricing and upgrade

Advertised by the server during the last successful anonymous check.

What maintenance-log costs, what Pro unlocks, the checkout link that carries this connection's token, and the one step a person has to take. Machine-readable; read it before telling a user how to lift a free-tier cap.

pricing URI
pricing://maintenance-log

MIME type: application/json

90-day uptime

A lightweight connection check about every six hours, sampled on hosts with many listings. It shows the server answered, not that its tools work.

Too few checks for a percentage yet (1 of 1 answered).

  1. 2026-11-07: 1 of 1 checks answered

30-day availability

Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.

Successful checks
1 of 1 (100%)
Average latency
661 ms
95th percentile latency
661 ms

Maintenance history

Public check and source-refresh events. Editorial and ownership records remain private.

  • · probe · passed · 661 ms · metadata changed · 8 tool(s), 1 resource(s), 0 resource template(s), 1 prompt(s)

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers the remote server. Use --scope project to write .mcp.json for the repo.
Claude Code configuration
claude mcp add --transport http mcpstamp-maintenance-log-mcp https://mcp.zovo.one/mcp/maintenance-log

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).
Codex configuration
codex mcp add mcpstamp-maintenance-log-mcp --url https://mcp.zovo.one/mcp/maintenance-log

Cursor

Merge this server into .cursor/mcp.json in your project, then enable mcpstamp-maintenance-log-mcp in your MCP settings.
Cursor configuration
{
  "mcpServers": {
    "mcpstamp-maintenance-log-mcp": {
      "url": "https://mcp.zovo.one/mcp/maintenance-log"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).
Cline configuration
{
  "mcpServers": {
    "mcpstamp-maintenance-log-mcp": {
      "type": "streamableHttp",
      "url": "https://mcp.zovo.one/mcp/maintenance-log",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start mcpstamp-maintenance-log-mcp and inspect its tools.
VS Code configuration
{
  "servers": {
    "mcpstamp-maintenance-log-mcp": {
      "type": "http",
      "url": "https://mcp.zovo.one/mcp/maintenance-log"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.
Gemini CLI configuration
gemini mcp add --transport http mcpstamp-maintenance-log-mcp https://mcp.zovo.one/mcp/maintenance-log

Claude Desktop

Open Claude Settings > Connectors > Add custom connector, enter this server URL and enable it for the conversation. This is a manual remote-connector handoff, not a desktop JSON configuration.
Claude Desktop configuration
https://mcp.zovo.one/mcp/maintenance-log

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.
Windsurf configuration
{
  "mcpServers": {
    "mcpstamp-maintenance-log-mcp": {
      "serverUrl": "https://mcp.zovo.one/mcp/maintenance-log"
    }
  }
}

Let your agent find its tools

Find servers like theluckystrike McpStamp Maintenance Log MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.