io.github.GillMacedo/latepayers
NPM · LATEPAYERS
AR aging from an invoice CSV: who owes what, how late, and who to chase first, on your machine.
Available components
Last scanned (10 hours ago)
Scores higher than 49% of npm servers
Category Finance and Payments
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency48
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 3 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability80
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 284 tokens (~142/item across 2 items; 2 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management13
- Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 72
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed npm/latepayers@0.1.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
receivables_aging_report Accounts receivable aging report ~225
Builds an accounts receivable aging report from an invoice CSV: what's owed in each overdue bucket, by customer, with who to chase first and how late each customer usually pays. Use for overdue invoices, collections and cash flow. Read-only, and never uses the network. Results include customer names and amounts from the file, so they reach the model. It can't contact anyone.
| Name | Type | Req | Description |
|---|---|---|---|
| as_of | string | – | Report date, YYYY-MM-DD. Default is today |
| columns | object | – | Column names by field (number, customer, issued, due, amount, paid, balance, paiddate, currency), when detection fails |
| date_format | string | – | dmy or mdy, needed only if the tool reports that dates are ambiguous |
| limit | null|integer | – | Most customers to return, highest priority first, default 100. 0 returns only the totals |
| path | string | yes | Path to the invoice CSV |
| terms_days | null|integer | – | Payment terms for invoices with no due date, default 30 |
| Name | Type | Req | Description |
|---|---|---|---|
| as_of | string | yes | – |
| buckets | object | yes | – |
| credits | null|array | yes | – |
| customer_count | integer | yes | – |
| customers_by_priority | null|array | yes | – |
| overdue_percent | number | yes | – |
| skipped_rows | null|array | yes | – |
| total_open | string | yes | – |
| total_overdue | string | yes | – |
| truncated | boolean | yes | – |
| warnings | null|array | yes | – |
No examples provided.
receivables_inspect_csv Inspect an invoice CSV ~59
Shows which columns latepayers detects in an invoice CSV and how many rows it can read, without returning row contents. Use if the file is unfamiliar or a report failed.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | Path to the invoice CSV |
| Name | Type | Req | Description |
|---|---|---|---|
| columns | object | yes | – |
| invoices | integer | yes | – |
| skipped | integer | yes | – |
No examples provided.
How do I install the io.github.GillMacedo/latepayers MCP server?
io.github.GillMacedo/latepayers runs locally as an npm package, launched with npx -y latepayers. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · latepayers
claude mcp add gillmacedo-latepayers -- npx -y latepayers
What is the io.github.GillMacedo/latepayers MCP server?
io.github.GillMacedo/latepayers is an MCP server listed in the public MCP registry as io.github.GillMacedo/latepayers. AR aging from an invoice CSV: who owes what, how late, and who to chase first, on your machine. This page covers its npm package (latepayers).
Is the io.github.GillMacedo/latepayers MCP server safe to use?
io.github.GillMacedo/latepayers scores 74 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. 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 io.github.GillMacedo/latepayers MCP server expose?
io.github.GillMacedo/latepayers exposes 2 tools: receivables_aging_report, receivables_inspect_csv. Their descriptions and schemas cost roughly 284 tokens of context every time the server is loaded.
Is the io.github.GillMacedo/latepayers MCP server still maintained?
io.github.GillMacedo/latepayers 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.
What licence is the io.github.GillMacedo/latepayers MCP server under?
io.github.GillMacedo/latepayers declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.