# Receipts & invoices to spreadsheet (remote · byondr.co)

Receipts and invoices to checked spreadsheet rows. Doubtful numbers are flagged.

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

## Components

- remote · `byondr.co`: 69/100 (this document), [markdown](https://verifymcp.io/servers/co-byondr-receipts/receipts-mcp.md), [page](https://verifymcp.io/servers/co-byondr-receipts/receipts-mcp)

## Channel facts

- Endpoint: `https://byondr.co/receipts/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.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-05.

- **Endpoint Security**: 66/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 57/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 954 tokens (~477/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 30/100
  - Stability observed for 9 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 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the Receipts & invoices to spreadsheet MCP server?

Receipts & invoices to spreadsheet is a hosted endpoint at https://byondr.co/receipts/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 co-byondr-receipts 'https://byondr.co/receipts/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "co-byondr-receipts": {
      "url": "https://byondr.co/receipts/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "co-byondr-receipts": {
      "type": "http",
      "url": "https://byondr.co/receipts/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.co-byondr-receipts]
url = "https://byondr.co/receipts/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "co-byondr-receipts": {
      "type": "remote",
      "url": "https://byondr.co/receipts/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add co-byondr-receipts --url 'https://byondr.co/receipts/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  co-byondr-receipts:
    url: "https://byondr.co/receipts/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "co-byondr-receipts": {
      "Transport": "http",
      "Url": "https://byondr.co/receipts/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add co-byondr-receipts -t streamable-http -u 'https://byondr.co/receipts/mcp'
```

### Other

```json
{
  "mcpServers": {
    "co-byondr-receipts": {
      "type": "http",
      "url": "https://byondr.co/receipts/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-05 (score 69, +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-03 (score 68, +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-01 (score 67, +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-10-29 (score 66, +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-10-28 (score 65, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-27 (score 65)

First indexed and scored.

## MCP tools (2)

### `extract_documents` (~718 tokens)

Read receipts and invoices (JPG, PNG, WebP, HEIC, PDF, or a zip of them; one document per file or PDF; up to 25 documents per call, 10 MB each, PDFs up to 10 pages) into checked numbers. Give each file as file_id (from create_upload), url (public https) or data_base64 (up to 2 MB inline). MCP requests are capped near 4 MB by the SDK, so keep all inline base64 in one call under about 2 MB and use create_upload for more. Returns one entry per document with vendor, date, currency, line items, subtotal, tax, total and payment method, each field marked ok, check or missing, the checks that ran, a status of ready or needs_review with review_reasons, and duplicate_of for a repeated receipt. Money is a decimal string, never a float. Each document also carries printed: its dates and currency as printed, the paths of fields whose text could not be read (printed.unreadable), the paths of fields a second read changed after a failed check (printed.second_look), and the paths of amounts printed with a dotted thousands separator on a rupiah-style receipt ("31.000") that were read as the whole number (printed.thousands; the value is already converted and the field is marked check), and the paths of amounts the model returned as JSON numbers, whose printed digits are lost (printed.number_typed; the field is marked check). Also returns 24-hour download links for the exports you ask for: csv (default), line_items_csv, quickbooks_csv (one currency; set quickbooks_currency and quickbooks_date_format, MM/DD/YYYY or DD/MM/YYYY) and file_pack (a zip of the originals renamed by date, vendor and total, plus documents.csv). Each link lists the documents left out of that file: quickbooks_csv leaves out every document with status needs_review (and ones missing a date or total), with the reason; csv, line_items_csv and file_pack keep every document. Hints: country (ISO 3166-1 alpha-2) and currency (ISO 4217) help with unclear receipts, date_order (DMY or MDY) settles dates like 03/04/2026. Show…

Input parameters:

- `country` (string): Country of the documents, ISO 3166-1 alpha-2 (for example DE)
- `currency` (string): Currency to expect when a document does not print one, ISO 4217 (for example EUR)
- `date_order` (string): How all-numeric dates such as 03/04/2026 are written: day first or month first
- `exports` (array): Files to produce, each as a 24-hour download link. Default: csv; [] writes no file
- `files` (array, required): Documents to read. Each item needs exactly one of file_id, url or data_base64
- `quickbooks_currency` (string): quickbooks_csv: the one currency the file holds (default: the most common one)
- `quickbooks_date_format` (string): quickbooks_csv: how dates are written (default MM/DD/YYYY)

Output parameters:

- `documents` (array)
- `exports` (object)
- `needs_review` (integer)
- `ready` (integer)
- `skipped` (array)

### `create_upload` (~111 tokens)

Get a one-hour signed upload URL for a document or a zip that is too large to send inline (over 2 MB; up to 100 MB here) or that already sits on disk. PUT the raw bytes to upload_url with a Content-Length header, then pass file_id to extract_documents. Free.

Input parameters:

- `bytes` (integer, required): Exact size of the file you will upload, in bytes (at most 100 MB)
- `filename` (string): Original file name, used to name the documents

Output parameters:

- `expires_at` (string)
- `file_id` (string)
- `max_bytes` (integer)
- `method` (string)
- `upload_url` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/co-byondr-receipts/receipts-mcp#diagnostics

## Score history

- 2026-11-05: 69
- 2026-11-04: 68
- 2026-11-03: 68
- 2026-11-02: 67
- 2026-11-01: 67
- 2026-10-31: 66
- 2026-10-30: 66
- 2026-10-29: 66
- 2026-10-28: 65
- 2026-10-27: 65

## Common questions

### What is the Receipts & invoices to spreadsheet MCP server?

Receipts & invoices to spreadsheet is an MCP server listed in the public MCP registry as co.byondr/receipts. Receipts and invoices to checked spreadsheet rows. Doubtful numbers are flagged. This page covers its hosted endpoint (https://byondr.co/receipts/mcp).

### Is the Receipts & invoices to spreadsheet MCP server safe to use?

Receipts & invoices to spreadsheet scores 69 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 Receipts & invoices to spreadsheet MCP server expose?

Receipts & invoices to spreadsheet exposes 2 tools: extract_documents, create_upload. Their descriptions and schemas cost roughly 829 tokens of context every time the server is loaded.

### Does the Receipts & invoices to spreadsheet MCP server require authentication?

No. We connected to Receipts & invoices to spreadsheet without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Receipts & invoices to spreadsheet MCP server still maintained?

Receipts & invoices to spreadsheet 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.

## Links

- Remote endpoint: https://byondr.co/receipts/mcp
- Website: https://byondr.co/receipts
- Changelog RSS feed: https://verifymcp.io/servers/co-byondr-receipts/receipts-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/co-byondr-receipts/receipts-mcp.json
- HTML version of this page: https://verifymcp.io/servers/co-byondr-receipts/receipts-mcp