# Deposit by Ouroboros Apps (remote · deposit-continuity2.vercel.app)

Freelance deposit and payment schedule for AI assistants

- Trust score: 90/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `deposit-continuity2.vercel.app`: 90/100 (this document), [markdown](https://verifymcp.io/servers/lahutchins91-deposit/deposit-continuity2.md), [page](https://verifymcp.io/servers/lahutchins91-deposit/deposit-continuity2)

## Channel facts

- Endpoint: `https://deposit-continuity2.vercel.app/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `1.0.3`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 94/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 70/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 1079 tokens (~89/item across 12 items; 12 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **Tool Coverage**: 71/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 12 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Deposit by Ouroboros Apps MCP server?

Deposit by Ouroboros Apps is a hosted endpoint at https://deposit-continuity2.vercel.app/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http lahutchins91-deposit 'https://deposit-continuity2.vercel.app/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "lahutchins91-deposit": {
      "url": "https://deposit-continuity2.vercel.app/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "lahutchins91-deposit": {
      "type": "http",
      "url": "https://deposit-continuity2.vercel.app/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.lahutchins91-deposit]
url = "https://deposit-continuity2.vercel.app/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "lahutchins91-deposit": {
      "type": "remote",
      "url": "https://deposit-continuity2.vercel.app/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add lahutchins91-deposit --url 'https://deposit-continuity2.vercel.app/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  lahutchins91-deposit:
    url: "https://deposit-continuity2.vercel.app/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "lahutchins91-deposit": {
      "Transport": "http",
      "Url": "https://deposit-continuity2.vercel.app/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add lahutchins91-deposit -t streamable-http -u 'https://deposit-continuity2.vercel.app/mcp'
```

### Other

```json
{
  "mcpServers": {
    "lahutchins91-deposit": {
      "type": "http",
      "url": "https://deposit-continuity2.vercel.app/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 90, +1)

- [security] Stability: 0.97 → pass

### 2026-11-02 (score 89, +1)

No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-30 (score 88, +1)

No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-28 (score 87, +1)

No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-26 (score 86, +1)

No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-24 (score 85, +1)

No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-22 (score 84, +1)

No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-20 (score 83, +1)

No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (12)

### `list_schedules` (~39 tokens)

list schedules

List the signed-in freelancer's deposit schedules. Use a returned id with read_schedule. Do not guess a schedule.

Input parameters:

- `offset` (integer)

Output parameters:

- `data`

### `start_schedule` (~80 tokens)

start schedule

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.

Input parameters:

- `clientName` (string, required)
- `currency` (string, required)
- `projectTitle` (required)
- `reference` (string, required)

Output parameters:

- `data`

### `read_schedule` (~68 tokens)

read schedule

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.

Input parameters:

- `scheduleId` (string, required)

Output parameters:

- `data`

### `record_deposit` (~82 tokens)

record deposit

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.

Input parameters:

- `amountMinor` (integer, required)
- `dueOn` (string, required)
- `scheduleId` (string, required)

Output parameters:

- `data`

### `add_later_payment` (~85 tokens)

add later payment

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.

Input parameters:

- `amountMinor` (integer, required)
- `dueOn` (string, required)
- `label` (string, required)
- `scheduleId` (string, required)

Output parameters:

- `data`

### `move_payment_date` (~83 tokens)

move payment date

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.

Input parameters:

- `dueOn` (string, required)
- `paymentId`
- `scheduleId` (string, required)
- `target` (string, required)

Output parameters:

- `data`

### `waive_deposit` (~59 tokens)

waive deposit

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.

Input parameters:

- `scheduleId` (string, required)

Output parameters:

- `data`

### `mark_deposit_paid` (~62 tokens)

mark deposit paid

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.

Input parameters:

- `scheduleId` (string, required)

Output parameters:

- `data`

### `write_client_script` (~72 tokens)

write client script

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.

Input parameters:

- `scheduleId` (string, required)
- `script` (string, required)

Output parameters:

- `data`

### `commit_schedule` (~58 tokens)

commit schedule

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.

Input parameters:

- `confirmed` (boolean, required)
- `scheduleId` (string, required)

Output parameters:

- `data`

### `suggest_schedule_change` (~148 tokens)

suggest schedule change

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.

Input parameters:

- `amountMinor` (integer)
- `dueOn` (string)
- `kind` (string, required)
- `label` (string)
- `paymentId`
- `scheduleId` (string, required)
- `script` (string)
- `summary` (string, required)
- `target` (string)

Output parameters:

- `data`

### `accept_schedule_change` (~81 tokens)

accept schedule change

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.

Input parameters:

- `changeId` (required)
- `confirmed` (boolean, required)
- `scheduleId` (string, required)

Output parameters:

- `data`

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/lahutchins91-deposit/deposit-continuity2#diagnostics

## Score history

- 2026-11-05: 90
- 2026-11-04: 90
- 2026-11-03: 89
- 2026-11-02: 89
- 2026-11-01: 88
- 2026-10-31: 88
- 2026-10-30: 88
- 2026-10-29: 87
- 2026-10-28: 87
- 2026-10-27: 86
- 2026-10-26: 86
- 2026-10-25: 85
- 2026-10-24: 85
- 2026-10-23: 84
- 2026-10-22: 84
- 2026-10-21: 83
- 2026-10-20: 83
- 2026-10-19: 82
- 2026-10-18: 82
- 2026-10-17: 81
- 2026-10-16: 81
- 2026-10-15: 81
- 2026-10-14: 80
- 2026-10-13: 80
- 2026-10-12: 79
- 2026-10-11: 79
- 2026-10-10: 78
- 2026-10-07: 77

## Common questions

### What is the Deposit by Ouroboros Apps MCP server?

Deposit by Ouroboros Apps is an MCP server listed in the public MCP registry as io.github.LAHutchins91/deposit. Freelance deposit and payment schedule for AI assistants. This page covers its hosted endpoint (https://deposit-continuity2.vercel.app/mcp).

### Is the Deposit by Ouroboros Apps MCP server safe to use?

Deposit by Ouroboros Apps scores 90 out of 100 on VerifyMCP. 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 Deposit by Ouroboros Apps MCP server expose?

Deposit by Ouroboros Apps exposes 12 tools: list_schedules, start_schedule, read_schedule, record_deposit, add_later_payment, and 7 more. Their descriptions and schemas cost roughly 917 tokens of context every time the server is loaded.

### Does the Deposit by Ouroboros Apps MCP server require authentication?

Yes. Deposit by Ouroboros Apps asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the Deposit by Ouroboros Apps MCP server still maintained?

Deposit by Ouroboros Apps is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://deposit-continuity2.vercel.app/mcp
- Repository: https://github.com/LAHutchins91/deposit-mcp
- Website: https://ouroborosapps.com/docs/deposit
- Changelog RSS feed: https://verifymcp.io/servers/lahutchins91-deposit/deposit-continuity2.xml
- Changelog JSON feed: https://verifymcp.io/servers/lahutchins91-deposit/deposit-continuity2.json
- HTML version of this page: https://verifymcp.io/servers/lahutchins91-deposit/deposit-continuity2