Skip to main content
Glama

Server Details

Equipment maintenance log: service entries with cost, full history, and what is due or overdue.

If you are the author of this connector, you can claim ownership. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Uptime
100.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
Repository
theluckystrike/mcp-servers
GitHub Stars
0
ChatGPT
–
Claude
–

TDQS

A4.1/5.0

Scored across 8 tools

Disambiguation5/5

Each tool targets a distinct resource-action pair, and the three prefix families (asset_, license_, maintenance_) cleanly partition the surface. The read-only tools are still clearly separated: asset_history reads one asset's full record, maintenance_due computes schedules across all assets, and maintenance_export dumps entries for a date range in CSV/Markdown. No two tools could be reasonably swapped for one another.

Naming Consistency5/5

Every name follows the same snake_case <domain>_<verb/noun> pattern with a stable prefix set: asset_add/asset_history/asset_remove, license_activate/license_status, maintenance_log/maintenance_due/maintenance_export. Verb choice is consistent (add/remove/history, activate/status, log/due/export) with no mixed casing or stray conventions.

Tool Count5/5

Eight tools is well within the sweet spot and each earns its place: three asset lifecycle tools, three log/reporting tools, and two licensing tools. Nothing looks like a redundant wrapper or an orphan.

Completeness3/5

Core workflows are covered (add/read/remove assets, log work, due report, export, licensing), but there is no update path for either assets or log entries — a mistyped serial, wrong currency, or bad cost/date can only be fixed by deleting, and a logged entry cannot be corrected or removed at all. That is a notable gap in an otherwise solid lifecycle surface.

Available Tools

8 tools
asset_addAdd an asset to the registerAInspect

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.

Inputs: name (required), tag, notes, currency, +1 more.

asset_historyRead one asset's log and total spendBInspect

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.

Inputs: asset (required).

asset_removeRemove an asset from the registerA
Destructive
Inspect

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.

Inputs: asset (required), confirm.

license_activateActivate licenseAInspect

Turn Pro on for this connection with key, an MCPL1.. 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.

Inputs: key (required).

license_statusLicense statusA
Read-onlyIdempotent
Inspect

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.

Inputs: no named parameters.

maintenance_dueReport what is overdue and what is coming dueBInspect

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.

Inputs: within_days.

maintenance_exportExport the log as CSV or MarkdownA
Read-onlyIdempotent
Inspect

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.

Inputs: to, from, format.

maintenance_logLog maintenance on an assetAInspect

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.

Inputs: date (required), work (required), asset (required), next_due, +3 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP-compatible host agents to browse an immutable equipment catalog, check tool availability, and generate standardized maintenance request prompts.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables voice-first household maintenance tracking, turning spoken updates into durable records, service history, and due-date reminders for a concise maintenance brief.
      MIT
    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.