Oblio
NPM · @FOREVERWORKS/MCP-OBLIO
Issue and track a Romanian company's invoices on Oblio, with totals computed as ANAF checks them.
Available components
Last scanned (8 hours ago)
Scores higher than 76% of npm servers
Category Finance and Payments
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 Security99
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 7 of 23 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to foreverworks/mcps). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 4 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability62
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management33
- Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage98
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 94% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 18 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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.
- 4 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.
- 1 Nov 26 +16
- Malware scan: unverified → pass ▲ security
- 31 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- Package version: 0.1.0 → 0.1.1 functional
- 30 Oct 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.
- 28 Oct 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.
- 26 Oct 26 79
First indexed and scored.
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 5 Nov 2026 · Analysed npm/@foreverworks/mcp-oblio@0.1.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | foreverworks/mcps |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/foreverworks/mcps/.github/workflows/release.yml@refs/tags/release-2026-10-31 |
| Rekor log index | 3614033860 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:9545d33193b117ee3cf5bd1eb720fed9b34436ab601abc154dfe15136710efa9ebfc72329af82f9a0904ee17f00d449e95ad5a6669372f8c6aee11285 |
Background: How many MCP packages publish verified provenance →
Dependencies 23 packages
| Packages resolved | 23 |
|---|---|
| Stale | 7 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
cancel_invoice Cancel an invoice ~175
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | The document number as text, without its series: "0042" is not 42. |
| series_name | string | yes | The document's series, exactly as list_series shows it. |
No output schema declared.
No examples provided.
collect_invoice Record a payment on an invoice ~395
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.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | string | yes | 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 | yes | 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 | yes | 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 | yes | The document's series, exactly as list_series shows it. |
| type | string | yes | 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. |
No output schema declared.
No examples provided.
create_invoice Issue an invoice ~541
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.
| Name | Type | Req | Description |
|---|---|---|---|
| client | object | yes | 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 | yes | – |
| 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 | yes | 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". |
No output schema declared.
No examples provided.
create_proforma Issue a proforma ~455
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.
| Name | Type | Req | Description |
|---|---|---|---|
| client | object | yes | 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 | yes | – |
| 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 | yes | A series from list_series, of the document's type. |
| work_station | string | – | Oblio's default: "Sediu". |
No output schema declared.
No examples provided.
delete_invoice Delete an invoice permanently ~194
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | The document number as text, without its series: "0042" is not 42. |
| series_name | string | yes | The document's series, exactly as list_series shows it. |
No output schema declared.
No examples provided.
get_invoice Get an invoice ~75
One invoice by series and number: its PDF and e-Factura links, and the payments recorded against it.
| Name | Type | Req | Description |
|---|---|---|---|
| number | string | yes | The document number as text, without its series: "0042" is not 42. |
| series_name | string | yes | The document's series, exactly as list_series shows it. |
No output schema declared.
No examples provided.
get_proforma Get a proforma ~61
One proforma by series and number.
| Name | Type | Req | Description |
|---|---|---|---|
| number | string | yes | The document number as text, without its series: "0042" is not 42. |
| series_name | string | yes | The document's series, exactly as list_series shows it. |
No output schema declared.
No examples provided.
health Health ~67
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
invoice_from_proforma Invoice an existing proforma ~226
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | The INVOICE series to issue into, from list_series. |
| proforma_number | string | yes | The document number as text, without its series: "0042" is not 42. |
| proforma_series | string | yes | The document's series, exactly as list_series shows it. |
No output schema declared.
No examples provided.
list_clients List clients ~95
The company's saved clients, optionally filtered by name or by the client's own CIF. Never cached.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
list_companies List companies ~64
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_invoices List issued invoices ~430
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
list_products List products ~93
The company's saved products and services, optionally filtered by name or code. Never cached.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
list_series List document series ~63
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_vat_rates List VAT rates ~50
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
restore_invoice Restore a cancelled invoice ~142
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | The document number as text, without its series: "0042" is not 42. |
| series_name | string | yes | The document's series, exactly as list_series shows it. |
No output schema declared.
No examples provided.
reverse_invoice Reverse an invoice (storno) ~359
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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 | yes | 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. |
No output schema declared.
No examples provided.
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.
npm · @foreverworks/mcp-oblio
claude mcp add com-foreverworks-oblio -- npx -y @foreverworks/mcp-oblio
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.