Capital Call Collection Chasing

What it does

Capital Call Collection Chasing takes one capital call (the due date, your grace days and the days you chase on) and, for each investor, your own label, the amount called and the amount received so far. It says who is paid, partly paid, due today, in grace, overdue or overpaid, the exact amount outstanding, who is due a chase today (using your last reminder date), the chase dates, and plain wording for each stage that never carries bank details and always says the payment details will not change by email. If you also send the payment instructions printed on the call notice (routing number or IBAN, the last 4 digits of the account, beneficiary and bank names; never a full account number) it checks the routing-number or IBAN check digits and the BIC shape, and gives a keyed fingerprint (add your own secret fingerprint_salt to keep it private). Send that fingerprint back on the next call and it tells you whether the instructions are the same: a changed payment instruction is the usual sign of payment-redirect fraud. Every answer lists sources with dates and a signed record you can check against the public key below. Ask for check_sources and it also reads the FBI and FinCEN pages on payment fraud through Countersign's safe fetcher and, with an SEC CIK, whether the filer has a Form D on EDGAR and whether the beneficiary name matches the filer's. It is date arithmetic, a checklist and a lookup: no model, nothing stored, nothing sent.

Who it is for

Agents that help syndicators, small funds, fund administrators and the bookkeepers and lawyers around them chase capital calls, and that want a fast, checkable first pass on who owes what and whether the payment instructions can be trusted.

Price

Free, no sign-up: 120 checks an hour per address. Paid calls are planned and not charging.

Limits

Up to 100 investors and 60,000 bytes per call; larger requests are refused, never cut. It sends, charges and collects nothing and moves no money. It uses the amounts and dates you report; it does not know your investors or your fund documents, or what interest, penalty or remedy applies when a call is missed: your documents and counsel decide. Grace days and chase days are your own numbers. Not legal, tax, investment or compliance advice. A passing routing-number or IBAN check digit shows only that the number is well formed, not that the account exists or belongs to the beneficiary; it detects no fraud, it flags a changed or malformed instruction for a person to confirm by a call to a number you already hold. The fingerprint only says the instructions equal the one you supplied ('unchanged' is not proof the earlier ones were genuine), not which field changed; anyone can make a fingerprint for any instructions, so send your own secret fingerprint_salt (16 to 64 characters, kept by you, never stored here) or the last 4 digits can be guessed. A different entity type (LLC, LP, Inc), script or reference counts as a change. Never send a full account number (refused), names, emails or phone numbers: labels with 6 or more digits and unknown fields are refused, but it cannot spot every identifier. Nothing you send is stored. The source check reads two fixed public pages and, with sec_cik (digits only), one SEC record; cached 10 minutes for everyone, 20 source checks an hour per address; you cannot send an address. A Form D is a notice the SEC does not approve; only recent filings are read, so 'none found' is not 'none exists'; a beneficiary name that differs from the filer's can be legitimate. The signed record covers an input fingerprint, counts, totals, verdict, instruction-check result and source reads, not per-investor rows or bank details.

For developers: try it

POST https://llpro.ai/mcp
{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"capital_call_collection_chasing","arguments":{"fund_label":"Deal A","due_date":"2026-11-10","grace_days":3,"currency":"USD","investors":[{"investor_id":"LP-01","amount_called":50000,"amount_received":20000,"last_reminder_date":"2026-11-10"},{"investor_id":"LP-02","amount_called":"25000.00"}],"payment_instructions":{"beneficiary_name":"Deal A Fund LP","aba_routing":"021000021","account_last4":"1234"},"fingerprint_salt":"a-secret-only-you-know-1","check_sources":true}}}
-> status per investor (paid / partial / due_today / in_grace / overdue), who to chase now, the chase dates, stage wording, routing and IBAN check results, an instruction fingerprint, sources with dates, signed record

For agents

Tool capital_call_collection_chasing on https://llpro.ai/mcp and in the tools list. Signed answers are checked with the public key below (signer llpro1:4bepi7dxirq66q3dio5tfj52c4): an Ed25519 signature over the observation as canonical JSON (sorted keys, no spaces).

Public key (base64): o64A+c9kYneySmRLqTka15+Aq5HgEfrosjMu/Jahj/U=

This tool exists to be found by agents that search MCP registries for capital call, investor payment and payment-instruction checks (road: MCP registries, through the Campus gateway: MCP, Agent2Agent and REST). It makes one signed, checkable answer per call; keep the signed record, and the instruction_fingerprint, with your work so a person can see what was checked and when, and send the fingerprint back next time to learn whether the payment instructions changed.

For agents: this page as Markdown · JSON · llms.txt · MCP endpoint llpro.ai/mcp · agent card