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.

Fynvo Firmenverzeichnis

REMOTE · API.FYNVO.DE

Deutsche Unternehmen nach Leistung, Zertifikat und Umkreis finden, mit Quelle je Angabe.

Available components

+3 this week 77 Trust /100

Last scanned (15 hours ago)

Scores higher than 67% 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 Security63
  • 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 enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
  • 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 Usability59
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1082 tokens (~360/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
  • Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
What we tested

Checks we ran (12)

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

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.

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.

  • 21 Nov 26 +1

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

  • 19 Nov 26 +1

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

  • 16 Nov 26 +1

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

  • 14 Nov 26 +1

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

  • 12 Nov 26 +1

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

  • 10 Nov 26 +1

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

  • 8 Nov 26 +1

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

  • 6 Nov 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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://api.fynvo.de/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=api.fynvo.de CN=YR1,O=Let's Encrypt,C=US 19 Oct 2026 17 Jan 2027 RSA 3072 SHA256-RSA 66f0ed985d37e4807838839ac3ad7d58f94
SANs: api.fynvo.de
CN=YR1,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA a20253f15f2691c05dc1ce13b9bcca4e
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of api.fynvo.de. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
de. DS published 26755 8 Verified
fynvo.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
Header Value
x-content-type-options nosniff
referrer-policy no-referrer

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://api.fynvo.de/mcp Verified 200
http (plaintext) http://api.fynvo.de/mcp Inconclusive 405
MCP tools · 3 exposed · ~983 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
anfrage_senden ~233

Schickt eine Anfrage an ein Unternehmen, im Auftrag des Nutzers. Nur benutzen, wenn der Nutzer das ausdrücklich will: die Anfrage geht an ein echtes Unternehmen. Die E-Mail-Adresse muss vom Nutzer kommen, nicht erfunden sein. Pflicht ist der Slug aus einem Suchtreffer, nicht der Firmenname. Required is the slug from a search result, not the company name. Sends an enquiry to a company on behalf of the user. Only use when the user explicitly asks for it: the enquiry reaches a real company. The email address must come from the user, never be invented.

NameTypeReqDescription
emailstringyesAntwortadresse des Nutzers. The user's reply address.
firmastring–Unternehmen des Absenders, freiwillig. Sender company, optional.
nachrichtstringyesDie Anfrage, 20 bis 5000 Zeichen. The enquiry, 20 to 5000 characters.
namestring–Name des Absenders, freiwillig. Sender name, optional.
slugstringyesDer Slug der Firma. The slug of the company.

No output schema declared.

No examples provided.

firma_abrufen ~119

Liefert das vollständige Profil eines Unternehmens: Adresse, Leistungen, Zertifikate, Registereintrag, Kontakt und zu jedem Feld die Herkunft der Angabe. Pflicht ist der Slug aus einem Suchtreffer, nicht der Firmenname. Required is the slug from a search result, not the company name. Returns the full profile of a company including address, services, certificates, register entry, contact and the provenance of every field.

NameTypeReqDescription
slugstringyesDer Slug aus einem Suchtreffer. The slug from a search result.

No output schema declared.

No examples provided.

firmen_suchen ~631

Sucht deutsche Unternehmen nach Leistung, Zertifikat, Region, Rechtsform, Betriebsgröße oder Freitext. Beantwortet Fragen wie "Wer fräst CNC-Teile aus Edelstahl im Raum Stuttgart und ist nach ISO 9001 zertifiziert?" oder "mittelständischer Fensterbauer in Bayern, seit mindestens zwanzig Jahren am Markt". Die Werte für leistung und zertifikat stammen aus einem festen Vokabular; ist der passende Slug unbekannt, zuerst ohne diese Filter mit q suchen und die Slugs aus den Treffern übernehmen. Ein Oberbegriff bei leistung trifft auch alle Leistungen darunter. groesse und besteht_jahre_min schließen Firmen aus, zu denen die Angabe fehlt; wer breit suchen will, lässt sie weg. Searches German companies by service, certificate, region, legal form, size or free text. Values for leistung and zertifikat come from a fixed vocabulary; if the matching slug is unknown, search with q first and take the slugs from the results. A parent term in leistung also matches all services below it. groesse and besteht_jahre_min exclude companies without that figure.

NameTypeReqDescription
besteht_jahre_mininteger–Nur Firmen, die seit mindestens so vielen Jahren bestehen. Firmen ohne Gründungsjahr bleiben draußen. Only companies in business for at least this many years.
bundeslandstring–Eines der sechzehn Bundesländer in amtlicher Schreibweise, etwa "Baden-Württemberg". One of the sixteen German federal states.
groessestring–Betriebsgröße nach Beschäftigten: kleinst (1-9), klein (10-49), mittel (50-249), gross (ab 250). Firmen ohne Angabe bleiben draußen. Company size by headcount; companies without a figure are excluded.
leistungstring–Slug einer Leistung oder eines Oberbegriffs, etwa "cnc-fraesen" oder "metallbearbeitung". Slug of a service or parent term.
plzstring–Fünf Ziffern für eine genaue Postleitzahl, zwei bis vier Ziffern für eine Region. Five digits for an exact postcode, two to four for a region.
pro_seiteinteger–Treffer je Seite, Standard 20. Results per page, default 20.
qstring–Freitext über Firmenname und Kurzbeschreibung. Free text over company name and short description.
rechtsformstring–Rechtsform des Unternehmens, etwa "GmbH" oder "GmbH & Co. KG". Legal form of the company.
seiteinteger–Seitenzahl ab 1. Page number starting at 1.
umkreis_kminteger–Umkreis um plz in Kilometern. Braucht plz. Radius around plz in kilometres, requires plz.
zertifikatstring–Slug eines Zertifikats, etwa "iso-9001" oder "iatf-16949". Slug of a certificate.

No output schema declared.

No examples provided.

Install

How do I install the Fynvo Firmenverzeichnis MCP server?

Fynvo Firmenverzeichnis is a hosted endpoint at https://api.fynvo.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 · api.fynvo.de

# add to Claude Code
claude mcp add --transport http de-fynvo-verzeichnis 'https://api.fynvo.de/mcp'
Common questions

What is the Fynvo Firmenverzeichnis MCP server?

Fynvo Firmenverzeichnis is an MCP server listed in the public MCP registry as de.fynvo/verzeichnis. Deutsche Unternehmen nach Leistung, Zertifikat und Umkreis finden, mit Quelle je Angabe. This page covers its hosted endpoint (https://api.fynvo.de/mcp).

Is the Fynvo Firmenverzeichnis MCP server safe to use?

Fynvo Firmenverzeichnis scores 77 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 Fynvo Firmenverzeichnis MCP server expose?

Fynvo Firmenverzeichnis exposes 3 tools: firmen_suchen, firma_abrufen, anfrage_senden. Their descriptions and schemas cost roughly 983 tokens of context every time the server is loaded.

Does the Fynvo Firmenverzeichnis MCP server require authentication?

No. We connected to Fynvo Firmenverzeichnis without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Fynvo Firmenverzeichnis MCP server still maintained?

Fynvo Firmenverzeichnis 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 Fynvo Firmenverzeichnis MCP server?

VerifyMCP ran 12 checks on Fynvo Firmenverzeichnis, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Fynvo Firmenverzeichnis: HTTPS. 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.