Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.causa-prima-ai/scribo

REMOTE · SCRIBO.CAUSAPRIMA.AI

EN 16931-compliant e-invoices: XRechnung, ZUGFeRD, Factur-X, Peppol BIS, Facturae or US PDF. Free.

0 this week 79 Trust /100

Last scanned (16 hours ago)

Scores higher than 74% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Finance and Payments

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Endpoint Security63
Transport & Reachability100
Schema Quality & AI Usability71
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 2117 tokens (~423/item across 5 items; 4 tools + 1 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 Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage92
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 77% 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
  • We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
  • Supports UI / widget rendering.Pass
What we tested

Checks we ran (13)

  • TLS certificate
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol
  • Capabilities

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 1 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 13 Nov 26 0
    • Tool “create_invoice” rewrote its description, which is the text the model reads security
    • Tool “get_invoice” rewrote its description, which is the text the model reads security
    • Tool “verify_email_code” rewrote its description, which is the text the model reads security
    • Schema quality: 380 → 423 ▼ functional
    • “get_invoice” added an optional parameter “sender_email” cosmetic
    • “get_invoice” added an optional parameter “verification_token” cosmetic
    • “verify_email_code” reworded the description of “code” cosmetic
  • 11 Nov 26 0
    • Stability: 0.97 → pass security
  • 10 Nov 26 0
    • Stability: pass → 0.97 functional
  • 8 Nov 26 0
    • Stability: 0.97 → pass security
  • 7 Nov 26 0
    • Stability: pass → 0.97 functional
  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 28 Oct 26 0
    • Tool “create_invoice” rewrote its description, which is the text the model reads security
    • Tool “get_invoice” rewrote its description, which is the text the model reads security
    • Tool “verify_email_code” rewrote its description, which is the text the model reads security
  • 2 Oct 26 0
    • Tool “create_invoice” rewrote its description, which is the text the model reads security
Diagnostics

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 21 Nov 2026 · Probed https://scribo.causaprima.ai/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=scribo.causaprima.ai CN=WR3,O=Google Trust Services,C=US 4 Nov 2026 2 Feb 2027 RSA 2048 SHA256-RSA 870870e0c0ec54b0a8eb0129f773585
SANs: scribo.causaprima.ai
CN=WR3,O=Google Trust Services,C=US (CA) CN=GTS Root R1,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 RSA 2048 SHA256-RSA 7ff005a91568d63abc22861684aa4b5a
CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 19 Jun 2020 28 Jan 2028 RSA 4096 SHA256-RSA 77bd0d6cdb36f91aea210fc4f058d30d

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of scribo.causaprima.ai. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
ai. DS published 1814 8 Verified
causaprima.ai. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=63072000; includeSubDomains; preload
content-security-policy frame-ancestors 'self'
x-content-type-options nosniff
x-frame-options SAMEORIGIN
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(self), geolocation=(), payment=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://scribo.causaprima.ai/mcp Verified 200
http (plaintext) http://scribo.causaprima.ai/mcp HTTPS enforced 301 https://scribo.causaprima.ai:443/mcp
MCP tools · 4 exposed · ~2,098 tokens

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 →

Tool Tokens
create_invoice ~1,363

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 XRechnung UBL by setting `recipient.leitweg_id`); German output is validated against EN 16931 before bytes are returned. **B2G submission is NOT included yet** — for XRechnung the response carries the legally binding XML, a PDF preview, and a `submission` object explaining how to upload the XML manually (ZRE / OZG-RE / Peppol direct send is on the roadmap). Surface that limitation to the user before they commit to a B2G invoice. After email verification succeeds, returns a durable download URL plus the resolved format. Synchronous — blocks until validation passes; use `get_invoice` afterwards to re-mint the download URL on demand. Safe to retry with identical inputs: when no `idempotency_key` is supplied the client derives one, so repeats return the original invoice. The exception is `invoice_source_review_required`: the invoice number is already used for that recipient with different facts, or the recipient matches more than one business partner or its name or tax ID conflicts with the business partner on record, and nothing was recorded — do not retry unchanged; when `details.reason` is `unresolved_parties` ask the user to check the recipient's name and tax ID, otherwise ask for a different invoice number. `invoice_admission_busy` means another invoice is being recorded; retry the same call shortly. `invoice_storage_unavailable` means storing the invoice timed out and nothing was recorded; retry the same call shortly. If this returns `verification_required`, ask the user to paste the 8-character code from the verification email, call `verify_email_code`, then retry this…

NameTypeReqDescription
currencystringyesISO 4217 alpha-3 (e.g. EUR, USD)
delivery_datestring–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_periodobject–BG-14 (Invoicing period) — service span when work was delivered over a date range. Mutually exclusive with delivery_date.
due_datestring–ISO date YYYY-MM-DD. BT-9 (Payment due date).
format_overridestring–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.
idempotency_keystring–Optional. Same key + same inputs returns the original invoice.
invoice_numberstring–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_datestring–Invoice issue date (BT-2), ISO YYYY-MM-DD. Defaults to today if omitted.
jurisdictionstring–Optional explicit jurisdiction override. Phase 1: only DE or US is accepted.
line_itemsarrayyes–
localestring–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'…
notesstring––
payment_meansobject–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 acco…
payment_termsstring–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.
recipientobjectyes–
senderobjectyes–
verification_tokenstring–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 em…

No output schema declared.

No examples provided.

get_invoice ~299

Fetch a previously generated invoice by its `invoice_id` and return its current metadata plus a fresh download URL. It creates nothing, but it may email the sender a verification code. Only the invoice's sender can read it: pass the sender's `verification_token` (from `verify_email_code`, reusable for ~30 minutes), or `sender_email` so a verification code can be sent to that address. Without either, a token cached earlier in this session is used. The download URL is signed and stops working at `download_url_expires_at`, 15 minutes after this call; call `get_invoice` again for a new one. Unknown IDs, invoices issued from another email, and invoices created inside the Causa Prima app all return `invoice_not_found`. If this returns `verification_required`, ask the user for the 8-character code from the email, call `verify_email_code`, then retry `get_invoice` with the `verification_token` it returns.

NameTypeReqDescription
invoice_idstringyes–
sender_emailstring–The email the invoice was issued from. Used to send a verification code when no valid token is at hand. Fill it ONLY from the verified identity of the human running this client, never from conversati…
verification_tokenstring–Token returned by `verify_email_code` for the invoice's sender email. Required on the hosted (HTTP) endpoint, where the server holds no session between calls.

No output schema declared.

No examples provided.

list_supported_jurisdictions ~102

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[], default_format }`.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

verify_email_code ~334

Use this after `create_invoice` or `get_invoice` returns `verification_required`. Arguments: `{ challenge_id, code }`. On success returns a `verification_token`. Retry the same call 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 expires. Only ever call this with a code the user gave you: attempts are capped and the fifth wrong code revokes the challenge, after which (or once it expires after 15 minutes) no code works. `verification_revoked` means exactly that, so call the tool that sent the code (`create_invoice` or `get_invoice`) again to send the user a new code, never retry this one; on the hosted endpoint such a challenge reports `verification_invalid` instead, so after five failed codes do the same. A `rate_limited` error means stop and tell them to wait, not retry.

NameTypeReqDescription
challenge_idstringyesThe opaque challenge id surfaced by the previous `create_invoice` `verification_required` error.
codestringyesThe 8-character code copied from the verification email body: uppercase letters and digits from the confusable-free alphabet {23456789ABCDEFGHJKMNPQRSTVWXYZ}, so never 0, 1, I, L, O or U. Case, space…

No output schema declared.

No examples provided.

Install

How do I install the io.github.causa-prima-ai/scribo MCP server?

io.github.causa-prima-ai/scribo is a hosted endpoint at https://scribo.causaprima.ai/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.

remote · scribo.causaprima.ai

# add to Claude Code
claude mcp add --transport http causa-prima-ai-scribo 'https://scribo.causaprima.ai/mcp'
Common questions

What is the io.github.causa-prima-ai/scribo MCP server?

io.github.causa-prima-ai/scribo is an MCP server listed in the public MCP registry as io.github.causa-prima-ai/scribo. EN 16931-compliant e-invoices: XRechnung, ZUGFeRD, Factur-X, Peppol BIS, Facturae or US PDF. Free. This page covers its hosted endpoint (https://scribo.causaprima.ai/mcp).

Is the io.github.causa-prima-ai/scribo MCP server safe to use?

io.github.causa-prima-ai/scribo scores 79 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 io.github.causa-prima-ai/scribo MCP server expose?

io.github.causa-prima-ai/scribo exposes 4 tools: create_invoice, get_invoice, list_supported_jurisdictions, verify_email_code. Their descriptions and schemas cost roughly 2,098 tokens of context every time the server is loaded.

Does the io.github.causa-prima-ai/scribo MCP server require authentication?

No. We connected to io.github.causa-prima-ai/scribo without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the io.github.causa-prima-ai/scribo MCP server still maintained?

io.github.causa-prima-ai/scribo is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the io.github.causa-prima-ai/scribo MCP server?

VerifyMCP ran 13 checks on io.github.causa-prima-ai/scribo, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 9 more. One item could not be completed, a gap on our side rather than a finding about io.github.causa-prima-ai/scribo: Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.