Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

de.flowboxx/agenten-tuer

REMOTE · AGENT.FLOWBOXX.DE

flowboxx Agenten-Tür: ehrliche Antworten zu Websites, Software, KI, Telegram. Anfrage an Menschen.

0 this week 81 Trust /100

Last scanned (16 hours ago)

Scores higher than 79% of remote servers

Reachable. Last reached 21 Nov 2026.

Category CRM and Sales

Trust breakdown (7 categories)

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 Security74
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability69
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 892 tokens (~111/item across 8 items; 8 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 Coverage87
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 62% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 11 Nov 26 0
    • Stability: 0.97 → pass security
  • 10 Nov 26 0
    • Stability: pass → 0.97 functional
  • 9 Nov 26 +2
    • Stability: fail → pass ▲ security
  • 6 Nov 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 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 79 to 83.

  • 24 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 69 to 73.

  • 22 Oct 26 0
    • The server rewrote its instructions, which are the text every model session reads security
  • 12 Oct 26 0
    • Tool “flowboxx_leistungen” rewrote its description, which is the text the model reads security
Diagnostics

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 21 Nov 2026 · Probed https://agent.flowboxx.de/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=agent.flowboxx.de CN=YE1,O=Let's Encrypt,C=US 27 Sept 2026 26 Dec 2026 ECDSA 256 ECDSA-SHA384 56026366f57468f5ecd724fc6d4abaa8aa1
SANs: agent.flowboxx.de
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
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 agent.flowboxx.de. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
de. DS published 26755 8 Verified
flowboxx.de. No DS 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

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://agent.flowboxx.de/mcp Verified 200
http (plaintext) http://agent.flowboxx.de/mcp HTTPS enforced 301 https://agent.flowboxx.de/mcp
MCP tools · 8 exposed · ~855 tokens

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 →

Tool Tokens
betrieb_anfrage ~72

Hinterlässt eine Anfrage direkt bei einem Betrieb aus dem Hub (kennung aus betrieb_suchen). Die Mail geht an den Betrieb selbst.

NameTypeReqDescription
anliegenstringyes–
kennungstringyes–
kontaktstringyesE-Mail oder Telefonnummer
namestringyes–

No output schema declared.

No examples provided.

betrieb_eintragen ~225

Trägt einen Betrieb mit Kontakt in die flowboxx-Kundenliste ein, flowboxx meldet sich. Es entsteht zunächst ein ENTWURF: Erst nach Klick auf den Bestätigungslink (Mail an kontakt_mail, 48 Stunden gültig) wird der Eintrag aktiv und für andere KIs auffindbar. Ohne zustimmung=true wird NICHTS angelegt. Nutzen, wenn eine KI im Auftrag eines Betriebs diesen ansprechbar machen möchte.

NameTypeReqDescription
branchestringyesEine feste Branche, siehe enum
fragenarray––
kontakt_mailstringyesE-Mail-Adresse des Betriebs
leistungenarray––
namestringyes–
ortstringyes–
plzstringyes5-stellige Postleitzahl des Betriebs
sprachestring–Sprachcode, Standard de
websitestring–Optional, wird nur gespeichert, nicht gecrawlt
zustimmungbooleanyesPflicht: true, sonst keine Anlage

No output schema declared.

No examples provided.

betrieb_fragen ~52

Beantwortet eine Frage zu einem bestimmten, bereits gefundenen Betrieb (kennung aus betrieb_suchen), ausschließlich aus dessen eigenen Angaben.

NameTypeReqDescription
kennungstringyes–
textstringyes–

No output schema declared.

No examples provided.

betrieb_suchen ~71

Sucht einen Betrieb im flowboxx-Hub (nur AKTIVE Türen). Nutzen, wenn eine KI für einen Menschen einen bestimmten Betrieb oder ein Angebot in einer Region sucht.

NameTypeReqDescription
ortstring–Ort oder Region, optional
textstringyesBetriebsname oder gesuchte Leistung

No output schema declared.

No examples provided.

flowboxx_anfrage ~158

Hinterlässt eine Kontaktanfrage für einen Menschen bei flowboxx. Nutzen, wenn der Nutzer ausdrücklich Kontakt aufnehmen oder eine Anfrage hinterlassen möchte. kontakt = E-Mail-Adresse ODER Telefonnummer (mindestens eine davon, frei als Text). anliegen darf auch den Firmen- oder Betriebsnamen enthalten, das ist kein eigenes Feld.

NameTypeReqDescription
anliegenstringyesWorum es geht, darf Firma/Betrieb und Details enthalten
gespraechsverlaufobject–Optional: Zusammenfassung und gewählter Vorschlag aus flowboxx_bedarf
kontaktstringyesE-Mail-Adresse oder Telefonnummer, mindestens eine davon als Text
namestringyesName der anfragenden Person

No output schema declared.

No examples provided.

flowboxx_bedarf ~121

Klärt einen freien Kundenwunsch: stellt bis zu drei feste Rückfragen, solange Pflichtangaben fehlen, und liefert danach eine Zusammenfassung mit drei Vorschlägen (klein, mittel, groß) aus dem Leistungsinventar, ohne Preise, Termine oder Machbarkeitszusagen.

NameTypeReqDescription
antwortenobject–Bisherige Antworten auf Rückfragen, Schlüssel = Fragen-Key
briefstringyes–
session_idstring–Optionale Sitzungs-Id des Clients, nur zur Protokollierung

No output schema declared.

No examples provided.

flowboxx_frage ~69

Beantwortet eine einzelne freie Frage zu flowboxx in 2 bis 4 Sätzen, ausschließlich aus dem eigenen Wissen. Bei unbekanntem Thema folgt ein ehrlicher Rückfall statt einer erfundenen Antwort.

NameTypeReqDescription
textstringyesDie Frage, maximal 600 Zeichen.

No output schema declared.

No examples provided.

flowboxx_leistungen ~87

Gibt die strukturierte Liste aller flowboxx-Leistungen zurück (Bereich, Leistung, für wen, Beleg-Link, Status) und, wenn der Betreiber Festpreise veröffentlicht hat, die Angebote mit Preis, Lieferzeit in Werktagen, Verzugsregel und Kündigung. Nutzen, wenn jemand wissen will, was flowboxx anbietet und was es kostet.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Install

How do I install the de.flowboxx/agenten-tuer MCP server?

de.flowboxx/agenten-tuer is a hosted endpoint at https://agent.flowboxx.de/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 · agent.flowboxx.de

# add to Claude Code
claude mcp add --transport http de-flowboxx-agenten-tuer 'https://agent.flowboxx.de/mcp'
Common questions

What is the de.flowboxx/agenten-tuer MCP server?

de.flowboxx/agenten-tuer is an MCP server listed in the public MCP registry as de.flowboxx/agenten-tuer. flowboxx Agenten-Tür: ehrliche Antworten zu Websites, Software, KI, Telegram. Anfrage an Menschen. This page covers its hosted endpoint (https://agent.flowboxx.de/mcp).

Is the de.flowboxx/agenten-tuer MCP server safe to use?

de.flowboxx/agenten-tuer scores 81 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 de.flowboxx/agenten-tuer MCP server expose?

de.flowboxx/agenten-tuer exposes 8 tools: flowboxx_leistungen, flowboxx_frage, flowboxx_anfrage, flowboxx_bedarf, betrieb_suchen, and 3 more. Their descriptions and schemas cost roughly 855 tokens of context every time the server is loaded.

Does the de.flowboxx/agenten-tuer MCP server require authentication?

No. We connected to de.flowboxx/agenten-tuer without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the de.flowboxx/agenten-tuer MCP server still maintained?

de.flowboxx/agenten-tuer is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the de.flowboxx/agenten-tuer MCP server?

VerifyMCP ran 13 checks on de.flowboxx/agenten-tuer, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.