Pink Agentic AI Payments (by PinkWallet): lets Claude, ChatGPT, Cursor pay vendor invoices within company spending rules (budgets, caps, allow-lists, human approval). Sandbox preview, test money.
Deposit is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Approved freelance deposit and payment dates for AI assistants, over MCP.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http deposit-mcp https://deposit-continuity2.vercel.app/mcp
# 2 — ask your agent for something these tools do
# list_schedules, start_schedule, read_schedule and 9 more
Deposit costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http deposit-mcp https://deposit-continuity2.vercel.app/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
12 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
List the signed-in freelancer's deposit schedules. Use a returned id with read_schedule. Do not guess a schedule.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| offset | integer | no | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| clientName | string | yes | — |
| projectTitle | yes | — | |
| reference | string | yes | — |
| currency | string | yes | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| scheduleId | string | yes | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| scheduleId | string | yes | — |
| amountMinor | integer | yes | — |
| dueOn | string | yes | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| scheduleId | string | yes | — |
| label | string | yes | — |
| amountMinor | integer | yes | — |
| dueOn | string | yes | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| scheduleId | string | yes | — |
| dueOn | string | yes | — |
| target | string | yes | — |
| paymentId | no | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| scheduleId | string | yes | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| scheduleId | string | yes | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| scheduleId | string | yes | — |
| script | string | yes | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| scheduleId | string | yes | — |
| confirmed | boolean | yes | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| scheduleId | string | yes | — |
| kind | string | yes | — |
| summary | string | yes | — |
| target | string | no | — |
| paymentId | no | — | |
| dueOn | string | no | — |
| amountMinor | integer | no | — |
| label | string | no | — |
| script | string | no | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| scheduleId | string | yes | — |
| changeId | yes | — | |
| confirmed | boolean | yes | — |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Deposit or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither: the repository linked on this page is where this record was collected from, not a copy of what the address serves, so it is not graded in its place. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.3.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Deposit can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.