Skip to content

Deposit by Ouroboros Apps MCP server

io.github.LAHutchins91/depositLAHutchins91streamable-httpv1.0.3Scanned

Freelance deposit and payment schedule for AI assistants

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

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

Tools listed without sign-in. Remote posture

With Anlyon

8 tools here can delete or cancel things. 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 Deposit by Ouroboros Apps MCP server can do

The Deposit by Ouroboros Apps MCP server is published by the GitHub account LAHutchins91. It has 12 tools. It can delete or cancel things (8 tools: record_deposit, add_later_payment, move_payment_date, waive_deposit and 4 more) and create or change data (2 tools: start_schedule and suggest_schedule_change). 2 tools only read.

None of its tools reads private data, brings in text other people write, or sends data out.

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 15, 2026, version 1.0.3.

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 8Claude Code: deny
  • accept_schedule_changeApply one suggested schedule change after the freelancer explicitly approves that change.No findings

    Why it is in this group

    • The name "accept_schedule_change" says "schedule": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Apply one suggested schedule change after the freelancer explicitly approves that change. Pass confirmed true only then. This is the path that may waive the deposit, mark it paid, or move a payment date. Calling it is not a substitute for the freelancer's approval.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: false
  • add_later_paymentAdd one later payment: a label, an amount in whole minor units, and a payment date.No findings

    Why it is in this group

    • The name "add_later_payment" says "add": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Add one later payment: a label, an amount in whole minor units, and a payment date. After the schedule is approved, a new later payment is refused until accept_schedule_change applies an add_later_payment suggestion.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: false
    • openWorldHint: false
  • commit_scheduleMark the current draft as the approved schedule.No findings

    Why it is in this group

    • The name "commit_schedule" says "commit": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Mark the current draft as the approved schedule. Pass confirmed true only after the freelancer explicitly approves the deposit, the later payment dates, and what the assistant may tell the client.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: false
  • mark_deposit_paidMark the deposit paid.No findings

    Why it is in this group

    • The name "mark_deposit_paid" says "mark": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Mark the deposit paid. After the schedule is approved, marking it paid is refused until accept_schedule_change applies a mark_deposit_paid suggestion. Do not tell the client the deposit is paid unless the record already says so.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: false
  • move_payment_dateMove a payment date.No findings

    Why it is in this group

    • The name "move_payment_date" says "move": a word for a change.
    • The name "move_payment_date" also says "payment": a word that usually means money moves, which cannot be taken back.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Move a payment date. target deposit moves the deposit date. target later moves one later payment and requires paymentId. After the schedule is approved, a different date is refused until accept_schedule_change applies a move_payment_date suggestion.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: false
    • openWorldHint: false
  • record_depositRecord the deposit amount in whole minor units and the deposit date as 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.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Record the deposit amount in whole minor units and the deposit date as YYYY-MM-DD. This does not waive the deposit and does not mark it paid. After the schedule is approved, a different amount or date is refused until an accepted schedule change.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: false
    • openWorldHint: false
  • waive_depositWaive the deposit.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 destructive (destructiveHint: true).
    Description, as the server wrote it
    Waive the deposit. After the schedule is approved, waiving is refused until accept_schedule_change applies a waive_deposit suggestion. Do not tell the client the deposit is waived unless the record already says so.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: false
  • write_client_scriptRecord what the assistant may tell the client about the deposit and payment dates.No findings

    Why it is in this group

    • The name "write_client_script" says "write": a word for a change.
    • The input takes a statement or command to run (input.script), which can change anything it can reach.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Record what the assistant may tell the client about the deposit and payment dates. After the schedule is approved, different wording is refused until an accepted revise_client_script suggestion. The assistant must not go beyond this script and the facts in read_schedule.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: false
    • openWorldHint: false
Changes things 2Claude Code: ask
  • start_scheduleStart a draft deposit schedule for one client project.No findings

    Why it is in this group

    • The name "start_schedule" says "start": a word for a change.
    Description, as the server wrote it
    Start a draft deposit schedule for one client project. Draft figures are not an approved commitment until commit_schedule. Currency is a three-letter code. Amounts later are minor units of that currency and are the freelancer's figures.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • suggest_schedule_changeRecord a suggested change.No findings

    Why it is in this group

    • The name "suggest_schedule_change" says "schedule": a word for a change.
    • The input takes a statement or command to run (input.script), which can change anything it can reach.
    Description, as the server wrote it
    Record a suggested change. This does not change the schedule. kind waive_deposit and kind mark_deposit_paid need only a summary. kind move_payment_date requires dueOn and target; target later also requires paymentId. kind revise_deposit requires amountMinor. kind add_later_payment requires label, amountMinor, and dueOn. kind revise_client_script requires script.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
Only reads 2Show 2 read-only tools
  • list_schedulesList the signed-in freelancer's deposit schedules.No findings

    Why it is in this group

    • The name "list_schedules" says "list": a word for reading.
    Description, as the server wrote it
    List the signed-in freelancer's deposit schedules. Use a returned id with read_schedule. Do not guess a schedule.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • read_scheduleRead the schedule before answering.No findings

    Why it is in this group

    • The name "read_schedule" says "read": a word for reading.
    Description, as the server wrote it
    Read the schedule before answering. Quote only this record. mayTellClient and clientScript are what the assistant may tell the client. Draft status is not an approved commitment. Proposed changes do not authorize a waiver, a paid deposit, or a new payment date.

    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 untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
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, 18:58 UTC, unchanged since Oct 22, 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://deposit-continuity2.vercel.app/.well-known/oauth-protected-resource/mcp
Authorization servers
https://uayvpvwwabvmkiynasyv.supabase.co/auth/v1
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 (8 destructive, 2 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://deposit-continuity2.vercel.app/mcp: tools/list returned 12 tools to an anonymous client, including record_deposit (destructive), add_later_payment (destructive), move_payment_date (destructive), waive_deposit (destructive), mark_deposit_paid (destructive) and 5 more

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

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

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

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

claude mcp add --transport http deposit https://deposit-continuity2.vercel.app/mcp
claude mcp add --transport http deposit https://deposit-continuity2.vercel.app/mcp

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__deposit__list_schedules",
      "mcp__deposit__read_schedule"
    ],
    "ask": [
      "mcp__deposit__start_schedule",
      "mcp__deposit__suggest_schedule_change"
    ],
    "deny": [
      "mcp__deposit__record_deposit",
      "mcp__deposit__add_later_payment",
      "mcp__deposit__move_payment_date",
      "mcp__deposit__waive_deposit",
      "mcp__deposit__mark_deposit_paid",
      "mcp__deposit__write_client_script",
      "mcp__deposit__commit_schedule",
      "mcp__deposit__accept_schedule_change"
    ]
  }
}

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

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.LAHutchins91/deposit/verify?hash=0472d6c959f848cff22613877e3c010b1e948ff3a50c4eb73733ec890a2a3b4c" | jq -e '.changed == false'

Pinned hash 0472d6c959f8, from Nov 15, 2026, 23: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.LAHutchins91/deposit/changes.xml

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

Badge

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

Source: MCP Registry · repository. Synced Oct 21, 2026, 18:17 UTC.

Deposit by Ouroboros Apps MCP server: questions and answers

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

Is the Deposit by Ouroboros Apps MCP server safe?

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

Yes. 8 tools can delete, cancel or revoke something: record_deposit, add_later_payment, move_payment_date, waive_deposit, mark_deposit_paid, write_client_script and 2 more.

Can the Deposit by Ouroboros Apps 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 Deposit by Ouroboros Apps MCP server have?

12 tools: 8 destructive, 2 write, 2 read. record_deposit, add_later_payment, move_payment_date, waive_deposit, mark_deposit_paid, write_client_script, commit_schedule, accept_schedule_change and 4 more.

Does the Deposit by Ouroboros Apps MCP server need sign-in or OAuth?

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

Does the Deposit by Ouroboros Apps MCP server send data to outside services?

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

Has the Deposit by Ouroboros Apps MCP server changed its tools?

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