briefflink
Registry code: 19dcdb2b8784d307
Briefflink druckt PDF-Briefe, kuvertiert, frankiert und versendet sie über den Versandpartner PIN AG. Ablauf: Preis mit get_letter_price nennen, PDF per create_upload_link (Nutzer lädt hoch) oder pdf_base64 übergeben, dann send_letter. send_letter liefert nur einen Bezahllink – der Brief geht erst nach der Zahlung durch den Nutzer raus. Vor send_letter immer Absender (Rücksendeadresse), Empfänger, Einschreiben-Wahl und Preis vom Nutzer bestätigen lassen. Die Empfängeradresse muss im Adressfeld des PDFs stehen oder wird von Briefflink dort eingesetzt.
- endpoint
- https://briefflink.de/api/mcp.php
- 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 briefflink live?
- Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
- Is briefflink free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does briefflink have?
- 4 tools: send_letter, get_letter_price, get_letter_status, create_upload_link.
- Is briefflink 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 4 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.
send_letter unknown never probed
Legt einen Briefauftrag an und gibt einen Stripe-Bezahllink zurück. Der Brief wird erst gedruckt und versendet, wenn der Nutzer bezahlt hat. Dokument per upload_id (aus create_upload_link) oder pdf_base64.
{ "type": "object", "required": [ "recipient_name", "recipient_street", "recipient_zip_city", "email", "sender_name", "sender_street", "sender_zip_city" ], "properties": { "email": { "type": "string", "description": "E-Mail des Nutzers für Versandbeleg und Rechnung" }, "country": { "type": "string", "default": "DE", "description": "ISO-Ländercode des Empfängers, z. B. DE, AT, CH, US" }, "upload_id": { "type": "string", "description": "ID aus create_upload_link" }, "pdf_base64": { "type": "string", "description": "Alternativ: PDF als Base64 (max. 10 MB)" }, "sender_name": { "type": "string", "description": "Absender: Name / Firma (Pflicht, erscheint als Rücksendeadresse)" }, "einschreiben": { "enum": [ "nein", "einwurf" ], "type": "string", "default": "nein", "description": "nein = Standardbrief, einwurf = Einwurf-Einschreiben mit Sendungsnummer (+5,49 € national, +7,49 € Ausland)" }, "sender_street": { "type": "string", "description": "Absender: Straße und Hausnummer (Pflicht)" }, "recipient_name": { "type": "string", "description": "Name / Firma des Empfängers" }, "sender_zip_city": { "type": "string", "description": "Absender: PLZ und Ort (Pflicht)" }, "recipient_street": { "type": "string", "description": "Straße und Hausnummer" }, "recipient_zip_city": { "type": "string", "description": "PLZ und Ort, z. B. \"10115 Berlin\"" } } }arguments 64 linesget_letter_price unknown 2h ago
Berechnet den Endpreis eines Briefes (Druck, Kuvert, Porto) aus Seitenzahl, Einschreiben-Wahl und Zielland. Kein Auftrag, keine Kosten.
{ "type": "object", "required": [ "pages" ], "properties": { "pages": { "type": "integer", "maximum": 20, "minimum": 1, "description": "Anzahl PDF-Seiten (1–20). 1–3 Standardbrief, 4–9 Kompaktbrief, 10–20 Großbrief" }, "country": { "type": "string", "default": "DE", "description": "ISO-Ländercode des Empfängers, z. B. DE, AT, CH, US" }, "einschreiben": { "enum": [ "nein", "einwurf" ], "type": "string", "default": "nein", "description": "nein = Standardbrief, einwurf = Einwurf-Einschreiben mit Sendungsnummer (+5,49 € national, +7,49 € Ausland)" } } }arguments 28 linesget_letter_status unknown 2h ago
Zeigt, ob ein Auftrag noch auf Zahlung wartet, bezahlt, versendet oder fehlgeschlagen ist.
{ "type": "object", "required": [ "letter_id" ], "properties": { "letter_id": { "type": "string", "description": "letter_id aus send_letter" } } }arguments 12 linescreate_upload_link unknown never probed
Erstellt einen Link (24 h gültig), über den der Nutzer sein PDF selbst hochlädt. Die upload_id danach an send_letter übergeben.
{ "type": "object", "properties": {} }arguments 4 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 id19dcdb2b8784d307.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/19dcdb2b8784d307/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/19dcdb2b8784d307?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.