# Backroom (pypi · backroom-mcp)

Invoice extraction for agents: submit a PDF, get verified structured data — never a guess.

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

## Components

- pypi · `backroom-mcp`: 63/100 (this document), [markdown](https://verifymcp.io/servers/pardhuparimi-backroom/backroom-mcp.md), [page](https://verifymcp.io/servers/pardhuparimi-backroom/backroom-mcp)

## Channel facts

- Registry: `pypi`
- Package: `backroom-mcp`
- Version: `0.1.1`
- 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**: 50/100
  - No malware found by supply-chain analysis.
  - Known CVEs could not be checked: we could not find this package in its registry.
  - Install-script risk not yet assessed.
  - Dependency health could not be checked: we could not find this package in its registry.
- **Provenance & Transparency**: 0/100
  - Repository check failed: the declared repository URL returned HTTP 404.
  - Provenance check failed: the registry has no such package, so there's no artefact to verify.
  - License check failed: the registry has no such package, so no license can be read.
  - Maintenance check failed: the registry has no such package, so there's no release history to read.
  - Security-disclosure policy not yet verified: we couldn't inspect the source repository.
- **Schema Quality & AI Usability**: 74/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 671 tokens (~111/item across 6 items; 6 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 71/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% 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 6 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 Backroom MCP server?

Backroom runs locally as a PyPI package, launched with uvx backroom-mcp. 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 pardhuparimi-backroom -- uvx backroom-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "pardhuparimi-backroom": {
      "command": "uvx",
      "args": [
        "backroom-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "pardhuparimi-backroom": {
      "command": "uvx",
      "args": [
        "backroom-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add pardhuparimi-backroom -- uvx backroom-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "pardhuparimi-backroom": {
      "type": "local",
      "command": [
        "uvx",
        "backroom-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add pardhuparimi-backroom --command uvx --arg backroom-mcp
```

### Hermes

```yaml
mcp_servers:
  pardhuparimi-backroom:
    command: "uvx"
    args: ["backroom-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "pardhuparimi-backroom": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "backroom-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add pardhuparimi-backroom -t stdio -c uvx -a backroom-mcp
```

### Other

```json
{
  "mcpServers": {
    "pardhuparimi-backroom": {
      "command": "uvx",
      "args": [
        "backroom-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-04 (score 63, 0)

- [security regression] Known CVEs: pass → unverified
- [security regression] Install scripts: pass → unverified
- [security regression] Stability: 0.20 → unverified
- [security] Provenance: Provenance check failed: the registry has no such package, so there's no artefact to verify.
- [security] The code this package runs automatically changed: its declared build backend
- [functional regression] Dependency health: 1.00 → unverified
- [functional regression] Maintenance: pass → fail
- [functional] License: License check failed: the registry has no such package, so no license can be read.

### 2026-11-02 (score 63, +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-31 (score 62, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-29 (score 61, +1)

No change was recorded against any check on this day. Stability & Change Management went from 0 to 3. That category is still filling its 30-day observation window: 0 days of observed history at the previous scan, 1 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-28 (score 60)

First indexed and scored.

## MCP tools (6)

### `submit_invoice` (~94 tokens)

Submit an invoice PDF for extraction.

Reads the local file at pdf_path and uploads it to Backroom.
Returns the intake receipt: job_id (null when the submission was
deduplicated against an earlier identical document), invoice_id,
the deduped flag, and the caller's updated usage meter. Poll the
job with get_job, then read the result with get_proposal.

Input parameters:

- `pdf_path` (string, required)

### `submit_invoice_and_wait` (~194 tokens)

Submit an invoice PDF and wait for the job to finish.

Submits the PDF, then polls the job with backoff until it reaches
a terminal state (done or failed) or timeout_seconds elapse.
Returns {"status", "intake", "job"}: on "completed", job carries
the terminal payload — its outcome ("proposal", "needs_human",
"failed", "duplicate"), its reason_code when the job ended
without a proposal, and proposal_id when one was issued. This
tool deliberately does NOT fetch the proposal itself: proposal
fetches are exactly-once, so the fetch is left as an explicit
get_proposal call whose result the caller keeps. On "timed_out",
job holds the last seen state; keep polling with get_job.

Input parameters:

- `pdf_path` (string, required)
- `poll_interval_seconds` (number)
- `timeout_seconds` (number)

### `get_job` (~96 tokens)

Get an extraction job's state and terminal payload.

While running, returns the job's state. When done, includes the
outcome ("proposal", "needs_human", "failed", "duplicate"), the
reason_code when the job ended without a proposal (for example
NO_EXTRACTABLE_TEXT for a scan with no readable text), and the
proposal_id when a proposal was issued.

Input parameters:

- `job_id` (integer, required)

### `get_proposal` (~128 tokens)

Fetch an extraction proposal by id. FETCH EXACTLY ONCE.

WARNING: the API purges the result on the first successful fetch
(zero retention) — a second fetch of the same id returns 404.
Keep everything this call returns; you cannot fetch it again.

The proposal is returned exactly as the API serves it: every
field is an object {value, status, confidence, provenance,
reason} where status is "verified", "extracted", or "unclear".
An unclear field has a null value — it was not guessed.

Input parameters:

- `proposal_id` (integer, required)

### `get_usage` (~46 tokens)

Get the caller's usage meter for the current calendar month.

Returns documents_used, the monthly cap, remaining documents,
and the period covered, for the API key in BACKROOM_API_KEY.

### `check_health` (~40 tokens)

Check the Backroom API's health (no API key required).

Returns the service status object, including model-provider
availability, exactly as the API reports it.

## Diagnostics

Captured diagnostic sections: Provenance. The full working is on the page: https://verifymcp.io/servers/pardhuparimi-backroom/backroom-mcp#diagnostics

## Score history

- 2026-11-05: 63
- 2026-11-04: 63
- 2026-11-03: 63
- 2026-11-02: 63
- 2026-11-01: 62
- 2026-10-31: 62
- 2026-10-30: 61
- 2026-10-29: 61
- 2026-10-28: 60

## Common questions

### What is the Backroom MCP server?

Backroom is an MCP server listed in the public MCP registry as io.github.pardhuparimi/backroom. Invoice extraction for agents: submit a PDF, get verified structured data, never a guess. This page covers its PyPI package (backroom-mcp).

### Is the Backroom MCP server safe to use?

Backroom scores 63 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 Backroom MCP server expose?

Backroom exposes 6 tools: submit_invoice, submit_invoice_and_wait, get_job, get_proposal, get_usage, check_health. Their descriptions and schemas cost roughly 598 tokens of context every time the server is loaded.

### Is the Backroom MCP server still maintained?

Backroom is still listed in the MCP registry, though our most recent checks did not reach this channel. We last reached this channel on 3 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- PyPI project: https://pypi.org/project/backroom-mcp/
- Socket report: https://socket.dev/pypi/package/backroom-mcp
- Website: https://backroom-api-wmk6.onrender.com/backroom/api/docs
- Changelog RSS feed: https://verifymcp.io/servers/pardhuparimi-backroom/backroom-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/pardhuparimi-backroom/backroom-mcp.json
- HTML version of this page: https://verifymcp.io/servers/pardhuparimi-backroom/backroom-mcp