McpStamp Maintenance Log
MCPB · MAINTENANCE-LOG.MCPB · 2 COMPONENTS
Equipment maintenance log: service entries with cost, full history, and what is due or overdue.
Available components
Last scanned (3 hours ago)
Scores higher than 94% of MCPB servers
Category IoT and Hardware
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security23
- No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
- Known CVEs were checked across the 92 of 92 dependencies we could resolve, so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- 30 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 48 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability77
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1046 tokens (~130/item across 8 items; 8 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 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. See how to fix → Fail
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 +1
- Maintenance: unverified → pass ▲ functional
- 3 Nov 26 0
- Provenance: unverified → fail ▼ security
- 2 Nov 26 +54
- Known CVEs: unverified → partial ▲ security
- Stability: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- Install scripts: unverified → pass ▲ security
- Dependency health: unverified → 0.85 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- License: unverified → pass ▲ functional
- Licence: MIT functional
- 30 Oct 26 0
- Package version: 0.22.0 → 0.22.5 functional
- 29 Oct 26 0
- Package version: 0.22.0 → 0.22.5 functional
- 26 Oct 26 0
- Package version: 0.22.0 → 0.22.5 functional
- 24 Oct 26 0
- Package version: 0.22.0 → 0.22.5 functional
- 22 Oct 26 0
- Package version: 0.22.0 → 0.22.5 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed mcpb/https://github.com/theluckystrike/mcp-servers/releases/download/v0.22.0/maintenance-log.mcpb@0.22.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | mcpb |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
Dependencies 92 packages
| Packages resolved | 92 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
asset_add Add an asset to the register ~206
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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 |
No output schema declared.
No examples provided.
asset_history Read one asset's log and total spend ~95
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.
| Name | Type | Req | Description |
|---|---|---|---|
| asset | string | yes | The asset id, e.g. AST-2026-0003, its serial or asset tag, or its name when only one asset has it |
No output schema declared.
No examples provided.
asset_remove Remove an asset from the register ~121
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.
| Name | Type | Req | Description |
|---|---|---|---|
| asset | string | yes | 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 |
No output schema declared.
No examples provided.
license_activate Activate license ~71
Activate a Pro key (MCPL1.xxx.yyy) from checkout: verified offline against a built-in public key, saved to your config file. A wrong, malformed or expired key is refused, unsaved. license_status reads it back.
| Name | Type | Req | Description |
|---|---|---|---|
| key | string | yes | License key from the checkout confirmation page |
No output schema declared.
No examples provided.
license_status License status ~54
Report this server's licence state: product, tier free or pro, licence id, expiry, the key source and the upgrade URL. No arguments, no network. Explains a free-tier refusal; license_activate installs a key.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
maintenance_due Report what is overdue and what is coming due ~89
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.
| Name | Type | Req | Description |
|---|---|---|---|
| within_days | integer | – | How far ahead to look, in days. Default 30 |
No output schema declared.
No examples provided.
maintenance_export Export the log as CSV or Markdown ~129
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
No output schema declared.
No examples provided.
maintenance_log Log maintenance on an asset ~281
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.
| Name | Type | Req | Description |
|---|---|---|---|
| asset | string | yes | 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 | yes | 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 | yes | What was done, e.g. Oil and filter change, or Annual boiler service |
No output schema declared.
No examples provided.
How do I install the McpStamp Maintenance Log MCP server?
McpStamp Maintenance Log ships as an MCPB bundle, a single file you download and open in an MCP host that supports MCPB bundles, such as Claude Desktop. The host reads the launch command from the bundle's own manifest, so there is no command to copy. Before opening it, check the file's SHA-256 matches the one the MCP registry declares for it, 6e4e8ab0924939be97c7f50e9f26807184a8201517c99242fc1cce33920a40eb; the commands to do that are on this page. If it does not match, do not open it.
mcpb · maintenance-log.mcpb
Download bundleCheck the download matches the SHA-256 the MCP registry declares before you open it. If it does not match, do not open the file.
SHA-256
6e4e8ab0924939be97c7f50e9f26807184a8201517c99242fc1cce33920a40eb
macOS / Linux
echo "6e4e8ab0924939be97c7f50e9f26807184a8201517c99242fc1cce33920a40eb maintenance-log.mcpb" | shasum -a 256 -c
Windows (PowerShell)
(Get-FileHash -Algorithm SHA256 .\maintenance-log.mcpb).Hash -eq "6e4e8ab0924939be97c7f50e9f26807184a8201517c99242fc1cce33920a40eb"
Run it in the folder you saved the bundle to, then open the file with an MCPB-capable host such as Claude Desktop.
What is the McpStamp Maintenance Log MCP server?
McpStamp Maintenance Log is an MCP server listed in the public MCP registry as io.github.theluckystrike/maintenance-log. Equipment maintenance log: service entries with cost, full history, and what is due or overdue. This page covers its MCPB bundle (https://github.com/theluckystrike/mcp-servers/releases/download/v0.22.0/maintenance-log.mcpb).
Is the McpStamp Maintenance Log MCP server safe to use?
McpStamp Maintenance Log scores 60 out of 100 on VerifyMCP. It declares no install or post-install scripts. 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 McpStamp Maintenance Log MCP server expose?
McpStamp 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,046 tokens of context every time the server is loaded.
What licence is the McpStamp Maintenance Log MCP server under?
McpStamp Maintenance Log declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.