io.github.CloudCorpRecords/ledgerbackup
OCI · GHCR.IO/CLOUDCORPRECORDS/LEDGERBACKUP · 2 COMPONENTS
Read-only backup and export of Xero accounting data: organisations, exports, manifests, downloads.
Available components
Last scanned (11 hours ago)
Scores higher than 46% of OCI servers
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 Security0
- No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
- Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
Provenance & Transparency45
- 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 0 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability78
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability observed for 0 of 30 days with no destabilising changes; credit accrues until the full window elapses.Unverified
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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 2 categories
Categories scored 0 because we could not verify them: 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.
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 41
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 oci/ghcr.io/cloudcorprecords/ledgerbackup@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 | oci |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
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 →
get_download_url Get export download URL ~111
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).
| Name | Type | Req | Description |
|---|---|---|---|
| exportId | string | yes | The id of the export whose signed download URL should be returned. |
No output schema declared.
No examples provided.
get_export_manifest Get export manifest ~173
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.
| Name | Type | Req | Description |
|---|---|---|---|
| exportId | string | yes | 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) |
No output schema declared.
No examples provided.
get_export_mapping Get export file→object mapping ~188
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.
| Name | Type | Req | Description |
|---|---|---|---|
| exportId | string | yes | 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) |
No output schema declared.
No examples provided.
get_export_status Get export status ~199
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.
| Name | Type | Req | Description |
|---|---|---|---|
| exportId | string | yes | The id of the export whose status should be reported. |
No output schema declared.
No examples provided.
list_exports List exports ~94
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.
| Name | Type | Req | Description |
|---|---|---|---|
| organisationId | string | – | Only list exports for this Xero organisation id; leave it out to list exports for all organisations. |
No output schema declared.
No examples provided.
list_organisations List accounting organisations ~35
List the accounting organisations (Xero, Sage, Reckon, or QuickBooks) connected to the authenticated Boxkite account.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
start_export Start a one-off accounting data export ~185
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.
| Name | Type | Req | Description |
|---|---|---|---|
| organisationId | string | yes | Organisation id from list_organisations |
No output schema declared.
No examples provided.
How do I install the io.github.CloudCorpRecords/ledgerbackup MCP server?
io.github.CloudCorpRecords/ledgerbackup runs locally as a container image, launched with docker run --rm -i ghcr.io/cloudcorprecords/ledgerbackup:0.1.0. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.
oci · ghcr.io/cloudcorprecords/ledgerbackup
claude mcp add cloudcorprecords-ledgerbackup -- docker run --rm -i ghcr.io/cloudcorprecords/ledgerbackup:0.1.0
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 container image (ghcr.io/cloudcorprecords/ledgerbackup).
Is the io.github.CloudCorpRecords/ledgerbackup MCP server safe to use?
io.github.CloudCorpRecords/ledgerbackup scores 41 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 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.