# Zovo AR Aging Report (remote · ar-aging.zovo.one)

Make an accounts receivable aging report from your open invoices and see who owes you money.

- Trust score: 79/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `ar-aging.zovo.one`: 79/100 (this document), [markdown](https://verifymcp.io/servers/theluckystrike-ar-aging/ar-aging.md), [page](https://verifymcp.io/servers/theluckystrike-ar-aging/ar-aging)

## Channel facts

- Endpoint: `https://ar-aging.zovo.one/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 70/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1316 tokens (~438/item across 3 items; 2 tools + 1 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 43/100
  - Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.
  - Supports UI / widget rendering.

## Install

### How do I install the Zovo AR Aging Report MCP server?

Zovo AR Aging Report is a hosted endpoint at https://ar-aging.zovo.one/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http theluckystrike-ar-aging 'https://ar-aging.zovo.one/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "theluckystrike-ar-aging": {
      "url": "https://ar-aging.zovo.one/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "theluckystrike-ar-aging": {
      "type": "http",
      "url": "https://ar-aging.zovo.one/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.theluckystrike-ar-aging]
url = "https://ar-aging.zovo.one/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "theluckystrike-ar-aging": {
      "type": "remote",
      "url": "https://ar-aging.zovo.one/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add theluckystrike-ar-aging --url 'https://ar-aging.zovo.one/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  theluckystrike-ar-aging:
    url: "https://ar-aging.zovo.one/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "theluckystrike-ar-aging": {
      "Transport": "http",
      "Url": "https://ar-aging.zovo.one/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add theluckystrike-ar-aging -t streamable-http -u 'https://ar-aging.zovo.one/mcp'
```

### Other

```json
{
  "mcpServers": {
    "theluckystrike-ar-aging": {
      "type": "http",
      "url": "https://ar-aging.zovo.one/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-21 (score 79, +1)

No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-19 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-17 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-15 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-13 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-10 (score 74, +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.

### 2026-11-09 (score 73, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-08 (score 73)

First indexed and scored.

## MCP tools (2)

### `generate_aging_report` (~569 tokens)

Generate AR aging report

Use this when the user wants an accounts receivable aging report (AR aging report, aged receivables, 'who owes me money and how late', ar aging report template filled in) from open invoices typed in chat, pasted as CSV/TSV, or attached as a CSV/XLSX export from QuickBooks, Xero, FreshBooks or Wave. Buckets each open balance into Current, 1-30, 31-60, 61-90 and over 90 days past due as of a date (default today in New York), with per-customer and grand totals that add up to the cent, partial payments and credit memos, optional DSO from credit sales, polite past-due reminder email drafts from invoice facts, and aging PDF, Excel and CSV downloads. Does not connect to accounting software, send emails or collect payments. Do not use for accounts payable (bills you owe).

Input parameters:

- `as_of_date`: Age the invoices as of this date, e.g. "2026-10-31". Default today in New York time.
- `company_name`: Your business name for the report header and email sign-off, e.g. "Bright Path Design LLC".
- `credit_sales` (number|string|null): Credit sales for the period, to compute DSO, e.g. 240000 or "$240,000".
- `currency`: Currency code, e.g. "USD" (default), "CAD", "EUR". With a mixed-currency file, only this currency is aged.
- `default_terms` (number|string|null): Terms for invoices with no due date and no terms, e.g. "Net 30" (default) or 15.
- `file` (object): An open invoices or A/R aging export (CSV, TSV or XLSX) from QuickBooks, Xero, FreshBooks, Wave or a spreadsheet, e.g. open_invoices.csv.
- `invoices`: Open invoices: an array of objects like {customer:"Acme Corp", invoice_number:"INV-1042", invoice_date:"2026-08-01", terms:"Net 30", amount:1200, amount_paid:200}, or pasted CSV/TSV text with a heade…
- `sales_period_days` (number|string|null): Days in the credit sales period for DSO, e.g. 365 (default), 90, "quarter", "month".
- `sender_name`: Name to sign the reminder emails with, e.g. "Dana Lee". Default the company name.

Output parameters:

- `as_of_date` (string)
- `as_of_note` (string)
- `assumptions` (array)
- `buckets` (array)
- `currency` (string)
- `customers` (array)
- `customers_not_shown` (number)
- `downloads` (object)
- `dso`
- `file_total_check` (string|null)
- `input` (object)
- `kind` (string)
- `pdf_pages` (number)
- `reminders` (array)
- `reminders_total` (number)
- `totals` (object)

### `generate_customer_statements` (~581 tokens)

Generate customer statements

Use this when the user wants customer statements (customer statement template, statement of account, open item statement) for customers who owe them money, from the same open invoices: typed, pasted CSV/TSV, or an attached CSV/XLSX export. Returns a PDF with one page per customer listing each open invoice with date, due date, amount, paid, open balance and days past due, an aging strip and the balance due, plus polite past-due reminder email drafts. Filter by customer names or overdue_only. Does not send statements or emails, and does not build an aging summary (use generate_aging_report).

Input parameters:

- `as_of_date`: Age the invoices as of this date, e.g. "2026-10-31". Default today in New York time.
- `company_address`: Your address or contact lines for the statement header, e.g. "12 Main St, Austin TX 78701, billing@brightpath.com".
- `company_name`: Your business name for the report header and email sign-off, e.g. "Bright Path Design LLC".
- `currency`: Currency code, e.g. "USD" (default), "CAD", "EUR". With a mixed-currency file, only this currency is aged.
- `customers`: Only these customers, e.g. ["Acme Corp", "Globex"] or "Acme Corp, Globex". Default every customer with a balance.
- `default_terms` (number|string|null): Terms for invoices with no due date and no terms, e.g. "Net 30" (default) or 15.
- `file` (object): An open invoices or A/R aging export (CSV, TSV or XLSX) from QuickBooks, Xero, FreshBooks, Wave or a spreadsheet, e.g. open_invoices.csv.
- `invoices`: Open invoices: an array of objects like {customer:"Acme Corp", invoice_number:"INV-1042", invoice_date:"2026-08-01", terms:"Net 30", amount:1200, amount_paid:200}, or pasted CSV/TSV text with a heade…
- `message`: Short note printed on every statement, e.g. "Thank you for your business."
- `overdue_only` (boolean|string|null): true to make statements only for customers with past-due invoices. Default false.
- `remit_to`: Payment instructions printed on each statement, e.g. "ACH or check to Bright Path Design, 12 Main St".
- `sender_name`: Name to sign the reminder emails with, e.g. "Dana Lee".

Output parameters:

- `as_of_date` (string)
- `as_of_note` (string)
- `currency` (string)
- `downloads` (object)
- `input` (object)
- `kind` (string)
- `notes` (array)
- `pages` (number)
- `reminders` (array)
- `reminders_total` (number)
- `statements` (array)
- `statements_count` (number)
- `statements_not_listed` (number)
- `totals` (object)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/theluckystrike-ar-aging/ar-aging#diagnostics

## Score history

- 2026-11-21: 79
- 2026-11-20: 78
- 2026-11-19: 78
- 2026-11-18: 77
- 2026-11-17: 77
- 2026-11-16: 76
- 2026-11-15: 76
- 2026-11-14: 75
- 2026-11-13: 75
- 2026-11-12: 74
- 2026-11-11: 74
- 2026-11-10: 74
- 2026-11-09: 73
- 2026-11-08: 73

## Common questions

### What is the Zovo AR Aging Report MCP server?

Zovo AR Aging Report is an MCP server listed in the public MCP registry as io.github.theluckystrike/ar-aging. Make an accounts receivable aging report from your open invoices and see who owes you money. This page covers its hosted endpoint (https://ar-aging.zovo.one/mcp).

### Is the Zovo AR Aging Report MCP server safe to use?

Zovo AR Aging Report scores 79 out of 100 on VerifyMCP. 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 Zovo AR Aging Report MCP server expose?

Zovo AR Aging Report exposes 2 tools: generate_aging_report, generate_customer_statements. Their descriptions and schemas cost roughly 1,150 tokens of context every time the server is loaded.

### Does the Zovo AR Aging Report MCP server require authentication?

No. We connected to Zovo AR Aging Report without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Zovo AR Aging Report MCP server still maintained?

Zovo AR Aging Report is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the Zovo AR Aging Report MCP server?

VerifyMCP ran 14 checks on Zovo AR Aging Report, covering TLS certificate, Authorization, HTTPS, HSTS header and 10 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://ar-aging.zovo.one/mcp
- Website: https://ar-aging.zovo.one/
- Changelog RSS feed: https://verifymcp.io/servers/theluckystrike-ar-aging/ar-aging.xml
- Changelog JSON feed: https://verifymcp.io/servers/theluckystrike-ar-aging/ar-aging/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/theluckystrike-ar-aging/ar-aging.json
- HTML version of this page: https://verifymcp.io/servers/theluckystrike-ar-aging/ar-aging
