mcp server
final-notice
Free demand-letter PDF generator for unpaid invoices, 80+ jurisdictions, 29 languages.
Description as published by the maintainer. Source
- version 1.0.0
- active
- document understanding
- voice
active — Registry entry last updated 2026-06-19. Dashed tags are derived by ZBS Index from the published description, not stated by the maintainer.
What this server can do
3 functions, named and described by the server itself. Parameter names are shown because they say more about what a function does than its name usually does.
generate_demand_letter(bank, tone, amount, attested, currency, language, senderRef, debtorName, debtorType, enclosures, senderName, senderType, signerName, description, senderTitle, deadlineDays, jurisdiction, originalDate, debtorAddress, invoiceNumber, senderAddress, senderContact, deliveryMethod)- Generate the finished demand-letter PDF (formal letter + matching envelope), localized and legally formatted for the jurisdiction. Returns the PDF as a base64 resource. Free, no registration. Required: senderName, senderAddress, debtorName, debtorAddress, amount.
list_jurisdictions- List every supported country/jurisdiction (code, name, currency, default language) plus the available languages and tones. Call this first to pick a valid jurisdiction + language.
preview_demand_letter(bank, tone, amount, attested, currency, language, senderRef, debtorName, debtorType, enclosures, senderName, senderType, signerName, description, senderTitle, deadlineDays, jurisdiction, originalDate, debtorAddress, invoiceNumber, senderAddress, senderContact, deliveryMethod)- Render the demand letter's text content (title, subject, body paragraphs, amount line, legal reference, closing) as structured JSON, without producing a PDF. Use to review or refine wording before generating. Required: senderName, senderAddress, debtorName, debtorAddress, amount.
Last successful function declaration observed on . Source: https://finalnotice.io/mcp. We list what the server declared; we do not call any of these functions.
Endpoint status observed on . Source: https://finalnotice.io/mcp.
Signals
These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.
| Signal | Value | What it measures | Window | Observed | Source |
|---|---|---|---|---|---|
| Latest published version | 1.0.0 | Latest version string the maintainer published to the registry. | as of fetch | Model Context Protocol | |
| Registry record last updated | 2026-06-19 | When the registry record was last updated by its maintainer. | point in time | Model Context Protocol | |
| First listed in the MCP Registry | 2026-06-19 | Date this server was first published to the official MCP Registry. Not a usage or quality measure. | point in time | Model Context Protocol | |
| mcp tools declared | 3 tools | Number of functions the server itself declared when asked to list them. This is what the server offers an agent, not a measure of how well any of them work. | as of probe | finalnotice.io | |
| mcp endpoint status | ok | The server listed 3 functions when asked. | as of probe | finalnotice.io |
Where to get it
Also from ptrinh
-
io.github.ptrinh/freeport-nostr
Search Freeport Nostr events by kind, tag & geohash radius (rides, services, reputation).
This record as data
Every field on this page, with its source and observation date, is in the catalog JSON. Fetch the whole kind at once instead of parsing this HTML.
GET /api/v1/entries/mcp_server.json