Pink Agentic AI Payments (by PinkWallet): lets Claude, ChatGPT, Cursor pay vendor invoices within company spending rules (budgets, caps, allow-lists, human approval). Sandbox preview, test money.
Scribo is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
EN 16931-compliant e-invoices: XRechnung, ZUGFeRD, Factur-X, Peppol BIS, Facturae or US PDF. Free.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http scribo-mcp https://scribo.causaprima.ai/mcp
# 2 — ask your agent for something these tools do
# create_invoice, get_invoice, list_supported_jurisdictions and 1 more
Scribo costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http scribo-mcp https://scribo.causaprima.ai/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
4 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Generate an invoice. Phase 1 supports Germany (DE) and the United States (US) only — DE emits an EN 16931-compliant XRechnung (UBL by default, CII via format_override) or ZUGFeRD COMFORT, US emits a plain PDF. Any other sender jurisdiction is rejected with unsupported_jurisdiction. The format is selected automatically from the sender's country (override with format_override, or auto-select
| Parameter | Type | Required | Notes |
|---|---|---|---|
| sender | object | yes | — |
| recipient | object | yes | — |
| line_items | array | yes | — |
| currency | string | yes | ISO 4217 alpha-3 (e.g. EUR, USD) |
| jurisdiction | string | no | Optional explicit jurisdiction override. Phase 1: only DE or US is accepted. |
| format_override | string | no | Force a specific output format. Phase 1 set: ZUGFeRD COMFORT/BASIC, XRechnung CII/UBL (Germany), or plain PDF (US). Factur-X / Facturae / Peppol BIS are Phase 2 and rejected by the server. |
| notes | string | no | — |
| invoice_number | string | no | Optional invoice number to print on the invoice (BT-1). If omitted, Scribo assigns one — never invent a value, and never state or show a fabricated invoice number to the user; when none was supplied, |
| issue_date | string | no | Invoice issue date (BT-2), ISO YYYY-MM-DD. Defaults to today if omitted. |
| due_date | string | no | ISO date YYYY-MM-DD. BT-9 (Payment due date). |
| payment_terms | string | no | BT-20 free-text payment terms (e.g. 'Net 14'). At least one of due_date or payment_terms is recommended; otherwise Scribo defaults to 'Due upon receipt' to satisfy EN 16931 BR-CO-25. |
| payment_means | object | no | BG-16 PAYMENT INSTRUCTIONS. Provide EITHER a SEPA iban OR US domestic details (account_number + routing_number) — not both account forms. An optional bic (SWIFT) may accompany either; US accou |
| delivery_date | string | no | ISO date YYYY-MM-DD. BT-72 (Actual delivery / service date). When unset, Scribo defaults to the issue date to satisfy EN 16931 / Factur-X BR-FX-EN-04. |
| delivery_period | object | no | BG-14 (Invoicing period) — service span when work was delivered over a date range. Mutually exclusive with delivery_date. |
| idempotency_key | string | no | Optional. Same key + same inputs returns the original invoice. |
| verification_token | string | no | Bearer token returned by verify_email_code. Pass it here when retrying a call that previously returned verification_required. Reusable for ~30 min across multiple invoices from the same sender ema |
| locale | string | no | BCP-47 language tag (e.g. de-DE, en-US) of THIS conversation — the language you are speaking with the user. Controls the language of the verification email, its confirmation page, and the sender's |
Fetch a previously generated invoice by its invoice_id and return its current metadata plus a freshly signed download URL. Read-only and tenant-scoped — cross-tenant lookups return 404. Use this after create_invoice to re-download bytes from a different device, or to obtain a new signed URL after the original expires.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| invoice_id | string | yes | — |
List jurisdictions Scribo can emit invoices for, with each jurisdiction's available formats and the default format applied when no override is given. Phase 1 returns Germany (DE — XRechnung / ZUGFeRD) and the United States (US — plain PDF) only. Read-only and side-effect-free; safe to call before create_invoice to confirm a country is supported. Returns an array of `{ jurisdiction, formats[], de
No parameter schema on file.
Use this after create_invoice returns verification_required. Arguments: { challenge_id, code }. On success returns a verification_token. Retry create_invoice with the same arguments plus that verification_token passed in its verification_token field. The token is reusable for ~30 min, so thread the same one into every subsequent create_invoice for the same sender email until it exp
| Parameter | Type | Required | Notes |
|---|---|---|---|
| challenge_id | string | yes | The opaque challenge id surfaced by the previous create_invoice verification_required error. |
| code | string | yes | The 6-character code copied from the verification email body. Drawn from the confusable-free alphabet {2,3,4,5,6,7,8,9}. Check the user's paste against that alphabet before calling — a malformed code |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Scribo or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither: the repository linked on this page is where this record was collected from, not a copy of what the address serves, so it is not graded in its place. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.0.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Scribo can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.