Tamgara
REMOTE · API.TAMGARA.COM
Fill in 1,000+ legal PDF templates in many languages, get a signed PDF back. Free, no API key.
Available components
Last scanned (7 hours ago)
Scores higher than 79% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Documents and Files
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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 33 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability75
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 2753 tokens (~83/item across 33 items; 33 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage99
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 97% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "envelope_send_invite" implies "send" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 34 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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://api.tamgara.com/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=api.tamgara.com | CN=YE2,O=Let's Encrypt,C=US | 22 Sept 2026 | 21 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 6cec399ef00ce62275d69fd555e7e932414 |
| SANs: api.tamgara.com | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.tamgara.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| tamgara.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.tamgara.com/api/mcp | Verified | 200 | |
| http (plaintext) | http://api.tamgara.com/api/mcp | HTTPS enforced | 308 | https://api.tamgara.com/api/mcp |
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 →
account_balance ~79
Guthaben-Konto abfragen (Kostendeckel für kostenpflichtige KI-Calls). Das Konto mit 1 € Startgutschein wird beim ersten kostenpflichtigen Call ausgestellt und dort zurückgegeben — merken und künftig mitschicken. Kostenlose Funktionen brauchen kein Konto.
| Name | Type | Req | Description |
|---|---|---|---|
| account_id | string | – | Bestehendes Konto (optional). |
No output schema declared.
No examples provided.
account_topup ~74
Guthaben aufladen. Hinweis: Die Zahlung wird gerade eingerichtet — der Aufladewunsch wird vermerkt, aber noch nicht real belastet (die kostenlosen Funktionen bleiben ohnehin frei).
| Name | Type | Req | Description |
|---|---|---|---|
| account_id | string | – | Konto (optional; sonst neu). |
| amount_cents | integer | – | Wunschbetrag in Cent (optional). |
No output schema declared.
No examples provided.
add_cover_page ~98
Stellt einem PDF ein DIN-5008-Adressblatt voran (für den Postversand). recipient = {name,street,zip,city,country}.
| Name | Type | Req | Description |
|---|---|---|---|
| filename | string | – | Dateiname (optional). |
| pdfBase64 | string | yes | Das PDF (base64). |
| recipient | object | yes | – |
| senderLine | string | – | Einzeilige Rücksendeangabe über dem Adressblock (optional). |
No output schema declared.
No examples provided.
apply_scan_answers ~127
Befüllt erkannte Felder eines gescannten (nicht-AcroForm-)PDFs: Text auf Schreiblinien, X in Checkboxen — per Ratio-Positionen (z. B. aus einer Feld-Erkennung).
| Name | Type | Req | Description |
|---|---|---|---|
| fields | array | yes | Erkannte Felder. |
| filename | string | – | Dateiname (optional). |
| lang | string | – | Sprachhinweis für die Schrift (optional). |
| pdfBase64 | string | yes | Das gescannte PDF (base64). |
| values | object | yes | Feld-id → Wert (Text; "true" für Checkbox). |
No output schema declared.
No examples provided.
brief_cancel ~35
Storniert einen Brief im 15-Minuten-Fenster von LetterXpress.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Brief-id. |
No output schema declared.
No examples provided.
brief_confirm ~39
Nach Zahlung: Brief einreichen. Braucht die job_id aus brief_create_checkout.
| Name | Type | Req | Description |
|---|---|---|---|
| jobId | string | yes | job_id aus brief_create_checkout. |
No output schema declared.
No examples provided.
brief_create_checkout ~137
Startet den bezahlten Briefversand: liefert eine Stripe-Checkout-URL. Der MENSCH bezahlt; danach brief_confirm mit der job_id. (Kein kostenloser Direktversand über die KI.)
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | Zielland: DE | AT | CH. |
| filename | string | – | Dateiname (optional). |
| pages | integer | – | Seitenzahl (optional). |
| pdfBase64 | string | yes | Das zu versendende PDF. |
| recipient | string | yes | Anzeigename des Empfängers (für Beleg). |
| registered | boolean | – | Einwurf-Einschreiben. |
No output schema declared.
No examples provided.
brief_ping ~28
Prüft, ob Briefversand (Post via LetterXpress) verfügbar/bezahlt ist.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
brief_quote ~91
Preis für einen Postbrief (Standard oder Einschreiben). Länder: DE/AT/CH.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | Zielland: DE | AT | CH (Default DE). |
| pages | integer | – | Seitenzahl (optional; sonst aus PDF). |
| pdfBase64 | string | – | Das zu versendende PDF. |
| registered | boolean | – | Einwurf-Einschreiben statt Standard. |
No output schema declared.
No examples provided.
brief_status ~26
Status/Tracking eines Briefs per id.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Brief-id. |
No output schema declared.
No examples provided.
envelope_create ~225
Sendet ein PDF zur mehrparteiigen elektronischen Signatur (DocuSign-Stil). Liefert die Vorgangs-id, einen ownerKey (geheim halten!) und pro Empfänger einen Signier-Link. fields platzieren Signatur-/Text-/Datum-/Checkbox-Felder per Ratio (0..1, y von oben). Emails an Empfänger nur über den zurückgegebenen ownerKey.
| Name | Type | Req | Description |
|---|---|---|---|
| docName | string | yes | Dokumentname, z. B. "Mietvertrag.pdf". |
| expiresDays | integer | – | Ablauf in Tagen (0 = kein Ablauf). |
| fields | array | – | Feld-Platzierungen. |
| isPublic | boolean | – | Öffentlicher Signier-Link statt fester Empfänger. |
| message | string | – | Begleitnachricht an die Empfänger (optional). |
| ownerName | string | yes | Name des Absenders/Erstellers. |
| pdfBase64 | string | yes | Das zu signierende PDF (z. B. aus fill_template). |
| recipients | array | – | Empfänger (bei isPublic leer). |
No output schema declared.
No examples provided.
envelope_send_invite ~81
Verschickt (erneut) die Signier-Einladung per E-Mail an einen Empfänger. Nur mit ownerKey.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | Ziel-E-Mail. | |
| id | string | yes | Vorgangs-id. |
| ownerKey | string | yes | ownerKey. |
| recipient | integer | yes | Empfänger-Index (0-basiert). |
No output schema declared.
No examples provided.
envelope_status ~67
Status eines Signier-Vorgangs (wer hat gesehen/unterschrieben) per id + ownerKey.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Vorgangs-id. |
| ownerKey | string | yes | Der bei create erhaltene ownerKey. |
| withInputs | boolean | – | Eingaben mitliefern. |
No output schema declared.
No examples provided.
envelope_upload_final ~67
Lädt das fertige (z. B. lokal signierte) PDF für einen Vorgang hoch. Nur mit ownerKey.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Vorgangs-id. |
| ownerKey | string | yes | ownerKey. |
| pdfBase64 | string | yes | Fertiges PDF. |
No output schema declared.
No examples provided.
envelope_void ~47
Storniert/annulliert einen Signier-Vorgang. Nur mit ownerKey.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Vorgangs-id. |
| ownerKey | string | yes | ownerKey. |
No output schema declared.
No examples provided.
fax_confirm ~46
Nach erfolgter Zahlung: Fax in die Warteschlange geben. Braucht die job_id aus fax_create_checkout.
| Name | Type | Req | Description |
|---|---|---|---|
| jobId | string | yes | job_id aus fax_create_checkout. |
No output schema declared.
No examples provided.
fax_countries ~26
Unterstützte Fax-Zielländer + Hinweise zur E.164-Nummer.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
fax_create_checkout ~116
Startet den bezahlten Faxversand: liefert eine Stripe-Checkout-URL. Der MENSCH bezahlt über diese URL; danach fax_confirm mit der job_id. (Kein kostenloser Direktversand über die KI.)
| Name | Type | Req | Description |
|---|---|---|---|
| filename | string | – | Dateiname (optional). |
| pages | integer | – | Seitenzahl (optional). |
| pdfBase64 | string | yes | Das zu faxende PDF. |
| to | string | yes | Zielnummer in E.164, z. B. +4976339202117. |
No output schema declared.
No examples provided.
fax_ping ~26
Prüft, ob Faxversand verfügbar ist und ob er bezahlt (Stripe) läuft.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
fax_quote ~85
Preis für einen Faxversand. Seitenzahl aus pdfBase64 abgeleitet, wenn nicht angegeben.
| Name | Type | Req | Description |
|---|---|---|---|
| pages | integer | – | Seitenzahl (optional; sonst aus PDF). |
| pdfBase64 | string | – | Das zu faxende PDF (z. B. aus fill_template). |
| to | string | – | Zielnummer E.164 (optional, für Zonenpreis). |
No output schema declared.
No examples provided.
fax_status ~34
Zustellstatus eines Fax (queued/sending/success/failed) per id.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Fax-id. |
No output schema declared.
No examples provided.
fill_pdf ~196
Ein BELIEBIGES (nicht-Katalog-)PDF ausfüllen und optional signieren → fertiges PDF (base64). answers = Feldname→Wert (aus inspect_pdf). Unterschrift wird in erkannte Signaturfelder gesetzt oder per manualPlacement platziert. lang (optional) wählt die Schrift für nicht-lateinische Eingaben (ar/zh/hi/…).
| Name | Type | Req | Description |
|---|---|---|---|
| answers | object | – | Feldname → Wert (String/Boolean). |
| extraText | object | – | – |
| filename | string | – | Dateiname (optional). |
| lang | string | – | Sprachhinweis für die Schrift (z. B. ar, zh, hi) — optional. |
| manualPlacement | object | – | – |
| pdfBase64 | string | yes | Das auszufüllende PDF (base64). |
| signaturePngDataUrl | string | – | Unterschrift als PNG data:-URL (optional). |
No output schema declared.
No examples provided.
fill_template ~242
Vorlage ausfüllen (und optional signieren) → fertiges PDF als base64. answers ist ein Objekt Feldname→Wert (Text/Datum "TT.MM.JJJJ" als String, Checkbox true/false, Radio/Dropdown = Option). Feldnamen vorher mit get_template abfragen.
| Name | Type | Req | Description |
|---|---|---|---|
| account_id | string | – | Guthaben-Konto (nur für ai:true). Fehlt es, wird eins mit 1 € Startguthaben ausgestellt und in der Antwort zurückgegeben. |
| ai | boolean | – | KI-Dokumenterstellung nutzen (kostenpflichtig, 0,20 € vom Guthaben; normales Ausfüllen ist kostenlos). |
| answers | object | – | Feldname → Wert (String oder Boolean). |
| country | string | – | Land ISO-2 für den Rechtsraum-Vermerk (optional). |
| id | string | – | Alternativ: sprachneutrale id (mit lang). |
| lang | string | – | Basissprache, wenn per id adressiert. |
| signaturePngDataUrl | string | – | Unterschrift als PNG data:-URL (optional). |
| slug | string | – | Slug der Vorlage. |
No output schema declared.
No examples provided.
get_provider ~47
Ein Anbieter per id (Kündigungsadresse, Fax, typische Frist).
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | Land: de | at | ch. |
| id | string | yes | Anbieter-id. |
No output schema declared.
No examples provided.
get_template ~146
Details + Feld-Schema einer Vorlage: welche Felder (Name, Typ, Label, Optionen) auszufüllen sind, plus Rechtsraum. Adressierbar per slug ODER per id+lang. Feldnamen sind sprachübergreifend gleich.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | Land ISO-2 für den passenden Rechtsraum. |
| id | string | – | Sprachneutrale Vorlagen-ID (mit lang kombinieren). |
| includeBlankPdf | boolean | – | Blanko-PDF als base64 mitliefern. |
| lang | string | – | Basissprache, wenn per id adressiert. |
| slug | string | – | Global eindeutiger Slug (aus search_templates). |
No output schema declared.
No examples provided.
info ~22
Überblick über Tamgara: Anzahl Vorlagen, Sprachen, Rechtsräume.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
inspect_pdf ~76
Ein BELIEBIGES PDF (base64) analysieren: Seitenzahl/-größen, ausfüllbare Formularfelder (Name, Typ, Label, Optionen), Signaturfelder und Unterschrifts-Positionen. Grundlage zum Ausfüllen fremder PDFs.
| Name | Type | Req | Description |
|---|---|---|---|
| pdfBase64 | string | yes | Das PDF als base64. |
No output schema declared.
No examples provided.
list_categories ~24
Vorlagen-Kategorien mit Anzahl (cancellation, sale, rental, …).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_languages ~29
Alle unterstützten Basissprachen mit Vorlagen-Anzahl, RTL-Flag und Rechtsräumen.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_locales ~25
Alle Locales (Sprache×Land) mit lokalisierter Rechtsphrase.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_providers ~109
Anbieter für Kündigungen (Kündigungsadresse/Fax/Frist). Länder: de, at, ch. Optional Freitextsuche.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Anbieter-Kategorie (optional). |
| country | string | – | Land: "de" | "at" | "ch" (Default de). |
| limit | integer | – | Max. Treffer (Default 25). |
| query | string | – | Freitext über Name/Aliase (min. 2 Zeichen). |
No output schema declared.
No examples provided.
pdf_from_images ~67
Aus einem oder mehreren Bildern (base64 PNG/JPEG) ein PDF bauen — ein Bild pro Seite (Foto/Scan → PDF).
| Name | Type | Req | Description |
|---|---|---|---|
| filename | string | – | Dateiname (optional). |
| images | array | yes | base64-Bilder (mit oder ohne data:-Präfix). |
No output schema declared.
No examples provided.
search_templates ~162
Vorlagen suchen/filtern. Freitext über Titel/Slug/Beschreibung, optional nach Sprache, Land (ISO-2, z. B. "DE", "EG") und Kategorie. Liefert Slugs zum Weiterverwenden.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Kategorie aus list_categories. |
| country | string | – | Ländercode ISO-2 groß, z. B. "DE", "AT", "EG". |
| lang | string | – | Basissprache, z. B. "de", "en", "ar". |
| limit | integer | – | Max. Treffer (1–200, Default 50). |
| query | string | – | Freitext, z. B. "Kündigung" oder "car purchase". |
No output schema declared.
No examples provided.
How do I install the Tamgara MCP server?
Tamgara is a hosted endpoint at https://api.tamgara.com/api/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 · api.tamgara.com
claude mcp add --transport http com-tamgara-tamgara 'https://api.tamgara.com/api/mcp'
What is the Tamgara MCP server?
Tamgara is an MCP server listed in the public MCP registry as com.tamgara/tamgara. Fill in 1,000+ legal PDF templates in many languages, get a signed PDF back. Free, no API key. This page covers its hosted endpoint (https://api.tamgara.com/api/mcp).
Is the Tamgara MCP server safe to use?
Tamgara scores 79 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 Tamgara MCP server expose?
Tamgara exposes 33 tools: info, list_languages, list_locales, list_categories, search_templates, and 28 more. Their descriptions and schemas cost roughly 2,699 tokens of context every time the server is loaded.
Does the Tamgara MCP server require authentication?
No. We connected to Tamgara without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Tamgara MCP server still maintained?
Tamgara 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.