# Oblio (npm · @foreverworks/mcp-oblio)

Issue and track a Romanian company's invoices on Oblio, with totals computed as ANAF checks them.

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

## Components

- npm · `@foreverworks/mcp-oblio`: 83/100 (this document), [markdown](https://verifymcp.io/servers/com-foreverworks-oblio/foreverworks-mcp-oblio.md), [page](https://verifymcp.io/servers/com-foreverworks-oblio/foreverworks-mcp-oblio)

## Channel facts

- Registry: `npm`
- Package: `@foreverworks/mcp-oblio`
- 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**: 99/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 7 of 23 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 100/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to foreverworks/mcps).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 4 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 62/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 3773 tokens (~221/item across 17 items; 17 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 33/100
  - Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 98/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 94% 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.
  - All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 18 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 Oblio MCP server?

Oblio runs locally as an npm package, launched with npx -y @foreverworks/mcp-oblio. 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 com-foreverworks-oblio -- npx -y @foreverworks/mcp-oblio
```

### Cursor

```json
{
  "mcpServers": {
    "com-foreverworks-oblio": {
      "command": "npx",
      "args": [
        "-y",
        "@foreverworks/mcp-oblio"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-foreverworks-oblio": {
      "command": "npx",
      "args": [
        "-y",
        "@foreverworks/mcp-oblio"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add com-foreverworks-oblio -- npx -y @foreverworks/mcp-oblio
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-foreverworks-oblio": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@foreverworks/mcp-oblio"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-foreverworks-oblio --command npx --arg -y --arg @foreverworks/mcp-oblio
```

### Hermes

```yaml
mcp_servers:
  com-foreverworks-oblio:
    command: "npx"
    args: ["-y", "@foreverworks/mcp-oblio"]
```

### Netclaw

```json
{
  "McpServers": {
    "com-foreverworks-oblio": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@foreverworks/mcp-oblio"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-foreverworks-oblio -t stdio -c npx -a -y @foreverworks/mcp-oblio
```

### Other

```json
{
  "mcpServers": {
    "com-foreverworks-oblio": {
      "command": "npx",
      "args": [
        "-y",
        "@foreverworks/mcp-oblio"
      ]
    }
  }
}
```

## 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 83, +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-01 (score 82, +16)

- [security improvement] Malware scan: unverified → pass

### 2026-10-31 (score 66, −15)

- [security regression] Malware scan: pass → unverified
- [functional] Package version: 0.1.0 → 0.1.1

### 2026-10-30 (score 81, +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-10-28 (score 80, +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-26 (score 79)

First indexed and scored.

## MCP tools (17)

### `cancel_invoice` (~175 tokens)

Cancel an invoice

Mark an invoice cancelled. Reversible with restore_invoice, and the number stays in the series, which is what a tax authority expects of an issued document. Prefer this over delete_invoice. The invoice is read first: the answer says what it totalled (before), and with expect_total a call whose number names an invoice of another total changes nothing. Moves money or makes a legal document: the client asks the user to approve each call.

Input parameters:

- `expect_total` (string): The total the invoice must have ("121.00"); when it differs nothing is changed. Recommended: a number can name the wrong invoice.
- `number` (string, required): The document number as text, without its series: "0042" is not 42.
- `series_name` (string, required): The document's series, exactly as list_series shows it.

### `collect_invoice` (~395 tokens)

Record a payment on an invoice

Record a payment received against an issued invoice: how it was paid, the amount in the invoice's currency (a decimal STRING), the day, and the payment's own reference. The invoice is read first: a cancelled one, one paid in full, or an amount over what it still owes is refused with nothing recorded, and a payment already on it with the same type, reference, amount and date is not recorded again (the answer says alreadyRecorded). The answer carries the balance before and after. list_invoices with status unpaid finds what is owed. Moves money or makes a legal document: the client asks the user to approve each call.

Input parameters:

- `amount` (string, required): The amount paid, in the invoice's currency, as a decimal STRING ("1210.00"), at most two decimals and at most what the invoice still owes.
- `date` (string, required): The day it was paid, YYYY-MM-DD.
- `document_number` (string): The payment's own reference ("OP 7001"), required for every type but Chitanta.
- `idempotency_key` (string): Leave it out: a retry with the same arguments then finds the payment if it landed and records nothing. Give a key of your own only to record a second payment identical in type, reference, amount and…
- `mentions` (string)
- `number` (string, required): The document number as text, without its series: "0042" is not 42.
- `receipt_series` (string): For a Chitanta: the receipt series from list_series. Oblio numbers the receipt.
- `series_name` (string, required): The document's series, exactly as list_series shows it.
- `type` (string, required): How it was paid, in Oblio's words: "Ordin de plata" for a bank transfer, "Card", "Chitanta" for cash with a receipt, and so on.

### `create_invoice` (~541 tokens)

Issue an invoice

Issue a new invoice. A real fiscal document: it takes the next number in the series, and in Romania it is what gets reported to ANAF. Prices, quantities and rates are decimal STRINGS. Every line states vat_included. The buyer's CIF or CNP and IBAN are checked by their control digits. The company is the one in app.json; the input has no field for it. The answer carries computedTotal (exact, EN 16931 rounding), oblioTotal (the document read back, which must match) and the idempotency_key it was sent with. Moves money or makes a legal document: the client asks the user to approve each call.

Input parameters:

- `client` (object, required): The buyer.
- `collect` (object): Issue the invoice already paid.
- `collect_date` (string): Collection date, YYYY-MM-DD.
- `contract_number` (string): The contract reference, BT-12 on the e-Factura.
- `currency` (string)
- `delivery_date` (string): Delivery date, YYYY-MM-DD.
- `due_date` (string): Due date, YYYY-MM-DD.
- `exchange_rate` (string): Oblio's default: the rate in the company settings.
- `idempotency_key` (string): Oblio refuses a second document with the same key. Leave it out: the key is then derived from the document's content and issue date, so an identical retry cannot issue twice. Give one only to issue a…
- `internal_note` (string): Not shown to the client.
- `issue_date` (string): YYYY-MM-DD. Oblio's default: today.
- `issuer_name` (string): Intocmit de.
- `language` (string): Two letters; Oblio's default: "RO".
- `mentions` (string): Printed on the document.
- `order_number` (string): The buyer's order reference, BT-13 on the e-Factura.
- `precision` (integer): Decimals kept on prices, 2 to 4.
- `products` (array, required)
- `send_email` (boolean): Oblio emails the document to the client (client.email, else the one saved in Oblio); the answer's emailedTo says where. Default: no.
- `series_name` (string, required): A series from list_series, of the document's type.
- `use_stock` (boolean): Take the goods out of stock, with stock enabled.
- `work_station` (string): Oblio's default: "Sediu".

### `create_proforma` (~455 tokens)

Issue a proforma

Issue a new proforma, which is not a fiscal document but takes a number in its series. Prices, quantities and rates are decimal STRINGS. Every line states vat_included. The buyer's CIF or CNP and IBAN are checked by their control digits. The company is the one in app.json; the input has no field for it. The answer carries computedTotal (exact, EN 16931 rounding), oblioTotal (the document read back, which must match) and the idempotency_key it was sent with.

Input parameters:

- `client` (object, required): The buyer.
- `contract_number` (string): The contract reference, BT-12 on the e-Factura.
- `currency` (string)
- `due_date` (string): Due date, YYYY-MM-DD.
- `exchange_rate` (string): Oblio's default: the rate in the company settings.
- `idempotency_key` (string): Oblio refuses a second document with the same key. Leave it out: the key is then derived from the document's content and issue date, so an identical retry cannot issue twice. Give one only to issue a…
- `internal_note` (string): Not shown to the client.
- `issue_date` (string): YYYY-MM-DD. Oblio's default: today.
- `issuer_name` (string): Intocmit de.
- `language` (string): Two letters; Oblio's default: "RO".
- `mentions` (string): Printed on the document.
- `order_number` (string): The buyer's order reference, BT-13 on the e-Factura.
- `precision` (integer): Decimals kept on prices, 2 to 4.
- `products` (array, required)
- `send_email` (boolean): Oblio emails the document to the client (client.email, else the one saved in Oblio); the answer's emailedTo says where. Default: no.
- `series_name` (string, required): A series from list_series, of the document's type.
- `work_station` (string): Oblio's default: "Sediu".

### `delete_invoice` (~194 tokens)

Delete an invoice permanently

Remove an invoice from Oblio for good. NO INVERSE. Oblio allows it only for the last number in a series, and anything already sent to ANAF stays there, so the two can end up out of step. cancel_invoice is almost always the right call instead. The invoice is read first: the answer says what it totalled (before), and with expect_total a call whose number names an invoice of another total changes nothing. Moves money or makes a legal document: the client asks the user to approve each call.

Input parameters:

- `expect_total` (string): The total the invoice must have ("121.00"); when it differs nothing is changed. Recommended: a number can name the wrong invoice.
- `number` (string, required): The document number as text, without its series: "0042" is not 42.
- `series_name` (string, required): The document's series, exactly as list_series shows it.

### `get_invoice` (~75 tokens)

Get an invoice

One invoice by series and number: its PDF and e-Factura links, and the payments recorded against it.

Input parameters:

- `number` (string, required): The document number as text, without its series: "0042" is not 42.
- `series_name` (string, required): The document's series, exactly as list_series shows it.

### `get_proforma` (~61 tokens)

Get a proforma

One proforma by series and number.

Input parameters:

- `number` (string, required): The document number as text, without its series: "0042" is not 42.
- `series_name` (string, required): The document's series, exactly as list_series shows it.

### `health` (~67 tokens)

Health

Check that the integration is alive and say so in detail: the Oblio account, the company CIF every call acts on, whether that CIF is one this account can actually reach, and the companies it can. Always asks Oblio, never the cache. Run this before concluding the MCP is broken.

### `invoice_from_proforma` (~226 tokens)

Invoice an existing proforma

Issue an invoice that references an existing proforma, so the two are linked in Oblio. Client, lines and total are the proforma's; nothing is retyped. The proforma is read first and returned as fromProforma, and the new invoice's total is held to it. Moves money or makes a legal document: the client asks the user to approve each call.

Input parameters:

- `idempotency_key` (string): Oblio refuses a second document with the same key. Leave it out: the key is then derived from the document's content and issue date, so an identical retry cannot issue twice. Give one only to issue a…
- `invoice_series` (string, required): The INVOICE series to issue into, from list_series.
- `proforma_number` (string, required): The document number as text, without its series: "0042" is not 42.
- `proforma_series` (string, required): The document's series, exactly as list_series shows it.

### `list_clients` (~95 tokens)

List clients

The company's saved clients, optionally filtered by name or by the client's own CIF. Never cached.

Input parameters:

- `client_cif` (string): The client's CIF.
- `limit` (integer): Return at most this many rows of the page.
- `name` (string): Part of the client's name.
- `offset` (integer): Oblio answers 250 rows a page; pass the nextOffset a full page reports to read the next.

### `list_companies` (~64 tokens)

List companies

The companies this Oblio account is attached to. Only the one whose CIF is in app.json is acted on; this is how you check that the right one is configured. Remembered for 10 minutes; `asOf` says when it was read from Oblio.

### `list_invoices` (~430 tokens)

List issued invoices

The company's issued invoices, newest first, filtered by issue date, series, buyer (CIF, e-mail or code; list_clients finds them by name), status ("unpaid", "paid", "cancelled") and e-Factura state. Each row: series and number, dates, currency, total with VAT as Oblio wrote it, whether it is cancelled, the buyer, the payments recorded against it, its e-Factura state and its PDF link. Drafts are never listed. Pass nextCursor back, with the same filters, for the next page; get_invoice reads one invoice.

Input parameters:

- `client_cif` (string): The buyer's CIF as it is saved in Oblio (list_clients shows it).
- `client_code` (string): The buyer's code in Oblio's client list.
- `client_email` (string): The buyer's e-mail as it is saved in Oblio.
- `cursor` (string): The nextCursor of the previous page, with the same filters. Leave it out for the first page.
- `efactura` (array): Only invoices in these e-Factura states: "not_sent", "processing" (in SPV, not yet answered), "sent", "errors" (not sent because of errors). Checked page by page after Oblio answers; scanned says how…
- `issued_after` (string): Start of the period, YYYY-MM-DD (Oblio's issuedAfter, its start date).
- `issued_before` (string): End of the period, YYYY-MM-DD (Oblio's issuedBefore, its end date).
- `limit` (integer): Invoices read per page, at most 100.
- `order` (string): By the order Oblio created the documents in. Default: newest first.
- `series_name` (string): The invoice series, exactly as list_series shows it.
- `status` (string): "unpaid" or "paid" (collected in Oblio), both without cancelled invoices, or "cancelled". Leave it out for all.

### `list_products` (~93 tokens)

List products

The company's saved products and services, optionally filtered by name or code. Never cached.

Input parameters:

- `code` (string): The product's code.
- `limit` (integer): Return at most this many rows of the page.
- `name` (string): Part of the product's name.
- `offset` (integer): Oblio answers 250 rows a page; pass the nextOffset a full page reports to read the next.

### `list_series` (~63 tokens)

List document series

The document series configured for the company, with the number each will issue next. Every issuing tool needs one of these names. Forgotten after any document this server issues or deletes. Remembered for 10 minutes; `asOf` says when it was read from Oblio.

### `list_vat_rates` (~50 tokens)

List VAT rates

The VAT rates available to the company: a line's vat_name and vat_percentage come from here. Remembered for 10 minutes; `asOf` says when it was read from Oblio.

### `restore_invoice` (~142 tokens)

Restore a cancelled invoice

Undo cancel_invoice. The invoice is read first: the answer says what it totalled (before), and with expect_total a call whose number names an invoice of another total changes nothing. Moves money or makes a legal document: the client asks the user to approve each call.

Input parameters:

- `expect_total` (string): The total the invoice must have ("121.00"); when it differs nothing is changed. Recommended: a number can name the wrong invoice.
- `number` (string, required): The document number as text, without its series: "0042" is not 42.
- `series_name` (string, required): The document's series, exactly as list_series shows it.

### `reverse_invoice` (~359 tokens)

Reverse an invoice (storno)

Issue a reversing invoice (storno) for an issued invoice, through Oblio's reference flow: a new invoice that references it, every line negated, its total exactly the reversed invoice's total negated. A real fiscal document, reported to ANAF like any invoice; the reversed invoice stays issued. Use it for an invoice already sent to the client or to ANAF; cancel_invoice is for one nobody has received. The invoice is read first: a cancelled one, or one that is itself a reversal, is refused. The answer carries computedTotal and oblioTotal (the storno read back, which must match) and the idempotency_key it was sent with. Moves money or makes a legal document: the client asks the user to approve each call.

Input parameters:

- `expect_total` (string): The total the invoice must have ("121.00"); when it differs nothing is changed. Recommended: a number can name the wrong invoice.
- `idempotency_key` (string): Leave it out: the key is derived from the invoice being reversed, so no retry can reverse it twice. Give one only to reverse the same invoice again on purpose, after the first reversal was cancelled.
- `number` (string, required): The document number as text, without its series: "0042" is not 42.
- `remove_payments` (boolean): Remove the payments recorded on the reversed invoice (Oblio's refund). Default: keep them, as when the money is refunded separately.
- `series_name` (string, required): The document's series, exactly as list_series shows it.
- `storno_series` (string): The invoice series the reversing invoice is issued in, from list_series. Default: the reversed invoice's own series.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/com-foreverworks-oblio/foreverworks-mcp-oblio#diagnostics

## Score history

- 2026-11-05: 83
- 2026-11-04: 83
- 2026-11-03: 82
- 2026-11-02: 82
- 2026-11-01: 82
- 2026-10-31: 66
- 2026-10-30: 81
- 2026-10-29: 80
- 2026-10-28: 80
- 2026-10-27: 79
- 2026-10-26: 79

## Common questions

### What is the Oblio MCP server?

Oblio is an MCP server listed in the public MCP registry as com.foreverworks/oblio. Issue and track a Romanian company's invoices on Oblio, with totals computed as ANAF checks them. This page covers its npm package (@foreverworks/mcp-oblio).

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

Oblio scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Oblio MCP server expose?

Oblio exposes 17 tools: cancel_invoice, collect_invoice, create_invoice, create_proforma, delete_invoice, and 12 more. Their descriptions and schemas cost roughly 3,485 tokens of context every time the server is loaded.

### Is the Oblio MCP server still maintained?

Oblio 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 Oblio MCP server under?

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

## Links

- npm package: https://www.npmjs.com/package/@foreverworks/mcp-oblio
- Socket report: https://socket.dev/npm/package/@foreverworks/mcp-oblio
- Repository: https://github.com/foreverworks/mcps
- Website: https://foreverworks.github.io/mcps/servers/oblio/
- Changelog RSS feed: https://verifymcp.io/servers/com-foreverworks-oblio/foreverworks-mcp-oblio.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-foreverworks-oblio/foreverworks-mcp-oblio.json
- HTML version of this page: https://verifymcp.io/servers/com-foreverworks-oblio/foreverworks-mcp-oblio