# io.github.CloudCorpRecords/billparse (oci · ghcr.io/cloudcorprecords/billparse)

Turn invoice PDFs, scans and photos into checked spreadsheets and structured data.

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

## Components

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

## Channel facts

- Registry: `oci`
- Package: `ghcr.io/cloudcorprecords/billparse`
- 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-21.

- **Supply Chain Security**: 0/100
  - 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.
  - Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
  - Install-script risk not yet assessed.
  - Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
- **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 10 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 76/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 638 tokens (~159/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 37/100
  - Stability observed for 11 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 4 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.

**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/billparse MCP server?

io.github.CloudCorpRecords/billparse runs locally as a container image, launched with docker run --rm -i ghcr.io/cloudcorprecords/billparse:0.1.0 mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add cloudcorprecords-billparse -- docker run --rm -i ghcr.io/cloudcorprecords/billparse:0.1.0 mcp
```

### Cursor

```json
{
  "mcpServers": {
    "cloudcorprecords-billparse": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/cloudcorprecords/billparse:0.1.0",
        "mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "cloudcorprecords-billparse": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/cloudcorprecords/billparse:0.1.0",
        "mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add cloudcorprecords-billparse -- docker run --rm -i ghcr.io/cloudcorprecords/billparse:0.1.0 mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "cloudcorprecords-billparse": {
      "type": "local",
      "command": [
        "docker",
        "run",
        "--rm",
        "-i",
        "ghcr.io/cloudcorprecords/billparse:0.1.0",
        "mcp"
      ],
      "enabled": true
    }
  }
}
```

### Hermes

```yaml
mcp_servers:
  cloudcorprecords-billparse:
    command: "docker"
    args: ["run", "--rm", "-i", "ghcr.io/cloudcorprecords/billparse:0.1.0", "mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "cloudcorprecords-billparse": {
      "Transport": "stdio",
      "Command": "docker",
      "Arguments": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/cloudcorprecords/billparse:0.1.0",
        "mcp"
      ]
    }
  }
}
```

### Other

```json
{
  "mcpServers": {
    "cloudcorprecords-billparse": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/cloudcorprecords/billparse:0.1.0",
        "mcp"
      ]
    }
  }
}
```

## 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 46, +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-19 (score 45, +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-17 (score 44, +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-14 (score 43, +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.

### 2026-11-12 (score 42, +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-10 (score 41)

First indexed and scored.

## MCP tools (4)

### `invoice_to_excel` (~184 tokens)

Invoice to Excel

Read an invoice (PDF, scan or photo) and turn it into a spreadsheet: returns the header fields, the line items and download links to an Excel (.xlsx) and a CSV file, valid for 60 minutes without signing in. Give the file as file_url, file_base64 or (ChatGPT) file. For additional outputs from the same processed invoice, use get_result with its job_id instead of submitting it again.

Input parameters:

- `file`: ChatGPT only: the attached file. Other clients use file_url or file_base64.
- `file_base64`: The invoice file's bytes, base64-encoded. Use for a local file.
- `file_name`: The file's name, e.g. invoice-1042.pdf (optional).
- `file_url`: An https link to the invoice (PDF or image) that the server can download.

### `check_invoice` (~188 tokens)

Check an invoice's math

Check whether an invoice adds up: each line's quantity times unit price, the lines against the subtotal, the tax against its printed rate, and subtotal plus tax against the total. Returns a one-line verdict and every problem found, with the invoice's own numbers. Give the file as file_url, file_base64 or (ChatGPT) file. For additional outputs from the same processed invoice, use get_result with its job_id instead of submitting it again.

Input parameters:

- `file`: ChatGPT only: the attached file. Other clients use file_url or file_base64.
- `file_base64`: The invoice file's bytes, base64-encoded. Use for a local file.
- `file_name`: The file's name, e.g. invoice-1042.pdf (optional).
- `file_url`: An https link to the invoice (PDF or image) that the server can download.

### `extract_invoice_data` (~184 tokens)

Extract invoice data

Extract an invoice's data as structured JSON: vendor and customer, invoice number and dates, PO number, currency, subtotal, discount, shipping, tax and total, tax lines, every line item, and confidence (overall and per field). Give the file as file_url, file_base64 or (ChatGPT) file. For additional outputs from the same processed invoice, use get_result with its job_id instead of submitting it again.

Input parameters:

- `file`: ChatGPT only: the attached file. Other clients use file_url or file_base64.
- `file_base64`: The invoice file's bytes, base64-encoded. Use for a local file.
- `file_name`: The file's name, e.g. invoice-1042.pdf (optional).
- `file_url`: An https link to the invoice (PDF or image) that the server can download.

### `get_result` (~82 tokens)

Get a result

Retrieve an already submitted invoice by the job_id returned by any reader, whether that reader answered processing or completed. Returns the available spreadsheet links, math check and extracted data without submitting or counting another document. Use this for additional outputs from the same invoice instead of calling another reader with the file again.

Input parameters:

- `job_id` (string, required): The job_id a previous call returned.

## Diagnostics

Captured diagnostic sections: Provenance. The full working is on the page: https://verifymcp.io/servers/cloudcorprecords-billparse/ghcr-io-cloudcorprecords-billparse#diagnostics

## Score history

- 2026-11-21: 46
- 2026-11-20: 45
- 2026-11-19: 45
- 2026-11-18: 44
- 2026-11-17: 44
- 2026-11-16: 43
- 2026-11-15: 43
- 2026-11-14: 43
- 2026-11-13: 42
- 2026-11-12: 42
- 2026-11-11: 41
- 2026-11-10: 41

## Common questions

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

io.github.CloudCorpRecords/billparse is an MCP server listed in the public MCP registry as io.github.CloudCorpRecords/billparse. Turn invoice PDFs, scans and photos into checked spreadsheets and structured data. This page covers its container image (ghcr.io/cloudcorprecords/billparse).

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

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

io.github.CloudCorpRecords/billparse exposes 4 tools: invoice_to_excel, check_invoice, extract_invoice_data, get_result. Their descriptions and schemas cost roughly 638 tokens of context every time the server is loaded.

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

io.github.CloudCorpRecords/billparse 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 licence is the io.github.CloudCorpRecords/billparse MCP server under?

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

### What did VerifyMCP test on the io.github.CloudCorpRecords/billparse MCP server?

VerifyMCP ran 12 checks on io.github.CloudCorpRecords/billparse, covering Source repository, Provenance, License, Maintenance and 8 more. 4 items could not be completed, a gap on our side rather than a finding about io.github.CloudCorpRecords/billparse: Malware scan, Known CVEs, Install scripts and Dependency health. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to a container image, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- GitHub Container Registry: https://ghcr.io/cloudcorprecords/billparse
- Repository: https://github.com/CloudCorpRecords/billparse
- Changelog RSS feed: https://verifymcp.io/servers/cloudcorprecords-billparse/ghcr-io-cloudcorprecords-billparse.xml
- Changelog JSON feed: https://verifymcp.io/servers/cloudcorprecords-billparse/ghcr-io-cloudcorprecords-billparse/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/cloudcorprecords-billparse/ghcr-io-cloudcorprecords-billparse.json
- HTML version of this page: https://verifymcp.io/servers/cloudcorprecords-billparse/ghcr-io-cloudcorprecords-billparse
