# Briefflink – Briefe mit KI versenden (remote · briefflink.de)

Send real paper letters from AI chat: print, envelope, postage, delivery. Pay per letter.

- Trust score: 76/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `briefflink.de`: 76/100 (this document), [markdown](https://verifymcp.io/servers/de-briefflink-letter/api-mcp-php.md), [page](https://verifymcp.io/servers/de-briefflink-letter/api-mcp-php)

## Channel facts

- Endpoint: `https://briefflink.de/api/mcp.php`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 69/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 654 tokens (~163/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 57/100
  - Stability observed for 17 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the Briefflink – Briefe mit KI versenden MCP server?

Briefflink – Briefe mit KI versenden is a hosted endpoint at https://briefflink.de/api/mcp.php, 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.

### Claude

```bash
claude mcp add --transport http de-briefflink-letter 'https://briefflink.de/api/mcp.php'
```

### Cursor

```json
{
  "mcpServers": {
    "de-briefflink-letter": {
      "url": "https://briefflink.de/api/mcp.php"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "de-briefflink-letter": {
      "type": "http",
      "url": "https://briefflink.de/api/mcp.php"
    }
  }
}
```

### Codex

```toml
[mcp_servers.de-briefflink-letter]
url = "https://briefflink.de/api/mcp.php"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "de-briefflink-letter": {
      "type": "remote",
      "url": "https://briefflink.de/api/mcp.php",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add de-briefflink-letter --url 'https://briefflink.de/api/mcp.php' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  de-briefflink-letter:
    url: "https://briefflink.de/api/mcp.php"
```

### Netclaw

```json
{
  "McpServers": {
    "de-briefflink-letter": {
      "Transport": "http",
      "Url": "https://briefflink.de/api/mcp.php"
    }
  }
}
```

### Vellum

```bash
assistant mcp add de-briefflink-letter -t streamable-http -u 'https://briefflink.de/api/mcp.php'
```

### Other

```json
{
  "mcpServers": {
    "de-briefflink-letter": {
      "type": "http",
      "url": "https://briefflink.de/api/mcp.php"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 76, +1)

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

### 2026-11-02 (score 75, +1)

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

### 2026-10-30 (score 74, +1)

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

### 2026-10-28 (score 73, +1)

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

### 2026-10-26 (score 72, +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.

### 2026-10-24 (score 71, +1)

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

### 2026-10-23 (score 70, +37)

- [security improvement] Authorization: unverified → partial
- [security improvement] Injection markers: unverified → pass
- [functional regression] MCP protocol: unverified → fail
- [functional improvement] Endpoint reachability: not serving MCP → reachable
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] Stability: unverified → 0.13

### 2026-10-22 (score 33, −36)

- [security regression] Endpoint reachability: reachable → not serving MCP
- [security regression] Stability: 0.07 → unverified
- [security regression] Tool safety: pass → unverified
- [security regression] Authorization: partial → unverified
- [functional regression] Capabilities: fail → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional] First check of Schema quality: unverified

## MCP tools (4)

### `get_letter_price` (~150 tokens)

Briefpreis berechnen

Berechnet den Endpreis eines Briefes (Druck, Kuvert, Porto) aus Seitenzahl, Einschreiben-Wahl und Zielland. Kein Auftrag, keine Kosten.

Input parameters:

- `country` (string): ISO-Ländercode des Empfängers, z. B. DE, AT, CH, US
- `einschreiben` (string): nein = Standardbrief, einwurf = Einwurf-Einschreiben mit Sendungsnummer (+5,49 € national, +7,49 € Ausland)
- `pages` (integer, required): Anzahl PDF-Seiten (1–20). 1–3 Standardbrief, 4–9 Kompaktbrief, 10–20 Großbrief

### `create_upload_link` (~40 tokens)

Upload-Link erstellen

Erstellt einen Link (24 h gültig), über den der Nutzer sein PDF selbst hochlädt. Die upload_id danach an send_letter übergeben.

### `send_letter` (~290 tokens)

Brief beauftragen (Bezahllink)

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.

Input parameters:

- `country` (string): ISO-Ländercode des Empfängers, z. B. DE, AT, CH, US
- `einschreiben` (string): nein = Standardbrief, einwurf = Einwurf-Einschreiben mit Sendungsnummer (+5,49 € national, +7,49 € Ausland)
- `email` (string, required): E-Mail des Nutzers für Versandbeleg und Rechnung
- `pdf_base64` (string): Alternativ: PDF als Base64 (max. 10 MB)
- `recipient_name` (string, required): Name / Firma des Empfängers
- `recipient_street` (string, required): Straße und Hausnummer
- `recipient_zip_city` (string, required): PLZ und Ort, z. B. "10115 Berlin"
- `sender_name` (string, required): Absender: Name / Firma (Pflicht, erscheint als Rücksendeadresse)
- `sender_street` (string, required): Absender: Straße und Hausnummer (Pflicht)
- `sender_zip_city` (string, required): Absender: PLZ und Ort (Pflicht)
- `upload_id` (string): ID aus create_upload_link

### `get_letter_status` (~43 tokens)

Briefstatus abfragen

Zeigt, ob ein Auftrag noch auf Zahlung wartet, bezahlt, versendet oder fehlgeschlagen ist.

Input parameters:

- `letter_id` (string, required): letter_id aus send_letter

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/de-briefflink-letter/api-mcp-php#diagnostics

## Score history

- 2026-11-05: 76
- 2026-11-04: 76
- 2026-11-03: 75
- 2026-11-02: 75
- 2026-11-01: 74
- 2026-10-31: 74
- 2026-10-30: 74
- 2026-10-29: 73
- 2026-10-28: 73
- 2026-10-27: 72
- 2026-10-26: 72
- 2026-10-25: 71
- 2026-10-24: 71
- 2026-10-23: 70
- 2026-10-22: 33
- 2026-10-21: 69
- 2026-10-20: 69
- 2026-10-19: 68

## Common questions

### What is the Briefflink – Briefe mit KI versenden MCP server?

Briefflink – Briefe mit KI versenden is an MCP server listed in the public MCP registry as de.briefflink/letter. Send real paper letters from AI chat: print, envelope, postage, delivery. Pay per letter. This page covers its hosted endpoint (https://briefflink.de/api/mcp.php).

### Is the Briefflink – Briefe mit KI versenden MCP server safe to use?

Briefflink – Briefe mit KI versenden scores 76 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 Briefflink – Briefe mit KI versenden MCP server expose?

Briefflink – Briefe mit KI versenden exposes 4 tools: get_letter_price, create_upload_link, send_letter, get_letter_status. Their descriptions and schemas cost roughly 523 tokens of context every time the server is loaded.

### Does the Briefflink – Briefe mit KI versenden MCP server require authentication?

No. We connected to Briefflink – Briefe mit KI versenden without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Briefflink – Briefe mit KI versenden MCP server still maintained?

Briefflink – Briefe mit KI versenden 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.

## Links

- Remote endpoint: https://briefflink.de/api/mcp.php
- Website: https://briefflink.de/ai/
- Changelog RSS feed: https://verifymcp.io/servers/de-briefflink-letter/api-mcp-php.xml
- Changelog JSON feed: https://verifymcp.io/servers/de-briefflink-letter/api-mcp-php.json
- HTML version of this page: https://verifymcp.io/servers/de-briefflink-letter/api-mcp-php