Skip to content

McpStamp Deposits MCP server

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

Track client security and retainer deposits: hold, apply to an invoice, refund, statements.

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

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

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 Deposits MCP server can do

The McpStamp Deposits MCP server is published by the GitHub account theluckystrike. It has 11 tools. It can delete or cancel things (1 tool: deposit_delete), do things that cannot be undone, such as sending, paying or publishing (deposit_refund) and create or change data (7 tools: deposit_record, deposit_apply, deposit_balance, deposit_statement_text and 3 more). 2 tools only read.

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

The fixed checks matched 1 finding (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.

11 tools

Deletes or cancels 1Claude Code: deny
  • deposit_deleteDelete a deposit that never moved money, freeing that month's free-tier slot.No findings

    Why it is in this group

    • The name "deposit_delete" says "delete": a word for removing or ending something.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Delete a deposit that never moved money, freeing that month's free-tier slot. One with anything applied or refunded is refused, naming it, since a payment or refund would be left with nothing behind it.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: false
    • openWorldHint: false
Can't be undone 1Claude Code: ask
  • deposit_refundGive part or all of a held deposit back to the client, with the date and how it was sent.No findings

    Why it is in this group

    • The name "deposit_refund" says "refund": a word that usually means money moves, which cannot be taken back.
    Description, as the server wrote it
    Give part or all of a held deposit back to the client, with the date and how it was sent. Refuses more than is still held. The invoice server is not touched: a refund is not a payment.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
Changes things 7Claude Code: ask
  • deposit_applyApply part of a held deposit to one invoice: it records that amount as a PAYMENT through the invoice server.No findings

    Why it is in this group

    • The name "deposit_apply" says "apply": a word for a change.
    Description, as the server wrote it
    Apply part of a held deposit to one invoice: it records that amount as a PAYMENT through the invoice server. amount_minor defaults to the lesser of held and owed. More than either, or a pre-arrival date, is refused.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • deposit_balanceAnswer "how much of theirs am I holding?" for one client or everyone: received, applied to invoices, refunded and still held, one row per currency, never added across them.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
    Answer "how much of theirs am I holding?" for one client or everyone: received, applied to invoices, refunded and still held, one row per currency, never added across them. Reads only; deposit_list shows each deposit.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • deposit_recordRecord a security or retainer deposit received from a client, in minor units, with its currency, the date it arrived and the bank reference.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
    Record a security or retainer deposit received from a client, in minor units, with its currency, the date it arrived and the bank reference. Returns the DEP-YYYY-NNNN id.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • deposit_statement_pdfCall this tool to render one client's A4 deposit statement and return a download link valid for one hour.1 finding

    Why it is in this group

    • The description's first verb is "call": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

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

      Matched text

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

      What this check looks for
    Description, as the server wrote it
    Call this tool to render one client's A4 deposit statement and return a download link valid for one hour. Titled DEPOSIT STATEMENT, every movement in date order, closing with what is still held. Pro.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • deposit_statement_textTurn one client's deposits into a plain-text statement to paste into an email: every movement in date order and the closing balance held.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
    Turn one client's deposits into a plain-text statement to paste into an email: every movement in date order and the closing balance held. Pass currency when they have more than one. Also a .txt download link valid one hour. Free on every tier.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • deposits_reportThe deposit book at a date: held per currency, received, applied and refunded, the oldest holdings with days held, and every deposit older than N days with nothing applied.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
    The deposit book at a date: held per currency, received, applied and refunded, the oldest holdings with days held, and every deposit older than N days with nothing applied. Pro; deposit_balance is free.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • 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
  • deposit_listList deposits newest first: DEP number, client, kind, date, reference and what was received, applied, refunded and still held, with the same four totalled per currency.No findings

    Why it is in this group

    • The name "deposit_list" says "list": a word for reading.
    Description, as the server wrote it
    List deposits newest first: DEP number, client, kind, date, reference and what was received, applied, refunded and still held, with the same four totalled per currency. Filter by client, status, kind, date.

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

    Matched text

    https://mcp.zovo.one/mcp/deposits: tools/list returned 11 tools to an anonymous client, including deposit_delete (destructive), deposit_refund (irreversible), deposit_record (write), deposit_apply (write), deposit_balance (write) and 4 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/deposits

Findings

Matches of fixed checks, with the text they matched.

1 warn
  • The server marks "deposit_statement_pdf" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

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

    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/deposits.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/deposits

Install

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

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

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__deposits__deposit_list",
      "mcp__deposits__license_status"
    ],
    "ask": [
      "mcp__deposits__deposit_record",
      "mcp__deposits__deposit_apply",
      "mcp__deposits__deposit_refund",
      "mcp__deposits__deposit_balance",
      "mcp__deposits__deposit_statement_text",
      "mcp__deposits__deposit_statement_pdf",
      "mcp__deposits__deposits_report",
      "mcp__deposits__license_activate"
    ],
    "deny": [
      "mcp__deposits__deposit_delete"
    ]
  }
}

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

Capability tags behind 1 rule
  • mcp__deposits__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/deposits/verify?hash=1dbc85823783ab876e6eb11172167756571c1879cf4d60190aa0c4d7d828c510" | jq -e '.changed == false'

Pinned hash 1dbc85823783, from Nov 15, 2026, 06: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/deposits/changes.xml

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

Badge

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

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

McpStamp Deposits MCP server: questions and answers

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

Is the McpStamp Deposits MCP server safe?

No scan can promise that. What its definitions show: 11 tools, 9 of which can change, send or delete something, and 1 finding 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 Deposits MCP server delete data?

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

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

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

What tools does the McpStamp Deposits MCP server have?

11 tools: 1 destructive, 1 irreversible, 7 write, 2 read. deposit_delete, deposit_refund, deposit_record, deposit_apply, deposit_balance, deposit_statement_text, deposit_statement_pdf, deposits_report and 3 more.

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

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

Does the McpStamp Deposits 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 Deposits MCP server changed its tools?

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