dozo
Registry code: eb0daad4e79ae94d
Dozo makes PDF invoices and works on PDFs on the user's own device, on dozokit.com: nothing is uploaded. For an invoice, call make_invoice with what the user said (ask for any missing name, line or price first); then give the user the link from the result: it opens the invoice filled in on dozokit.com, where they check it and download the PDF. For merging, compressing, splitting, signing or organizing PDFs, or turning images into a PDF, call pdf_tool and give the user the link: they pick their files on dozokit.com. Files attached to this chat cannot be used by Dozo; do not ask the user to…
- endpoint
- https://dozokit.com/mcp
- protocol
- streamable-http ·2025-06-18
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is dozo live?
- Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
- Is dozo free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does dozo have?
- 2 tools: pdf_tool, make_invoice.
- Is dozo safe to connect?
- The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
90 days 100%· all time 100%
last good check
of 2 tools
- unknown → live
Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.
through this hub
successful
what callers paid
Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run
Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.
pdf_tool unknown 2h ago
Give the user the Dozo PDF tool they need, on dozokit.com: merge (several PDFs into one), compress (make a PDF smaller), split (by page ranges), jpg_to_pdf (images into one PDF), sign, organize (reorder, rotate, delete pages). The user picks the files there and they never leave their device. Files already attached to this conversation cannot be used. Read-only. Donne le lien vers l’outil PDF : les fichiers restent sur l’appareil.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "tool" ], "properties": { "lang": { "enum": [ "en", "fr" ], "type": "string", "default": "en", "description": "Language of the tool, fr for a French-speaking user." }, "tool": { "enum": [ "merge", "compress", "split", "jpg_to_pdf", "sign", "organize" ], "type": "string" } } }arguments 29 linesmake_invoice unknown 2h ago
Lay out a PDF invoice from the details the user gives: who sends it, who pays, and the lines (description, quantity, unit price, VAT %). Shows a preview, and returns a dozokit.com link that opens the invoice filled in, where the user checks it and downloads the PDF, made on their device. Use lang fr and EUR for a French invoice; set noVat for a French micro-entrepreneur exempt from VAT (it prints « TVA non applicable, art. 293 B du CGI »). Read-only: nothing is sent or stored. Crée une facture PDF à partir des informations données.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "seller", "client", "lines" ], "properties": { "due": { "type": "string", "pattern": "^\\d{4}-\\d{2}-\\d{2}$", "description": "Due date, YYYY-MM-DD. Defaults to 30 days after the issue date." }, "bank": { "type": "string", "maxLength": 300, "description": "Bank details such as IBAN and BIC." }, "lang": { "enum": [ "en", "fr" ], "type": "string", "default": "en", "description": "Language printed on the invoice." }, "lines": { "type": "array", "items": { "type": "object", "required": [ "description", "price" ], "properties": { "qty": { "type": "number", "default": 1, "maximum": 1000000, "minimum": 0 }, "vat": { "type": "number", "default": 0, "maximum": 100, "minimum": 0, "description": "VAT rate in percent, 0 when there is none." }, "price": { "type": "number", "maximum": 1000000000, "minimum": -1000000000, "description": "Unit price, before VAT." }, "description": { "type": "string", "maxLength": 200, "minLength": 1 } } }, "maxItems": 50, "minItems": 1 }, "noVat": { "type": "boolean", "default": false }, "terms": { "type": "string", "maxLength": 600, "description": "Payment terms or notes." }, "client": { "type": "object", "required": [ "name" ], "properties": { "name": { "type": "string", "maxLength": 120, "minLength": 1, "description": "Who pays the invoice." }, "address": { "type": "string", "maxLength": 300 }, "vatNumber": { "type": "string", "maxLength": 40 } } }, "issued": { "type": "string", "pattern": "^\\d{4}-\\d{2}-\\d{2}$", "description": "Issue date, YYYY-MM-DD. Defaults to today." }, "number": { "type": "string", "maxLength": 40, "description": "Invoice number. Defaults to INV-<year>-001." }, "seller": { "type": "object", "required": [ "name" ], "properties": { "name": { "type": "string", "maxLength": 120, "minLength": 1, "description": "The person or company sending the invoice." }, "email": { "type": "string", "maxLength": 120 }, "address": { "type": "string", "maxLength": 300 }, "companyId": { "type": "string", "maxLength": 60, "description": "SIRET, company number, ABN…" }, "vatNumber": { "type": "string", "maxLength": 40 } } }, "currency": { "type": "string", "default": "EUR", "pattern": "^[A-Z]{3}$", "description": "ISO currency code." } } }arguments 146 lines
This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.
Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your MCP server's instructions — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's ideb0daad4e79ae94d.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/eb0daad4e79ae94d/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/eb0daad4e79ae94d?ref=badge)
The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.
An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.