Skip to content

McpStamp Maintenance Log MCP server

io.github.theluckystrike/maintenance-logtheluckystrikestreamable-httpv0.23.0Scanned

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

8 tools: 1 can delete or cancel things, 1 do something that can't be undone, 5 change things and 1 only read.

Tools: 1 delete, 1 irreversible, 5 write, 1 read.
  • Reads private data · 0
  • Reads text others write · 1
  • Can send data out · 1
  • 3 findings

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here can delete or cancel things and 1 does something that can't be undone. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the McpStamp Maintenance Log MCP server can do

The McpStamp Maintenance Log MCP server is published by the GitHub account theluckystrike. It has 8 tools. It can delete or cancel things (1 tool: asset_remove), do things that cannot be undone, such as sending, paying or publishing (maintenance_export) and create or change data (5 tools: asset_add, maintenance_log, maintenance_due, asset_history and 1 more). 1 tool only reads.

1 tool brings in text other people can write (license_status); 1 tool can send data out of your system (maintenance_export).

The fixed checks matched 3 findings (annotation-conflict). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 15, 2026, version 0.23.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

8 tools

Deletes or cancels 1Claude Code: deny
  • asset_removeRemove an asset entered by mistake or sold off.No findings

    Why it is in this group

    • The name "asset_remove" says "remove": a word for removing or ending something.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: false
    • openWorldHint: false
Can't be undone 1Claude Code: ask
  • maintenance_exportExport maintenance entries dated inside a range.Can send data out1 finding

    Why it is in this group

    • The input addresses people (input.to): what it sends cannot be taken back.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • outboundThe input takes a destination (input.to): what the tool writes goes there.

    Findings

    • Warn

      The server marks "maintenance_export" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The input addresses people (input.to): what it sends cannot be taken back.

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
Changes things 5Claude Code: ask
  • asset_addAdd 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.No findings

    Why it is in this group

    • The name "asset_add" says "add": a word for a change.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • asset_historyRead 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…1 finding

    Why it is in this group

    • The description's first verb is "read": a word for reading.
    • The server marks it as not read-only (readOnlyHint: false).

    Findings

    • Warn

      The server marks "asset_history" as not read-only (readOnlyHint: false), and its words say it reads.

      Matched text

      annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":false}; The description's first verb is "read": a word for reading.

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • license_activateTurn Pro on for this connection with key, an MCPL1.<payload>.<signature> issued at checkout for this server or the bundle.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • maintenance_dueThe 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 al…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • maintenance_logLog 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 (inter…1 finding

    Why it is in this group

    • The name "maintenance_log" says "log": a word for reading.
    • The server marks it as not read-only (readOnlyHint: false).

    Findings

    • Warn

      The server marks "maintenance_log" as not read-only (readOnlyHint: false), and its words say it reads.

      Matched text

      annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":false}; The name "maintenance_log" says "log": a word for reading.

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
Only reads 1Show 1 read-only tool
  • license_statusReport 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.Reads text others writeNo findings

    Why it is in this group

    • The name "license_status" says "status": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "url": it reads web pages, which anyone can write.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write1
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out1
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:33 UTC, unchanged since Nov 13, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
7
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://mcp.zovo.one/.well-known/oauth-protected-resource/mcp/maintenance-log
Authorization servers
https://mcp.zovo.one
Legacy HTTP+SSE transport
no
Dynamic client registration
yes
Client ID metadata documents
no
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 7 tools that change things (1 destructive, 1 irreversible, 5 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://mcp.zovo.one/mcp/maintenance-log: tools/list returned 8 tools to an anonymous client, including asset_remove (destructive), maintenance_export (irreversible), asset_add (write), maintenance_log (write), maintenance_due (write) and 2 more

    What this check looks for

Posture changes

  1. Nov 13, 2026
    • tools/list served without credentials: no to yes
    • Tools that change things, listed without credentials: 0 to 7
    • Protocol version: none to 2025-06-18
  2. Nov 6, 2026
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 7 to 0
    • Protocol version: 2025-06-18 to none
    • RFC 9728 protected resource metadata: https://mcp.zovo.one/.well-known/oauth-protected-resource to https://mcp.zovo.one/.well-known/oauth-protected-resource/mcp/maintenance-log

Findings

Matches of fixed checks, with the text they matched.

3 warn
  • The server marks "maintenance_log" as not read-only (readOnlyHint: false), and its words say it reads.

    Matched text

    annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":false}; The name "maintenance_log" says "log": a word for reading.

    What this check looks for
  • The server marks "asset_history" as not read-only (readOnlyHint: false), and its words say it reads.

    Matched text

    annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":false}; The description's first verb is "read": a word for reading.

    What this check looks for
  • The server marks "maintenance_export" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The input addresses people (input.to): what it sends cannot be taken back.

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. tools/list served without credentials: no -> yes; Tools that change things, listed without credentials: 0 -> 7; Protocol version: none -> 2025-06-18.View diff
    • tools/list served without credentials: no to yes
    • Tools that change things, listed without credentials: 0 to 7
    • Protocol version: none to 2025-06-18
  2. PostureRemote posture changed. tools/list served without credentials: yes -> no; Tools that change things, listed without credentials: 7 -> 0; Protocol version: 2025-06-18 -> none (and 1 more).View diff
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 7 to 0
    • Protocol version: 2025-06-18 to none
    • RFC 9728 protected resource metadata: https://mcp.zovo.one/.well-known/oauth-protected-resource to https://mcp.zovo.one/.well-known/oauth-protected-resource/mcp/maintenance-log

Install

Pinned to version 0.23.0. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__maintenance-log__license_status"
    ],
    "ask": [
      "mcp__maintenance-log__asset_add",
      "mcp__maintenance-log__maintenance_log",
      "mcp__maintenance-log__maintenance_due",
      "mcp__maintenance-log__asset_history",
      "mcp__maintenance-log__maintenance_export",
      "mcp__maintenance-log__license_activate"
    ],
    "deny": [
      "mcp__maintenance-log__asset_remove"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as maintenance-log. Review it before you use it.

Capability tags behind 2 rules
  • mcp__maintenance-log__maintenance_export outbound
  • mcp__maintenance-log__license_status untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.theluckystrike/maintenance-log/verify?hash=834231f956b1795c6848739b9c01f9d456b5b6ede40b7c189c7d843634776eac" | jq -e '.changed == false'

Pinned hash 834231f956b1, from Nov 15, 2026, 06:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.theluckystrike/maintenance-log/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.theluckystrike/maintenance-log
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.theluckystrike/maintenance-log.svg)](https://radar.anlyon.com/servers/io.github.theluckystrike/maintenance-log)

Source: MCP Registry · repository. Synced Nov 2, 2026, 03:18 UTC.

McpStamp Maintenance Log MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the McpStamp Maintenance Log MCP server safe?

No scan can promise that. What its definitions show: 8 tools, 7 of which can change, send or delete something, and 3 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the McpStamp Maintenance Log MCP server delete data?

Yes. 1 tool can delete, cancel or revoke something: asset_remove.

Can the McpStamp Maintenance Log MCP server do things that cannot be undone?

Yes. 1 tool can send, pay, publish or merge: maintenance_export.

What tools does the McpStamp Maintenance Log MCP server have?

8 tools: 1 destructive, 1 irreversible, 5 write, 1 read. asset_remove, maintenance_export, asset_add, maintenance_log, maintenance_due, asset_history, license_activate and license_status.

Does the McpStamp Maintenance Log MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the McpStamp Maintenance Log MCP server send data to outside services?

1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): maintenance_export.

Has the McpStamp Maintenance Log MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 15, 2026.