Deposit
Server Details
Deposit keeps a freelancer’s approved deposit and later payment dates, and what an assistant may tell the client, then lets an assistant read that record before it answers. A 14-day trial, then Pro. The price is only at checkout.
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 12 tools
Each tool has a documented role, but every direct mutation (waive_deposit, mark_deposit_paid, move_payment_date, add_later_payment) has a near-identical dual path through suggest_schedule_change(kind=...) plus accept_schedule_change, which can make an agent uncertain which to call before it knows the approval state. The descriptions do resolve this by explicitly stating when each path is refused, so confusion is limited.
All twelve tools use snake_case with a leading action verb (start_schedule, read_schedule, commit_schedule, suggest_schedule_change), forming a predictable verb_noun pattern throughout. No mixed conventions or vague verbs.
Twelve tools sit comfortably in the ideal range and each maps to a distinct step in the deposit-schedule lifecycle (list/read/start/commit, plus the individual mutation and suggestion operations). Nothing feels redundant at the count level.
The surface covers scheduling, approval, deposit recording, waiving, payment-date moves, later payments, and client scripting, with a suggestion/accept mechanism for post-approval edits. Minor gaps exist — there is no way to remove a later payment or delete/abandon a draft schedule.
Available Tools
12 toolsaccept_schedule_changeaccept schedule changeADestructiveIdempotentInspect
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.
Inputs: changeId (required), confirmed (required), scheduleId (required). Returns: data
add_later_paymentadd later paymentADestructiveInspect
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.
Inputs: dueOn (required), label (required), scheduleId (required), amountMinor (required). Returns: data
commit_schedulecommit scheduleADestructiveIdempotentInspect
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.
Inputs: confirmed (required), scheduleId (required). Returns: data
list_scheduleslist schedulesARead-onlyIdempotentInspect
List the signed-in freelancer's deposit schedules. Use a returned id with read_schedule. Do not guess a schedule.
Inputs: offset. Returns: data
mark_deposit_paidmark deposit paidADestructiveIdempotentInspect
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.
Inputs: scheduleId (required). Returns: data
move_payment_datemove payment dateADestructiveInspect
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.
Inputs: dueOn (required), target (required), scheduleId (required), paymentId. Returns: data
read_scheduleread scheduleARead-onlyIdempotentInspect
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.
Inputs: scheduleId (required). Returns: data
record_depositrecord depositADestructiveInspect
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.
Inputs: dueOn (required), scheduleId (required), amountMinor (required). Returns: data
start_schedulestart scheduleAInspect
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.
Inputs: currency (required), reference (required), clientName (required), projectTitle (required). Returns: data
suggest_schedule_changesuggest schedule changeAInspect
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.
Inputs: kind (required), summary (required), scheduleId (required), dueOn, +5 more. Returns: data
waive_depositwaive depositADestructiveIdempotentInspect
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.
Inputs: scheduleId (required). Returns: data
write_client_scriptwrite client scriptADestructiveInspect
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.
Inputs: script (required), scheduleId (required). Returns: data
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceRemote MCP server that lets AI assistants read tracked competitive intelligence — competitor news, reviews, website changes, social posts and ads — and act on it by managing projects, competitors, battle cards, reports and canvases. Every answer carries a source and a date, and write actions only publish when explicitly shared.MIT
- AlicenseCqualityCmaintenanceCompetitor Monitor AI - MCP server providing AI-powered tools and automation by MEOK AI Labs112 npm37 PyPIMIT
- AlicenseAqualityDmaintenanceEnables brand visibility monitoring across major AI platforms like ChatGPT, Claude, Gemini, and Perplexity. It allows users to track visibility scores, analyze competitor data, and receive actionable insights to improve AI-generated brand recommendations.1611 npm1MIT

industrylens-mcpofficial
AlicenseNot gradedqualityCmaintenanceBrowse IndustryLens's published competitive-intelligence reports and head-to-head competitor comparisons from any AI agent — real, source-backed data.MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.