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.

Papierkram MCP by usefulapi

REMOTE · PAPIERKRAM.USEFULAPI.IO

Read Papierkram invoices, vouchers, contacts, projects, time; create contacts, time, draft invoices.

−46 this week 18 Trust /100

Last scanned (7 hours ago)

Scores higher than 4% of remote servers

Reachable. Last reached 5 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 Security46
Transport & Reachability0
Schema Quality & AI Usability0
  • Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
  • Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
  • Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
  • Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified

Unverified: 5 categories

Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

What we tested

Checks we ran (4)

  • TLS certificate
  • HSTS header
  • DNSSEC
  • Transport

Checks we could not complete (7)

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 yet verified: we couldn't confirm whether this endpoint requires it.
  • HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven.
  • Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
  • Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
  • Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
  • Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
  • Capabilities in Capabilities (scores 0 for this)Capabilities not yet verified: we couldn't read the endpoint's capabilities.

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.

  • 2 Nov 26 −50
    • Endpoint reachability: reachable → not serving MCP ▼ security
    • Stability: 0.23 → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Authorization: pass → unverified ▼ security
    • Schema quality: 100 → unverified ▼ functional
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
  • 1 Nov 26 +1

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

  • 31 Oct 26 +3
    • Authorization: partial → pass ▲ security
    • New tool “papierkram_update_voucher”, which the server declares destructive security
    • New tool “papierkram_pay_voucher”, which the server declares destructive security
    • Schema quality: 130 → 148 ▼ functional
    • Schema quality: 4297 → 5347 ▼ functional
    • MCP protocol: fail → pass ▲ functional
    • Destructive annotations: pass → 100 functional
    • New prompt “check_bank_connections_and_transactions” functional
    • New prompt “check_tracked_hours_on_a_project” functional
    • New prompt “create_a_project_and_task_then_record_time” functional
    • New prompt “prepare_a_draft_invoice_or_add_a_contact” functional
    • New prompt “review_expense_vouchers_of_a_supplier” functional
    • New prompt “see_which_invoices_are_still_unpaid” functional
    • MCP protocol version: 2025-06-18 → 2025-11-25 functional
    • Server version: 1.11.0 → 1.13.0 functional
    • Server version: 1.10.0 → 1.11.0 functional
    • Server version: 1.9.0 → 1.10.0 functional
    • Server version: 1.7.2 → 1.9.0 functional
    • New tool “papierkram_create_voucher” functional
    • New tool “papierkram_get_voucher_document” functional
    • New tool “papierkram_get_voucher_pdf” functional
    • New tool “papierkram_upload_voucher_document” functional
  • 30 Oct 26 0
    • Server version: 1.7.1 → 1.7.2 functional
    • Server version: 1.7.0 → 1.7.1 functional
  • 29 Oct 26 +1
    • Server version: 1.6.0 → 1.7.0 functional
    • Server version: 1.5.0 → 1.6.0 functional
  • 28 Oct 26 0
    • Server version: 1.3.0 → 1.5.0 functional
  • 27 Oct 26 +1
    • Server version: 1.2.0 → 1.3.0 functional
  • 26 Oct 26 0
    • Stability: unverified → 0.03 ▲ functional
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 5 Nov 2026 · Probed https://papierkram.usefulapi.io/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=usefulapi.io CN=WE1,O=Google Trust Services,C=US 13 Sept 2026 12 Dec 2026 ECDSA 256 ECDSA-SHA256 d9be3287b0fde9630e825ba1f79bff3f
SANs: usefulapi.io, *.usefulapi.io
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of papierkram.usefulapi.io. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
io. DS published 38690 8 Verified
usefulapi.io. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Inconclusive

We could not reach the endpoint well enough to judge its authorisation posture.

Result Inconclusive
HTTP status 302

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://papierkram.usefulapi.io/mcp Redirected 302 https://usefulapi.io/papierkram/
http (plaintext) http://papierkram.usefulapi.io/mcp Inconclusive 302 http://papierkram.usefulapi.io/mcp
MCP tools · 39 exposed · ~5,515 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
papierkram_create_company ~244

WRITE: create a contact (company) in Papierkram. Papierkram assigns the customer number. Nothing is sent to the contact. Check papierkram_list_companies first to avoid duplicates. Costs Papierkram API credits (a create 10, an invoice 50; the monthly quota is limited).

NameTypeReqDescription
bank_bicstring–BIC.
bank_ibanstring–IBAN.
contact_typestringyescustomer or supplier (required).
delivery_methodstring–How documents are delivered to this contact.
emailstring–E-mail address.
namestringyesCompany name.
notesstring–Internal notes.
phonestring–Phone.
postal_citystring–Postal address: city.
postal_countrystring–Postal address: country.
postal_streetstring–Postal address: street and number.
postal_zipstring–Postal address: ZIP.
ust_idnrstring–VAT id (USt-IdNr.), e.g. DE123456789.
websitestring–Website.

No output schema declared.

No examples provided.

papierkram_create_invoice ~290

WRITE: create a DRAFT outgoing invoice (state draft; it is NOT finalized or sent, and gets no invoice number until the user completes it in Papierkram). Needs a payment term id (papierkram_list_payment_terms) and at least one line item. Use papierkram_list_invoices afterwards to check it. Costs Papierkram API credits (a create 10, an invoice 50; the monthly quota is limited).

NameTypeReqDescription
contact_person_id––Contact person of the customer (from papierkram_list_persons).
custom_template_id––Custom invoice template id (from papierkram_get_info).
customer_id–yesCompany id of the customer (from papierkram_list_companies).
descriptionstring–Notes shown on the invoice.
document_datestring–Invoice date yyyy-mm-dd (default today).
grossboolean–False (default): prices are net. True: prices are gross.
line_itemsarrayyesThe invoice lines.
namestringyesInvoice title/subject.
payment_term_id–yesPayment term id (from papierkram_list_payment_terms).
project_id––Project the invoice belongs to.
supply_datestring–Supply/service date or period as text, e.g. 01.10.2026 - 14.10.2026.

No output schema declared.

No examples provided.

papierkram_create_person ~148

WRITE: add a contact person to an existing company. Nothing is sent to the person. Costs Papierkram API credits (a create 10, an invoice 50; the monthly quota is limited).

NameTypeReqDescription
commentstring–Comment.
company_id–yesCompany id.
departmentstring–Department.
emailstring–E-mail address.
first_namestringyesFirst name.
last_namestringyesLast name.
mobilestring–Mobile phone.
phonestring–Phone.
positionstring–Position.
salutationstring–Salutation, e.g. Herr or Frau.

No output schema declared.

No examples provided.

papierkram_create_project ~169

WRITE: create a project for a customer. Costs Papierkram API credits (a create 10, an invoice 50; the monthly quota is limited).

NameTypeReqDescription
budget_moneystring–Money budget, e.g. 5000.00.
budget_timestring–Time budget in budget_time_unit.
budget_time_unitstring–Unit of budget_time.
budget_typestring–Budget kind; then pass budget_money or budget_time.
customer_id–yesCompany id of the customer (from papierkram_list_companies).
descriptionstring–Description.
end_datestring–End date yyyy-mm-dd.
namestringyesProject name.
start_datestring–Start date yyyy-mm-dd.

No output schema declared.

No examples provided.

papierkram_create_proposition ~201

WRITE: create a stored product or service (Leistung/Artikel) with a price. Costs Papierkram API credits (a create 10, an invoice 50; the monthly quota is limited).

NameTypeReqDescription
article_nostringyesArticle number.
descriptionstring–Description.
namestringyesName.
pricestring–Net unit price, e.g. 99.50.
proposition_typestringyesservice, product or ecommerce.
time_unitstringyesTime unit used for time tracking with this item.
unit_name_1string–Unit name singular, e.g. Stunde.
unit_name_nstring–Unit name plural, e.g. Stunden.
vat_ratestringyesVAT rate as Papierkram writes it, e.g. 19% (see vat_rate.name of an existing item from papierkram_get_proposition).

No output schema declared.

No examples provided.

papierkram_create_task ~121

WRITE: create a time-tracking task in a project. Costs Papierkram API credits (a create 10, an invoice 50; the monthly quota is limited).

NameTypeReqDescription
deadlinestring–Deadline yyyy-mm-dd.
namestringyesTask name.
project_id–yesProject id (from papierkram_list_projects).
proposition_id––Product/service id the time is billed with (from papierkram_list_propositions).
user_id––User assigned to the task (from papierkram_list_users).

No output schema declared.

No examples provided.

papierkram_create_time_entry ~159

WRITE: record a time entry (worked time) on a task. Not billed until an invoice is made. Costs Papierkram API credits (a create 10, an invoice 50; the monthly quota is limited).

NameTypeReqDescription
commentsstring–What was done.
ended_at_timestringyesEnd time HH:MM.
entry_datestringyesDay of the work, yyyy-mm-dd.
started_at_timestringyesStart time HH:MM.
task_id–yesTask id (from papierkram_list_tasks).
unbillableboolean–True when the time must not be billed.
user_id–yesUser who worked (from papierkram_list_users).

No output schema declared.

No examples provided.

papierkram_create_voucher ~370

WRITE: book an expense voucher (Beleg) in Papierkram, e.g. from a receipt. Papierkram books it at once (state unpaid, no draft), so this tool works in two steps. Without confirm it creates nothing: it returns the exact request and possible duplicates (same document date, creditor and total) for the user to review. After the user approves, call again with the same arguments and confirm: true. Then attach the file with papierkram_upload_voucher_document and record a payment with papierkram_pay_voucher. Asset categories that need a depreciation (AfA) setting must be finished in Papierkram. Costs 50 Papierkram API credits; each duplicate check reads 1.

NameTypeReqDescription
allow_duplicateboolean–True only after the user confirmed that a reported possible duplicate is a different voucher.
confirmboolean–False or missing: preview only, nothing is created. True: book the voucher now.
creditor_id––Supplier company id (from papierkram_list_companies; it must be a supplier).
descriptionstring–Notes.
document_datestringyesReceipt date yyyy-mm-dd (Belegdatum).
due_datestring–Due date yyyy-mm-dd.
entertainment_personsarray–Guests of a business meal (Bewirtungskosten only).
entertainment_reasonstring–Reason of a business meal (Bewirtungskosten only).
flaggedboolean–Mark the voucher for a later check.
line_itemsarrayyesThe voucher lines.
namestringyesVoucher title, e.g. the supplier and the receipt number.
provenancestringyesWhere the supplier is: domestic (Germany), eu or foreign.

No output schema declared.

No examples provided.

papierkram_get_bank_transaction ~34

Get one bank transaction by id.

NameTypeReqDescription
id–yesTransaction id (from papierkram_list_bank_transactions).

No output schema declared.

No examples provided.

papierkram_get_company ~39

Get one contact (company) by id, with its people.

NameTypeReqDescription
id–yesCompany id (from papierkram_list_companies).

No output schema declared.

No examples provided.

papierkram_get_estimate ~35

Get one estimate with its line items.

NameTypeReqDescription
id–yesEstimate id (from papierkram_list_estimates).

No output schema declared.

No examples provided.

papierkram_get_info ~34

Read the API version and the account's custom invoice templates (ids usable as custom_template_id when creating an invoice).

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

papierkram_get_invoice ~41

Get one outgoing invoice with its line items, billing address and payment term.

NameTypeReqDescription
id–yesInvoice id (from papierkram_list_invoices).

No output schema declared.

No examples provided.

papierkram_get_person ~42

Get one contact person of a company.

NameTypeReqDescription
company_id–yesCompany id.
id–yesPerson id (from papierkram_list_persons).

No output schema declared.

No examples provided.

papierkram_get_project ~31

Get one project by id.

NameTypeReqDescription
id–yesProject id (from papierkram_list_projects).

No output schema declared.

No examples provided.

papierkram_get_proposition ~54

Get one stored product or service, including its vat_rate (name such as 19% and rate such as 0.19).

NameTypeReqDescription
id–yesProposition id (from papierkram_list_propositions).

No output schema declared.

No examples provided.

papierkram_get_task ~31

Get one task by id.

NameTypeReqDescription
id–yesTask id (from papierkram_list_tasks).

No output schema declared.

No examples provided.

papierkram_get_time_entry ~35

Get one time entry by id.

NameTypeReqDescription
id–yesTime entry id (from papierkram_list_time_entries).

No output schema declared.

No examples provided.

papierkram_get_user ~31

Get one user by id.

NameTypeReqDescription
id–yesUser id (from papierkram_list_users).

No output schema declared.

No examples provided.

papierkram_get_voucher ~36

Get one expense voucher with its line items.

NameTypeReqDescription
id–yesVoucher id (from papierkram_list_vouchers).

No output schema declared.

No examples provided.

papierkram_get_voucher_document ~181

Get an original file uploaded to an expense voucher (a receipt PDF or image), so its content can be read. Reads the voucher (papierkram_get_voucher) and fetches documents[].uri. Images come back as images, PDFs as an embedded file (up to 3 MB). The API has no documented download for one document: if Papierkram does not serve the file to an API token, the tool says so; then use papierkram_get_voucher_pdf. Files that are not yet attached to a voucher (the upload inbox) are not reachable through the Papierkram API.

NameTypeReqDescription
document_id––Document id (documents[].id of papierkram_get_voucher). Needed only when the voucher has more than one document.
voucher_id–yesVoucher id (from papierkram_list_vouchers).

No output schema declared.

No examples provided.

papierkram_get_voucher_pdf ~92

Get the PDF that Papierkram makes for one expense voucher (GET /expense/vouchers/{id}/pdf). The API reference does not say whether it embeds the uploaded receipt; for the original uploaded file use papierkram_get_voucher_document. Returns the PDF as an embedded file (up to 3 MB).

NameTypeReqDescription
id–yesVoucher id (from papierkram_list_vouchers).

No output schema declared.

No examples provided.

papierkram_list_bank_connections ~128

List the bank accounts connected to Papierkram (name, IBAN, balance data as Papierkram reports it). Paged.

NameTypeReqDescription
order_bystring–Field to sort by, e.g. document_date. Must be used together with order_direction.
order_directionstring–Sort direction. Must be used together with order_by.
pageinteger–Page number, 1-based (default 1). Use next_page from the previous reply.
page_sizeinteger–Results per page, 1-100 (default 100).

No output schema declared.

No examples provided.

papierkram_list_bank_transactions ~147

List bank transactions (value, currency, usage text, booking date, counterparty). Filter by bank connection. Paged.

NameTypeReqDescription
bank_connection_id––Only transactions of this bank connection (from papierkram_list_bank_connections).
order_bystring–Field to sort by, e.g. document_date. Must be used together with order_direction.
order_directionstring–Sort direction. Must be used together with order_by.
pageinteger–Page number, 1-based (default 1). Use next_page from the previous reply.
page_sizeinteger–Results per page, 1-100 (default 100).

No output schema declared.

No examples provided.

papierkram_list_companies ~122

List contacts (companies: customers and suppliers) with address, VAT id and contact data. Paged.

NameTypeReqDescription
order_bystring–Field to sort by, e.g. document_date. Must be used together with order_direction.
order_directionstring–Sort direction. Must be used together with order_by.
pageinteger–Page number, 1-based (default 1). Use next_page from the previous reply.
page_sizeinteger–Results per page, 1-100 (default 100).

No output schema declared.

No examples provided.

papierkram_list_estimates ~194

List estimates (Angebote) with state, dates and totals. Filter by company, project or document date range. Paged.

NameTypeReqDescription
company_id––Only estimates of this company.
document_date_range_endstring–Only documents dated on or before this day (yyyy-mm-dd).
document_date_range_startstring–Only documents dated on or after this day (yyyy-mm-dd).
order_bystring–Field to sort by, e.g. document_date. Must be used together with order_direction.
order_directionstring–Sort direction. Must be used together with order_by.
pageinteger–Page number, 1-based (default 1). Use next_page from the previous reply.
page_sizeinteger–Results per page, 1-100 (default 100).
project_id––Only estimates of this project.

No output schema declared.

No examples provided.

papierkram_list_invoices ~205

List outgoing invoices (Ausgangsrechnungen) with state (draft, ...), dates, totals and outstanding_amount. Filter by company, project or document date range. Paged.

NameTypeReqDescription
company_id––Only invoices of this company.
document_date_range_endstring–Only documents dated on or before this day (yyyy-mm-dd).
document_date_range_startstring–Only documents dated on or after this day (yyyy-mm-dd).
order_bystring–Field to sort by, e.g. document_date. Must be used together with order_direction.
order_directionstring–Sort direction. Must be used together with order_by.
pageinteger–Page number, 1-based (default 1). Use next_page from the previous reply.
page_sizeinteger–Results per page, 1-100 (default 100).
project_id––Only invoices of this project.

No output schema declared.

No examples provided.

papierkram_list_payment_terms ~118

List the payment term templates (ids needed as payment_term_id when creating an invoice).

NameTypeReqDescription
order_bystring–Field to sort by, e.g. document_date. Must be used together with order_direction.
order_directionstring–Sort direction. Must be used together with order_by.
pageinteger–Page number, 1-based (default 1). Use next_page from the previous reply.
page_sizeinteger–Results per page, 1-100 (default 100).

No output schema declared.

No examples provided.

papierkram_list_persons ~128

List the contact persons of one company. Paged.

NameTypeReqDescription
company_id–yesCompany id (from papierkram_list_companies).
order_bystring–Field to sort by, e.g. document_date. Must be used together with order_direction.
order_directionstring–Sort direction. Must be used together with order_by.
pageinteger–Page number, 1-based (default 1). Use next_page from the previous reply.
page_sizeinteger–Results per page, 1-100 (default 100).

No output schema declared.

No examples provided.

papierkram_list_projects ~127

List projects with dates, budget and state. Filter by company. Paged.

NameTypeReqDescription
company_id––Only projects of this company.
order_bystring–Field to sort by, e.g. document_date. Must be used together with order_direction.
order_directionstring–Sort direction. Must be used together with order_by.
pageinteger–Page number, 1-based (default 1). Use next_page from the previous reply.
page_sizeinteger–Results per page, 1-100 (default 100).

No output schema declared.

No examples provided.

papierkram_list_propositions ~138

List the stored products and services (Leistungen/Artikel) with article number, price and unit (the VAT rate is only in papierkram_get_proposition). Paged.

NameTypeReqDescription
order_bystring–Field to sort by, e.g. document_date. Must be used together with order_direction.
order_directionstring–Sort direction. Must be used together with order_by.
pageinteger–Page number, 1-based (default 1). Use next_page from the previous reply.
page_sizeinteger–Results per page, 1-100 (default 100).

No output schema declared.

No examples provided.

papierkram_list_tasks ~139

List time-tracking tasks. Filter by project or product/service. Paged.

NameTypeReqDescription
order_bystring–Field to sort by, e.g. document_date. Must be used together with order_direction.
order_directionstring–Sort direction. Must be used together with order_by.
pageinteger–Page number, 1-based (default 1). Use next_page from the previous reply.
page_sizeinteger–Results per page, 1-100 (default 100).
project_id––Only tasks of this project.
proposition_id––Only tasks of this product/service.

No output schema declared.

No examples provided.

papierkram_list_time_entries ~263

List tracked time entries. Filter by project, task, invoice, user, billing state or start time range (RFC 3339 date-time). Paged.

NameTypeReqDescription
billing_statestring–Only entries in this billing state.
invoice_id––Only entries billed on this invoice.
order_bystring–Field to sort by, e.g. document_date. Must be used together with order_direction.
order_directionstring–Sort direction. Must be used together with order_by.
pageinteger–Page number, 1-based (default 1). Use next_page from the previous reply.
page_sizeinteger–Results per page, 1-100 (default 100).
project_id––Only entries of this project.
start_time_range_endstring–Only entries started at or before this time, RFC 3339.
start_time_range_startstring–Only entries started at or after this time, RFC 3339, e.g. 2026-10-01T00:00:00Z.
task_id––Only entries of this task.
user_id––Only entries of this user (from papierkram_list_users).

No output schema declared.

No examples provided.

papierkram_list_users ~118

List the users of the account (ids needed as user_id for time entries and tasks).

NameTypeReqDescription
order_bystring–Field to sort by, e.g. document_date. Must be used together with order_direction.
order_directionstring–Sort direction. Must be used together with order_by.
pageinteger–Page number, 1-based (default 1). Use next_page from the previous reply.
page_sizeinteger–Results per page, 1-100 (default 100).

No output schema declared.

No examples provided.

papierkram_list_vouchers ~210

List expense vouchers (Belege / incoming invoices and receipts) with creditor, state, dates and amounts. Filter by creditor (supplier company), project or document date range. Paged.

NameTypeReqDescription
creditor_id––Only vouchers of this creditor (company id of the supplier).
document_date_range_endstring–Only documents dated on or before this day (yyyy-mm-dd).
document_date_range_startstring–Only documents dated on or after this day (yyyy-mm-dd).
order_bystring–Field to sort by, e.g. document_date. Must be used together with order_direction.
order_directionstring–Sort direction. Must be used together with order_by.
pageinteger–Page number, 1-based (default 1). Use next_page from the previous reply.
page_sizeinteger–Results per page, 1-100 (default 100).
project_id––Only vouchers of this project.

No output schema declared.

No examples provided.

papierkram_pay_voucher ~253

WRITE: book a payment of an expense voucher (POST /expense/vouchers/{id}/pay), with a value and payment date or with an existing bank transaction. Without confirm it changes nothing: it reads the voucher and returns the exact request for the user to review. After approval, call again with confirm: true. A value that differs from the open amount needs difference_reason (teilzahlung = part payment, skonto = cash discount, mahnung = reminder fee, schmaelerung = reduction, sonstige = other). A repeated call books a second payment: after an error, check the voucher state with papierkram_get_voucher before retrying.

NameTypeReqDescription
banking_transaction_id––Bank transaction that paid the voucher (from papierkram_list_bank_transactions).
confirmboolean–False or missing: preview only, nothing is booked. True: book the payment now.
difference_reasonstring–Why the value differs from the open amount.
id–yesVoucher id.
payment_datestring–Payment date yyyy-mm-dd (default: Papierkram's default, today).
valuenumber–Paid amount. Needed unless banking_transaction_id is given.

No output schema declared.

No examples provided.

papierkram_update_company ~214

WRITE: change fields of an existing contact (only the fields you pass are changed). Read it first with papierkram_get_company.

NameTypeReqDescription
bank_bicstring–BIC.
bank_ibanstring–IBAN.
contact_typestring–customer or supplier.
delivery_methodstring–How documents are delivered to this contact.
emailstring–E-mail address.
id–yesCompany id.
namestring–New company name.
notesstring–Internal notes.
phonestring–Phone.
postal_citystring–Postal address: city.
postal_countrystring–Postal address: country.
postal_streetstring–Postal address: street and number.
postal_zipstring–Postal address: ZIP.
ust_idnrstring–VAT id (USt-IdNr.), e.g. DE123456789.
websitestring–Website.

No output schema declared.

No examples provided.

papierkram_update_voucher ~439

WRITE: change an existing expense voucher (PUT /expense/vouchers/{id}): title, supplier, provenance, dates, notes, flag or line items (amount, VAT rate, category). Only the fields you pass are changed. line_items REPLACES all lines of the voucher: pass the full new list. Without confirm it changes nothing: it reads the voucher and returns its current values next to the exact request for the user to review. After approval, call again with the same arguments and confirm: true. Papierkram refuses a voucher that can no longer be edited (e.g. a paid or locked one). Lines with a billing (re-invoicing) or depreciation (AfA) setting cannot be replaced here, so the tool refuses line_items for such a voucher; change those lines in Papierkram. Payments are booked with papierkram_pay_voucher. Costs 1 Papierkram API credit; the preview, and a confirmed line change, also read the voucher (1 each).

NameTypeReqDescription
confirmboolean–False or missing: preview only, nothing is changed. True: change the voucher now.
creditor_id––New supplier company id (from papierkram_list_companies; it must be a supplier).
descriptionstring–New notes.
document_datestring–New receipt date yyyy-mm-dd (Belegdatum).
due_datestring|null–New due date yyyy-mm-dd; null removes the due date.
entertainment_personsarray–Guests of a business meal (Bewirtungskosten only).
entertainment_reasonstring–Reason of a business meal (Bewirtungskosten only).
flaggedboolean–Mark (true) or unmark (false) the voucher for a later check.
id–yesVoucher id (from papierkram_list_vouchers).
line_itemsarray–The complete new list of voucher lines. It replaces ALL current lines.
namestring–New voucher title.
provenancestring–Where the supplier is: domestic (Germany), eu or foreign.

No output schema declared.

No examples provided.

papierkram_upload_voucher_document ~154

WRITE: attach a file (receipt PDF or image) to an existing expense voucher (POST /expense/vouchers/{id}/documents). The file is given as base64, up to 3 MB. Check papierkram_get_voucher first: a repeated upload attaches the file twice. Costs 10 Papierkram API credits.

NameTypeReqDescription
content_base64stringyesThe file content as standard base64.
filenamestringyesFile name, e.g. receipt-2026-10-31.pdf.
mime_typestringyesMedia type of the file.
voucher_id–yesVoucher id (from papierkram_list_vouchers or papierkram_create_voucher).

No output schema declared.

No examples provided.

Install

How do I install the Papierkram MCP by usefulapi server?

Papierkram MCP by usefulapi is a hosted endpoint at https://papierkram.usefulapi.io/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 · papierkram.usefulapi.io

# add to Claude Code
claude mcp add --transport http io-usefulapi-papierkram 'https://papierkram.usefulapi.io/mcp'
Common questions

What is the Papierkram MCP by usefulapi server?

Papierkram MCP by usefulapi is listed in the public MCP registry as io.usefulapi/papierkram. Read Papierkram invoices, vouchers, contacts, projects, time; create contacts, time, draft invoices. This page covers its hosted endpoint (https://papierkram.usefulapi.io/mcp).

Is the Papierkram MCP by usefulapi server safe to use?

Papierkram MCP by usefulapi scores 18 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 Papierkram MCP by usefulapi server expose?

Papierkram MCP by usefulapi exposes 39 tools: papierkram_get_info, papierkram_list_companies, papierkram_get_company, papierkram_list_persons, papierkram_get_person, and 34 more. Their descriptions and schemas cost roughly 5,515 tokens of context every time the server is loaded.

Does the Papierkram MCP by usefulapi server require authentication?

Its publisher declares no required credentials for Papierkram MCP by usefulapi. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.

Is the Papierkram MCP by usefulapi server still maintained?

Papierkram MCP by usefulapi 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 did VerifyMCP test on the Papierkram MCP by usefulapi server?

VerifyMCP ran 4 checks on Papierkram MCP by usefulapi, covering TLS certificate, HSTS header, DNSSEC and Transport. 7 items could not be completed, a gap on our side rather than a finding about Papierkram MCP by usefulapi: Authorization, HTTPS, Schema quality, Stability and 3 more. 5 categories score 0 for that reason, because we only credit what we can confirm. 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.