Skip to content

McpStamp Leave Tracker MCP server

io.github.theluckystrike/leavetheluckystrikestreamable-httpv0.23.0Scanned

Employee leave and PTO: requests, approvals, balances, who is out, and conflict checks.

12 tools: 1 can delete or cancel things, 9 change things and 2 only read.

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

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here can delete or cancel things. Govern it.

  • 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 Leave Tracker MCP server can do

The McpStamp Leave Tracker MCP server is published by the GitHub account theluckystrike. It has 12 tools. It can delete or cancel things (1 tool: leave_cancel) and create or change data (9 tools: leave_employee_add, leave_request, leave_approve, leave_reject and 5 more). 2 tools only read.

1 tool brings in text other people can write (license_status).

The fixed checks matched 2 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.

12 tools

Deletes or cancels 1Claude Code: deny
  • leave_cancelCancel a pending or approved request by id, keeping its record with status cancelled.1 finding

    Why it is in this group

    • The name "leave_cancel" says "cancel": a word for removing or ending something.
    • The server marks it not destructive (destructiveHint: false), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "leave_cancel" not destructive (destructiveHint: false), and its own name, description or input give the class "destructive".

      Matched text

      annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":false}; The name "leave_cancel" says "cancel": a word for removing or ending something.

      What this check looks for
    Description, as the server wrote it
    Cancel a pending or approved request by id, keeping its record with status cancelled. Differs from leave_reject in intent (voluntary withdrawal). Nothing happened if already cancelled.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
Changes things 9Claude Code: ask
  • leave_approveApprove a pending leave request by id.No findings

    Why it is in this group

    • The name "leave_approve" says "approve": a word for a change.
    Description, as the server wrote it
    Approve a pending leave request by id. Also used to re-open a rejected one. Nothing to approve on an already-approved request.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • leave_balanceShow one employee's leave balance: allowance + carried-over, minus approved and pending, as whole days plus a possible half day.1 finding

    Why it is in this group

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

    Findings

    • Warn

      The server marks "leave_balance" 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 "show": a word for reading.

      What this check looks for
    Description, as the server wrote it
    Show one employee's leave balance: allowance + carried-over, minus approved and pending, as whole days plus a possible half day. Remaining is rounded down to whole days on the report.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • leave_employee_addAdd an employee to the leave tracker and return their EMP-NNNN id.No findings

    Why it is in this group

    • The name "leave_employee_add" says "add": a word for a change.
    Description, as the server wrote it
    Add an employee to the leave tracker and return their EMP-NNNN id. Give their annual paid-leave allowance in whole days and any days carried over from last year. Balances charge approved plus pending leave against allowance + carried-over. Free tier: unlimited.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • leave_export_icsPro.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.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Pro. Export all APPROVED leave as an .ics calendar (RFC5545). Returns the calendar text; pass path to also write it to a local file. watermark-free.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • leave_importPro.No findings

    Why it is in this group

    • The name "leave_import" says "import": a word for a change.
    Description, as the server wrote it
    Pro. Bulk-create leave requests from a CSV/TSV. First row is a header: employee,type,start,end,halfDay,status,reason. status may be omitted (defaults to pending) or be approved/rejected. Each request is still checked for overlap conflicts; a conflicting row is reported, not applied. watermark-free, full CRUD.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • leave_out_rangeWho is out in a date range: start and end are inclusive YYYY-MM-DD.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
    Who is out in a date range: start and end are inclusive YYYY-MM-DD. Each employee appears once per day; pending requests count as a plan. Use for coverage, calendars and absence summaries. Free tier: unlimited.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • leave_rejectReject or cancel a leave request by id.No findings

    Why it is in this group

    • The name "leave_reject" says "reject": a word for a change.
    Description, as the server wrote it
    Reject or cancel a leave request by id. A pending or approved request becomes rejected; a rejected one can be reopened via leave_approve. Use leave_cancel (via reject with reason) for voluntary withdrawal.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • leave_requestCreate a leave or PTO request and return its LV-NNNN id.No findings

    Why it is in this group

    • The name "leave_request" says "request": a word for a change.
    Description, as the server wrote it
    Create a leave or PTO request and return its LV-NNNN id. type is vacation, sick, unpaid or parental. start and end are inclusive YYYY-MM-DD dates; halfDay charges half a day for the whole span. A pending request is refussed if it would overlap another approved or pending request of the same employee. Free tier: unlimited requests.

    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
Only reads 2Show 2 read-only tools
  • leave_listList all employees, or all leave requests (optionally filtered by employee and/or status).No findings

    Why it is in this group

    • The name "leave_list" says "list": a word for reading.
    Description, as the server wrote it
    List all employees, or all leave requests (optionally filtered by employee and/or status). Omit the filter to list requests.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • 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 or outbound.

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 out0
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 6, 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
10
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/leave
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 10 tools that change things (1 destructive, 9 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://mcp.zovo.one/mcp/leave: tools/list returned 12 tools to an anonymous client, including leave_cancel (destructive), leave_employee_add (write), leave_request (write), leave_approve (write), leave_reject (write) and 5 more

    What this check looks for

Posture changes

  1. Nov 6, 2026
    • 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/leave

Findings

Matches of fixed checks, with the text they matched.

2 warn
  • The server marks "leave_balance" 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 "show": a word for reading.

    What this check looks for
  • The server marks "leave_cancel" not destructive (destructiveHint: false), and its own name, description or input give the class "destructive".

    Matched text

    annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":false}; The name "leave_cancel" says "cancel": a word for removing or ending something.

    What this check looks for

History

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

  1. PostureRemote posture changed. RFC 9728 protected resource metadata: https://mcp.zovo.one/.well-known/oauth-protected-resource -> https://mcp.zovo.one/.well-known/oauth-protected-resource/mcp/leave.View diff
    • 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/leave

Install

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

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

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__leave__leave_list",
      "mcp__leave__license_status"
    ],
    "ask": [
      "mcp__leave__leave_employee_add",
      "mcp__leave__leave_request",
      "mcp__leave__leave_approve",
      "mcp__leave__leave_reject",
      "mcp__leave__leave_balance",
      "mcp__leave__leave_out_range",
      "mcp__leave__leave_import",
      "mcp__leave__leave_export_ics",
      "mcp__leave__license_activate"
    ],
    "deny": [
      "mcp__leave__leave_cancel"
    ]
  }
}

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 leave. Review it before you use it.

Capability tags behind 1 rule
  • mcp__leave__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/leave/verify?hash=4513816b13fec87bc8d87a0aa2897bce2015182f7f31ea2b2d4f3520498b3d16" | jq -e '.changed == false'

Pinned hash 4513816b13fe, from Nov 15, 2026, 05:18 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/leave/changes.xml

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

Badge

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

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

McpStamp Leave Tracker MCP server: questions and answers

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

Is the McpStamp Leave Tracker MCP server safe?

No scan can promise that. What its definitions show: 12 tools, 10 of which can change, send or delete something, and 2 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 Leave Tracker MCP server delete data?

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

Can the McpStamp Leave Tracker MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the McpStamp Leave Tracker MCP server have?

12 tools: 1 destructive, 9 write, 2 read. leave_cancel, leave_employee_add, leave_request, leave_approve, leave_reject, leave_balance, leave_out_range, leave_import and 4 more.

Does the McpStamp Leave Tracker MCP server need sign-in or OAuth?

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

Does the McpStamp Leave Tracker MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the McpStamp Leave Tracker MCP server changed its tools?

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