# io.github.CloudCorpRecords/ledgerbackup (npm · @reneturcios/ledgerbackup)

Read-only backup and export of Xero accounting data: organisations, exports, manifests, downloads.

- Trust score: 70/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- npm · `@reneturcios/ledgerbackup`: 70/100 (this document), [markdown](https://verifymcp.io/servers/cloudcorprecords-ledgerbackup/reneturcios-ledgerbackup.md), [page](https://verifymcp.io/servers/cloudcorprecords-ledgerbackup/reneturcios-ledgerbackup)
- oci · `ghcr.io/cloudcorprecords/ledgerbackup`: 41/100, [markdown](https://verifymcp.io/servers/cloudcorprecords-ledgerbackup/ghcr-io-cloudcorprecords-ledgerbackup.md), [page](https://verifymcp.io/servers/cloudcorprecords-ledgerbackup/ghcr-io-cloudcorprecords-ledgerbackup)

## Channel facts

- Registry: `npm`
- Package: `@reneturcios/ledgerbackup`
- Version: `0.1.0`
- Transport: `stdio`

## Trust breakdown

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. 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-05.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 30 of 92 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 0 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 78/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 985 tokens (~140/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability observed for 0 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.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 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.

**Unverified: 1 category.** A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

## Install

### How do I install the io.github.CloudCorpRecords/ledgerbackup MCP server?

io.github.CloudCorpRecords/ledgerbackup runs locally as an npm package, launched with npx -y @reneturcios/ledgerbackup. 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 cloudcorprecords-ledgerbackup -- npx -y @reneturcios/ledgerbackup
```

### Cursor

```json
{
  "mcpServers": {
    "cloudcorprecords-ledgerbackup": {
      "command": "npx",
      "args": [
        "-y",
        "@reneturcios/ledgerbackup"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "cloudcorprecords-ledgerbackup": {
      "command": "npx",
      "args": [
        "-y",
        "@reneturcios/ledgerbackup"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add cloudcorprecords-ledgerbackup -- npx -y @reneturcios/ledgerbackup
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "cloudcorprecords-ledgerbackup": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@reneturcios/ledgerbackup"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add cloudcorprecords-ledgerbackup --command npx --arg -y --arg @reneturcios/ledgerbackup
```

### Hermes

```yaml
mcp_servers:
  cloudcorprecords-ledgerbackup:
    command: "npx"
    args: ["-y", "@reneturcios/ledgerbackup"]
```

### Netclaw

```json
{
  "McpServers": {
    "cloudcorprecords-ledgerbackup": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@reneturcios/ledgerbackup"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add cloudcorprecords-ledgerbackup -t stdio -c npx -a -y @reneturcios/ledgerbackup
```

### Other

```json
{
  "mcpServers": {
    "cloudcorprecords-ledgerbackup": {
      "command": "npx",
      "args": [
        "-y",
        "@reneturcios/ledgerbackup"
      ]
    }
  }
}
```

## 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-05 (score 70)

First indexed and scored.

## MCP tools (7)

### `list_organisations` (~35 tokens)

List accounting organisations

List the accounting organisations (Xero, Sage, Reckon, or QuickBooks) connected to the authenticated Boxkite account.

### `start_export` (~185 tokens)

Start a one-off accounting data export

Starts a read-only export of one accounting organisation's data (Xero, Sage, Reckon, or QuickBooks). Costs $39 per organisation: when payment is outstanding the response is status 'awaiting_payment' with a Stripe checkoutUrl for the user to complete in a browser, and the export begins once that payment settles. This is not a status endpoint: it reports only the state at creation, and repeat calls return the existing export for that organisation rather than creating or charging for a second one. Export progress is reported by get_export_status, and newly created exports appear in list_exports. A typical export runs for hours, and pauses whenever it meets a provider rate limit or Boxkite's egress budget — anything from under a minute to the next UTC day. get_export_status reports when it resumes.

Input parameters:

- `organisationId` (string, required): Organisation id from list_organisations

### `list_exports` (~94 tokens)

List exports

List one-off exports (newest first), optionally for one organisation. Use this to find an export after payment and to poll its status until it is 'ready'. Side-effect free: it never starts a new export or charges anything. Each entry carries progress, parkedUntil and pollAfterSeconds.

Input parameters:

- `organisationId` (string): Only list exports for this Xero organisation id; leave it out to list exports for all organisations.

### `get_export_status` (~199 tokens)

Get export status

Reports the state of one export: status (queued | running | ready | failed) and whether its download is available yet. Also returns progress {discovered, transferred, percent}; parkedUntil; and pollAfterSeconds, the interval after which this status is expected to have changed. A large export runs for hours, so pollAfterSeconds can be a long interval. parkedUntil is a timestamp, present whenever work on the organisation is paused and expected to resume. How long varies by cause and is not worth guessing at: hitting Xero's per-minute limit pauses for under a minute, approaching its daily quota pauses for about an hour, and exhausting the daily quota or Boxkite's own egress budget pauses until the next UTC day. Wait until the timestamp (or pollAfterSeconds, which already accounts for it) rather than describing a cause to the user.

Input parameters:

- `exportId` (string, required): The id of the export whose status should be reported.

### `get_export_manifest` (~173 tokens)

Get export manifest

See what an IN-PROGRESS export contains so far (entities included, per-entity record/file counts, and per-file checksums), growing as discovery and downloading proceed. The per-file list is paged: check filesPage.hasMore and pass fileOffset to walk it. Once the export finishes, this returns status 'complete' with a pointer instead of a list, because the full manifest travels inside the ZIP as manifest.json: get a download URL, then read manifest.json from the archive.

Input parameters:

- `exportId` (string, required): The id of the in-progress export whose manifest (contents so far) should be returned.
- `fileLimit` (integer): Files per page (default 500, max 5000)
- `fileOffset` (integer): Index of the first file to return (default 0)

### `get_export_mapping` (~188 tokens)

Get export file→object mapping

For an IN-PROGRESS export, get the mapping of each file discovered so far to the accounting object it represents or is attached to (e.g. which invoice a receipt PDF belongs to). Paged (default 200 files, max 500): check filesPage.hasMore and pass fileOffset for the next page; the `objects` map covers only the files on the current page. Once the export finishes, this returns status 'complete' with a pointer instead: the full mapping ships under Info/ inside the ZIP, so download the archive and read Info/files.json from it.

Input parameters:

- `exportId` (string, required): The id of the in-progress export whose file-to-object mapping should be returned.
- `fileLimit` (integer): Files per page (default 200, max 500)
- `fileOffset` (integer): Index of the first file to return (default 0)

### `get_download_url` (~111 tokens)

Get export download URL

Returns a short-lived signed URL for the export ZIP, valid within the export's 7-day retention window, along with byteSize (the archive's size in bytes, null if unavailable) and fileCount. These archives range from a few MB to several GB. The archive contains the exported files plus manifest.json (every file with its sha256) and Info/ (the file-to-Xero-object mapping).

Input parameters:

- `exportId` (string, required): The id of the export whose signed download URL should be returned.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/cloudcorprecords-ledgerbackup/reneturcios-ledgerbackup#diagnostics

## Score history

- 2026-11-05: 70

## Common questions

### What is the io.github.CloudCorpRecords/ledgerbackup MCP server?

io.github.CloudCorpRecords/ledgerbackup is an MCP server listed in the public MCP registry as io.github.CloudCorpRecords/ledgerbackup. Read-only backup and export of Xero accounting data: organisations, exports, manifests, downloads. This page covers its npm package (@reneturcios/ledgerbackup).

### Is the io.github.CloudCorpRecords/ledgerbackup MCP server safe to use?

io.github.CloudCorpRecords/ledgerbackup scores 70 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.CloudCorpRecords/ledgerbackup MCP server expose?

io.github.CloudCorpRecords/ledgerbackup exposes 7 tools: list_organisations, start_export, list_exports, get_export_status, get_export_manifest, and 2 more. Their descriptions and schemas cost roughly 985 tokens of context every time the server is loaded.

### Is the io.github.CloudCorpRecords/ledgerbackup MCP server still maintained?

io.github.CloudCorpRecords/ledgerbackup 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.CloudCorpRecords/ledgerbackup MCP server under?

io.github.CloudCorpRecords/ledgerbackup declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- npm package: https://www.npmjs.com/package/@reneturcios/ledgerbackup
- Socket report: https://socket.dev/npm/package/@reneturcios/ledgerbackup
- Repository: https://github.com/CloudCorpRecords/ledgerbackup
- Changelog RSS feed: https://verifymcp.io/servers/cloudcorprecords-ledgerbackup/reneturcios-ledgerbackup.xml
- Changelog JSON feed: https://verifymcp.io/servers/cloudcorprecords-ledgerbackup/reneturcios-ledgerbackup.json
- HTML version of this page: https://verifymcp.io/servers/cloudcorprecords-ledgerbackup/reneturcios-ledgerbackup