Collections Optimizer
Server Details
Prioritise overdue accounts by recovery uplift and recommend a compliant contact strategy.
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- OAuth
- Works in Glama
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-06-18
- URL
- Repository
- Saify-Technologies/saifs-ai-mcps-docs
- GitHub Stars
- 0
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 2 tools
The two tools have a clear selection boundary: use collections_optimizer for up to 5,000 accounts with data sent directly, and use collections_optimizer_get_engine for larger books or sandbox files. The similarity of the names could cause a brief pause, but the descriptions make the threshold-based split explicit.
Both names use snake_case and share the collections_optimizer prefix, so they are readable and related. However, the pattern is not a clean verb_noun convention: one is a standalone noun phrase and the other appends a get_engine action suffix.
Two tools is thin for a server covering propensity modeling, queue generation, compliance checks, forecasting, agent allocation, and champion-challenger testing. The design intentionally uses one monolithic engine plus a large-data fallback, which is coherent but gives the agent little granularity.
The main tool covers a very broad collections-optimization surface: scoring, queue ranking, compliance rules, self-cure lists, roll rates, forecasts, survival analysis, allocation, and testing. The large-data path is also covered by the engine-script fallback, with only minor gaps around finer-grained account lookup or ingestion workflows.
Publisher details
- Operator
- Saifs.ai · Publisher source
- Operator website
- https://saifs.ai/ · Publisher source
- Vendor relationship
- Not applicable
- Documentation
- Not applicable
- Trust center
- Not applicable
- Restrictions
- Not applicable
Available Tools
2 toolscollections_optimizerCollections Queue, Contact Strategy & Roll-Rate PlannerARead-onlyInspect
Daily collections plan within fair-collection rules. From today's overdue accounts (account_id, balance, dpd, promises, contact counts, consents, stop flags) and optional payment history (paid, contacted, channel, recovered), contact log, monthly snapshots, agents and test results it returns: propensity to pay (L2 logistic, weight-of-evidence driver report, held-out AUC); self-cure chance and contact uplift (two models, contacted vs not, held-out Qini; rule of thumb at cold start); a call queue ranked by expected extra recovery per call within agent capacity, with the best permitted channel, call window learned from reach rates, tone tier, why, and rule checks + id on every recommendation; self-cure, deferred (earliest permitted date) and do-not-contact lists; balance-first / oldest-first comparison; Markov roll rates, forecasts and eventual write-off chance; Kaplan-Meier time to cure; Hungarian agent allocation by language, skill and success; champion-challenger split and z-test. Hard limits: India 08:00-19:00, US 08:00-21:00 and Reg F 7-in-7 and 7-day wait, cease/dispute/bankruptcy/deceased/legal/hardship never queued; policy can only tighten. Decision cards first. Up to 5,000 accounts; larger: collections_optimizer_get_engine.
Inputs: l2, as_of, agents, policy, +18 more. Returns: queue, alerts, status, drivers, +17 more
collections_optimizer_get_engineCollections Optimizer — Get Engine Script (large books)ARead-onlyInspect
For books over 5,000 accounts or 20,000 rows of history, contact log or snapshots, or any such file already in your code sandbox. Returns a complete numpy-only Python script with the same engine as collections_optimizer; it reads accounts, history, contact log, snapshots, agents and test results, prints the decision cards, the queue and the do-not-contact list, and writes everything to collections_plan.json. No debtor data reaches this server on this path.
Inputs: params, agents_path, history_path, accounts_path, +3 more. Returns: notes, paths, script, language, +7 more
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Review overdue B2B receivables and prepare held collection intakes. No automatic debtor outreach.
Machine-paid revenue intelligence, recovery decisions, and x402 routing for AI agents.
Place overdue B2B invoices for collection and track outreach, payments and remittances.
Choose and rank suppliers, size orders and classify spend from delivery and purchase data.
Related MCP Servers
- AlicenseNot gradedqualityBmaintenanceEnables autonomous agents to optimize payment recovery by applying decline-code-specific retry windows and reducing involuntary churn through MCP-accessible ledger and fraud-checking workflows.7MIT
- AlicenseNot gradedqualityCmaintenanceEnables finance teams to preview, prepare, approve, send, and audit multilingual overdue-invoice payment reminders through an MCP client, with human approval and safeguards against paid or disputed invoices.MIT
- AlicenseNot gradedqualityCmaintenanceEnables agents to delegate decisions to a configurable model, returning recommended choices with percentage scores and profile-based routing.7 npmMIT
- FlicenseNot gradedqualityCmaintenanceEnables creditworthiness analysis for non-traditional borrowers using rule-based scoring, financial behavior assessment, and underwriting report generation via MCP tools.1-
Glama MCP Gateway
Add one secure layer between your agents and this server.