Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.CloudCorpRecords/billparse

OCI · GHCR.IO/CLOUDCORPRECORDS/BILLPARSE · 2 COMPONENTS

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

+3 this week 46 Trust /100

Last scanned (17 hours ago)

Scores higher than 50% of OCI servers

Category Documents and Files

Trust breakdown (7 categories)

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
Schema Quality & AI Usability76
  • AI-judged instruction clarity (excellent).Pass
  • 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. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management37
  • Stability observed for 11 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
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 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: 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.

What we tested

Checks we ran (12)

  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (4)

These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Malware scan in Supply Chain Security (scores 0 for this)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 in Supply Chain Security (scores 0 for this)Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
  • Install scripts in Supply Chain Security (scores 0 for this)Install-script risk not yet assessed.
  • Dependency health in Supply Chain Security (scores 0 for this)Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 21 Nov 26 +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.

  • 19 Nov 26 +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.

  • 17 Nov 26 +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.

  • 14 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.

  • 12 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.

  • 10 Nov 26 41

    First indexed and scored.

Diagnostics

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 21 Nov 2026 · Analysed oci/ghcr.io/cloudcorprecords/billparse@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 →

MCP tools · 4 exposed · ~638 tokens

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 →

Tool Tokens
check_invoice ~188

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.

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

No output schema declared.

No examples provided.

extract_invoice_data ~184

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.

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

No output schema declared.

No examples provided.

get_result ~82

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.

NameTypeReqDescription
job_idstringyesThe job_id a previous call returned.

No output schema declared.

No examples provided.

invoice_to_excel ~184

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.

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

No output schema declared.

No examples provided.

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.

oci · ghcr.io/cloudcorprecords/billparse

# add to Claude Code
claude mcp add cloudcorprecords-billparse -- docker run --rm -i ghcr.io/cloudcorprecords/billparse:0.1.0 mcp
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.