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.

frag.hugo

REMOTE · MCP.FRAGHUGO.DE

GDPR platform: your assistant fills in VVT, TOMs, AVV and DSFA, your DSB reviews them.

Available components

+3 this week 70 Trust /100

Last scanned (22 hours ago)

Scores higher than 55% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Security

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
Transport & Reachability100
Schema Quality & AI Usability64
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 3326 tokens (~237/item across 14 items; 14 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 Management40
  • Stability observed for 12 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
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 14 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 15 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
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.

  • 20 Nov 26 +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.

  • 17 Nov 26 +1

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

  • 15 Nov 26 +1

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

  • 13 Nov 26 +1

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

  • 11 Nov 26 +1

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

  • 10 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 9 Nov 26 65

    First indexed and scored.

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://mcp.fraghugo.de/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=fraghugo.de CN=WE1,O=Google Trust Services,C=US 28 Oct 2026 26 Jan 2027 ECDSA 256 ECDSA-SHA256 7467bd3c91bcc5b90eac81a662253937
SANs: fraghugo.de, mcp.fraghugo.de, *.mcp.fraghugo.de
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp.fraghugo.de. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
de. DS published 26755 8 Verified
fraghugo.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
strict-transport-security max-age=31536000; includeSubDomains; preload
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://mcp.fraghugo.de/mcp Verified 200
http (plaintext) http://mcp.fraghugo.de/mcp HTTPS enforced 301 https://mcp.fraghugo.de/mcp
MCP tools · 14 exposed · ~3,110 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
check_email_security ~139

Checks the public DNS records that protect a domain against e-mail spoofing: SPF, DKIM (common selectors), DMARC, DNSSEC, MTA-STS, TLS-RPT, BIMI and CAA. Returns an overall assessment, one finding per check and recommendations. Use it for a company domain, not for single mailboxes. Nothing is stored. Rate limited per connection.

NameTypeReqDescription
domainstringyesPublic domain name, e.g. "example.de" (an e-mail address or URL is reduced to its domain)
sprachestring–Output language. Default: German if the input is German, otherwise English.
NameTypeReqDescription
anbieterstring|nullyesDetected mail provider, if any
domainstringyes–
empfehlungenarrayyes–
geprueft_amstringyes–
gesamtobjectyes–
gespeichertbooleanyesNothing about this check is stored by frag.hugo
hinweisstring|nullyes–
linkstringyes–
pruefungenarrayyes–

No examples provided.

check_software_gdpr ~145

Looks up whether frag.hugo has reviewed a software or cloud service for GDPR use in companies (contract partner, data processing agreement, subprocessors, data location, third-country transfer, AI training, certificates, admin controls, deletion, data subject rights). Returns the published verdict with evidence links, or, if the service has not been reviewed, the ten criteria to check yourself. It never estimates a verdict for unreviewed services.

NameTypeReqDescription
namestringyesName of the software or cloud service, e.g. "Canva", "ChatGPT"
sprachestring–Output language. Default: German if the input is German, otherwise English.
NameTypeReqDescription
dienststring|nullyesName of the reviewed service, if found
geeigneter_tarifstring|nullyes–
geprueftstring|nullyes–
gesuchtstringyes–
herstellerstring|nullyes–
kriterienarrayyes–
kriterien_zum_selbst_pruefenarrayyes–
kurzurteilstring|nullyesgeeignet | mit-auflagen | ungeeignet (only if reviewed)
linkstringyes–
naechste_pruefungstring|nullyes–
quelleobjectyes–
statusstringyes–
ungeeignetstring|nullyes–
urteilstring|nullyes–

No examples provided.

create_data_subject_request ~329

Logs a data subject request (access, erasure, rectification, restriction, portability, objection) in the connected frag.hugo account and calculates the one-month deadline of Art. 12(3) GDPR. Step 1 (without `bestaetigung`): preview with the deadline, the possible extension, a note on identity verification and a reply draft from the frag.hugo templates, plus a confirmation value valid for 15 minutes. Step 2 (same input plus `bestaetigung`): creates the request; the data protection officer on file is notified. It does not send anything to the requesting person. Use only for requests addressed to the user’s own organisation.

NameTypeReqDescription
artstringyesType of request: access (Art. 15), erasure (17), rectification (16), restriction (18), portability (20), objection (21)
beschreibungstring–What the person asks for, in short
bestaetigungstring–Value from the preview. Omit it to get the preview; send it unchanged to log the request.
eingegangen_amstringyesDate the request was received (YYYY-MM-DD). Starts the one-month deadline. Not in the future.
kanalstringyesHow the request arrived
kontaktstringyesE-mail address or postal address for the reply
namestringyesName of the requesting person as given in the request
sprachestring–Output language. Default: German if the input is German, otherwise English.
NameTypeReqDescription
antwortentwurf–––
app_linkstring––
benachrichtigtarray––
bestaetigungstring––
dsar_idstring––
felderobject––
friststringyesDeadline for the answer (YYYY-MM-DD), one month from receipt
gueltig_bisstring––
identitaetspruefung_hinweisstring––
schrittstringyes–
verlaengerung_moeglichobject––
wiederholtboolean––
wird_benachrichtigtarray––

No examples provided.

find_supervisory_authority ~212

Finds the competent German data protection supervisory authority by federal state, postcode (PLZ) of the main establishment or authority ID, with competence, website, key figures from the latest activity report (with evidence links), focus topics and notes for SMEs. In Bavaria, public bodies are supervised by BayLfD, companies by BayLDA. If a postcode spans two states, it asks back. Not for authorities outside Germany.

NameTypeReqDescription
behoerde_idstring–Authority ID from this tool
bundeslandstring–German federal state, name or code (e.g. "Bayern", "BY") or "Bund"
oeffentliche_stelleboolean–true for public bodies (only matters in Bavaria: BayLfD instead of BayLDA)
plzstring–German postcode (PLZ) of the main establishment, 5 digits
sprachestring–Output language. Default: German if the input is German, otherwise English.
NameTypeReqDescription
behoerde–yes–
quelleobjectyes–
rueckfrage–yes–
statusstringyes–

No examples provided.

get_compliance_deadlines ~250

Lists dated compliance deadlines from the frag.hugo deadline calendar (GDPR, NIS2, AI Act, CRA, DORA, Data Act, accessibility act and more), each with legal provision, status, what to do and the official source. Without date filters it returns the next upcoming deadlines from today. Not for deadlines of an individual company (data breach, data subject request); those need an account.

NameTypeReqDescription
bisstring–To date (YYYY-MM-DD)
gesetzstring–Law (Gesetz) key, e.g. "nis2", "ai-act", "dsgvo"
limitinteger–Number of results, 1–30 (default 10)
sprachestring–Output language. Default: German if the input is German, otherwise English.
statusstring–in-kraft = in force, kommt = upcoming, verschoben = postponed, entwurf = draft
vonstring–From date (YYYY-MM-DD). Default: today, unless "status" is set
zielgruppestring–Target group (Zielgruppe); deadlines for "alle" are always included
NameTypeReqDescription
fristenarrayyes–
gesamtintegeryes–
naechste_pruefungstring|nullyesDate of the next scheduled review of the calendar
quelleobjectyes–
standstringyes–

No examples provided.

get_cyber_threat_picture ~166

Summarises how many organisations from Germany ransomware groups have named on their leak sites in the last 30 days or 12 months, by industry and group, with the frag.hugo monthly assessment and method. Counts are perpetrator claims from the RansomLook inventory (CIRCL, CC BY 4.0), not confirmed incidents. Not for looking up individual victims.

NameTypeReqDescription
branchestring–Industry (Branche), e.g. "Industrie", "Gesundheitswesen"
sprachestring–Output language. Default: German if the input is German, otherwise English.
zeitraumstring–30t = last 30 days, 12m = last 12 months (default 30t)
NameTypeReqDescription
branche–yes–
branchenarrayyes–
datenquelleobjectyes–
einordnung–yes–
gruppenarrayyes–
hinweisstringyes–
kennzahlenobjectyes–
methodikstringyes–
quelleobjectyes–
standstringyes–
zeitraumstringyes–

No examples provided.

get_subprocessor_changes ~161

Shows the subprocessor lists of 17 widely used cloud providers (Microsoft 365, Google Workspace, AWS, Salesforce, HubSpot, Stripe and others) as monitored daily by frag.hugo: date of the last change, number of entries, names and links to the official list and the data processing agreement. Use it to check whether a provider changed its subprocessors since a given date. Not for providers outside these 17.

NameTypeReqDescription
anbieterstring–Provider ID; without it all 17 monitored providers are listed
seitstring–Only providers whose subprocessor list changed on or after this date (YYYY-MM-DD)
sprachestring–Output language. Default: German if the input is German, otherwise English.
NameTypeReqDescription
anbieterarrayyes–
gesamtintegeryes–
quelleobjectyes–
standstringyes–

No examples provided.

get_website_check_result ~97

Returns the result of a website check started with start_website_check: status per category and up to eight most important findings with explanation, or "still running". Only scans started through this connector within the last 24 hours can be fetched.

NameTypeReqDescription
scan_idstringyesscan_id returned by start_website_check
sprachestring–Output language. Default: German if the input is German, otherwise English.
NameTypeReqDescription
ergebnis–yes–
linkstringyesFull report in the browser on check.fraghugo.de (runs the check there again)
scan_idstringyes–
statusstringyes–
urlstring|nullyes–
wartezeit_s–yes–

No examples provided.

my_privacy_deadlines ~179

Lists the open data protection deadlines of the organisation connected to this frag.hugo account: data breaches with their 72-hour reporting deadline (Art. 33 GDPR), data subject requests with their one-month deadline (Art. 12(3) GDPR, incl. extensions) and records of processing or processor agreements waiting for review by the data protection officer. Returns type, deadline, status and an app link per entry — no descriptions, names or contact details. Requires a connected frag.hugo account. Not for deadlines of laws in general (use get_compliance_deadlines).

NameTypeReqDescription
artstring–Which deadlines: data breaches (72 h), data subject requests (one month), entries awaiting DPO review, or all
sprachestring–Output language. Default: German if the input is German, otherwise English.
NameTypeReqDescription
anfragen–yes–
datenpannen–yesnull = not requested or no permission
freigaben–yes–
linkstringyes–
ohne_rechtarrayyes–
organisationstringyesOrganisation bound to this connection

No examples provided.

plan_software_introduction ~363

Prepares the data protection paperwork for introducing a new software or cloud service in the connected frag.hugo account. Step 1 (without `bestaetigung`): preview with the frag.hugo GDPR test result for the service (if reviewed), the matching template for the record of processing activities (Verarbeitungsverzeichnis) and what will be created, plus a confirmation value valid for 15 minutes. Step 2 (same input plus `bestaetigung`): creates a record of processing entry and a processor agreement (AVV) entry, both submitted for review by the data protection officer. It does not approve the software and does not contact the vendor.

NameTypeReqDescription
abteilungenarray–Departments that will use it
anbieterstring–Vendor, if known
bestaetigungstring–Value from the preview. Omit it to get the preview; send it unchanged to create the entries.
betroffenearray–Groups of persons concerned (e.g. "Beschäftigte", "Kunden")
datenartenarray–Kinds of personal data processed (e.g. "Kontaktdaten", "Chatnachrichten")
softwarestringyesName of the software or cloud service (e.g. "Slack", "HubSpot")
sprachestring–Output language. Default: German if the input is German, otherwise English.
startstring–Planned start (YYYY-MM-DD)
vorlage_refstring–Choose one of the templates offered in the preview (`vvt_vorlage.ref` or one of `weitere`) if the purpose fits better
zweckstringyesWhat the software will be used for
NameTypeReqDescription
app_linksarray––
avv_idstring––
benachrichtigtarray––
bestaetigungstring––
dsbstring|null––
felderobject––
gueltig_bisstring––
pruefstand–––
schrittstringyes–
vvt_idstring––
vvt_vorlage–––
wiederholtboolean––
wird_angelegtarray––

No examples provided.

report_data_breach ~444

Records a personal data breach in the connected frag.hugo account and starts the 72-hour deadline of Art. 33 GDPR. Step 1 (without `bestaetigung`): returns a preview with the deadline, the competent supervisory authority of the organisation, missing mandatory details for that authority, a draft report in the order of the authority form and the reporting channel, plus a confirmation value valid for 15 minutes. Step 2 (same input plus `bestaetigung`): creates the breach as a draft in frag.hugo; the company admins and the data protection officer are notified. It does not submit anything to the authority and does not decide whether reporting is required. Use only when the user wants to record a breach of their own organisation.

NameTypeReqDescription
anzahl_betroffeneinteger–Approximate number of affected persons
anzahl_unbekanntboolean–true if the number of affected persons is not yet known
beschreibungstringyesWhat happened, in plain words (20–4,000 characters). Avoid names of affected persons.
bestaetigungstring–Value from the preview. Omit it to get the preview; send it unchanged to create the breach.
betroffene_datenarray–Categories of personal data affected
entdeckt_amstringyesWhen the organisation became aware of the breach, ISO 8601 with time zone (e.g. 2026-10-28T09:30:00+01:00). Starts the 72-hour deadline. Not in the future.
kategorien_personenarray–Categories of data subjects
massnahmenstring–Measures already taken
risikostringyesRisk to the rights and freedoms of persons as assessed by the organisation; "unklar" if not yet assessed
sprachestring–Output language. Default: German if the input is German, otherwise English.
uebungboolean–true = practice case (drill): no deadline reminders, no notifications
vorfall_typarrayyesType(s) of incident
NameTypeReqDescription
app_linkstring––
behoerde_freitextstring|null––
benachrichtigtarray––
bestaetigungstring––
breach_idstring––
entwurf_meldungstring–Draft for the report under Art. 33(3) GDPR, in the order of the authority form
fehlende_pflichtfelder_der_behoerdearray––
felderobject––
friststringyesEnd of the 72-hour reporting deadline (UTC)
gueltig_bisstring––
meldeweg–––
schrittstringyes–
uebungbooleanyes–
wiederholtboolean––
wird_benachrichtigtarray––
zustaendige_behoerde–––

No examples provided.

search_gdpr_fines ~281

Searches the frag.hugo database of documented GDPR fines (Germany and Europe), each case with authority, amount, GDPR articles, a short summary and the official source. Use it for questions such as "which fines were imposed for Art. 32" or "fines against telecom companies in Germany". Not for legal advice in an individual case and not for fines under other laws. Results are sorted by date, newest first.

NameTypeReqDescription
artikelstring–GDPR article, e.g. "Art. 32" or "32"
betrag_minnumber–Minimum fine in EUR
bisinteger–To year (inclusive)
branchestring–Industry (Branche), e.g. "Telekommunikation"
bundeslandstring–German federal state (Bundesland) or "Bund"
landstring–Country, ISO 3166-1 alpha-2, e.g. DE, IE, FR
limitinteger–Number of results, 1–20 (default 10)
sprachestring–Output language. Default: German if the input is German, otherwise English.
suchestring–Free text: company, facts, authority (max. 100 chars)
voninteger–From year (inclusive)
NameTypeReqDescription
gesamtintegeryesTotal number of matching cases
quelleobjectyes–
standstringyes–
trefferarrayyes–

No examples provided.

start_website_check ~156

Starts the free frag.hugo website check (Hugo Check) for a public URL: cookies and tracking before consent, consent banner, Google Fonts, privacy policy and imprint, TLS and security headers, e-mail records, accessibility and shop duties. Returns the result directly if it is ready within about 20 seconds, otherwise a scan_id for get_website_check_result. The same URL within one hour returns the same scan. Limited to 3 new checks per hour per connection. Not legal advice.

NameTypeReqDescription
sprachestring–Output language. Default: German if the input is German, otherwise English.
urlstringyesPublic website address, http or https, e.g. "https://www.example.de"
NameTypeReqDescription
ergebnis–yes–
linkstringyesFull report in the browser on check.fraghugo.de (runs the check there again)
scan_idstringyes–
statusstringyes–
urlstring|nullyes–
wartezeit_s–yes–
wiederverwendetbooleanyestrue = same URL was checked within the last hour; that scan is returned

No examples provided.

vendor_profile ~188

Collects what frag.hugo publishes about a vendor for a due-diligence note: e-mail security of its domain, the GDPR review verdict if one exists, the subprocessor monitor entry, documented GDPR fines matched by company name, incidents published on fraghugo.de, and optionally a website check. It gives no overall grade and does not judge the vendor; each item carries its own source. Use the company name for better fine matching.

NameTypeReqDescription
domainstringyesMain domain of the vendor, e.g. "stripe.com"
firmennamestring–Company name (Firmenname) for matching fines and incidents
sprachestring–Output language. Default: German if the input is German, otherwise English.
website_pruefenboolean–Also start a website check (Hugo Check) of the domain; counts against its hourly limit
NameTypeReqDescription
bussgelderarrayyes–
domainstringyes–
firmennamestring|nullyes–
gesamtnotenullyesDeliberately none: each line stands with its own source
lagebildarrayyes–
mail_sicherheit–yes–
pruefstand–yes–
quellen_standobjectyesAs-of date per data export used
subprozessor_monitorarrayyes–
website_check–yes–

No examples provided.

Install

How do I install the frag.hugo MCP server?

frag.hugo is a hosted endpoint at https://mcp.fraghugo.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 · mcp.fraghugo.de

# add to Claude Code
claude mcp add --transport http de-fraghugo-frag-hugo 'https://mcp.fraghugo.de/mcp'
Common questions

What is the frag.hugo MCP server?

frag.hugo is an MCP server listed in the public MCP registry as de.fraghugo/frag.hugo. GDPR platform: your assistant fills in VVT, TOMs, AVV and DSFA, your DSB reviews them. This page covers its hosted endpoint (https://mcp.fraghugo.de/mcp).

Is the frag.hugo MCP server safe to use?

frag.hugo scores 70 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 frag.hugo MCP server expose?

frag.hugo exposes 14 tools: search_gdpr_fines, get_compliance_deadlines, check_software_gdpr, get_subprocessor_changes, find_supervisory_authority, and 9 more. Their descriptions and schemas cost roughly 3,110 tokens of context every time the server is loaded.

Does the frag.hugo MCP server require authentication?

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

Is the frag.hugo MCP server still maintained?

frag.hugo 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 frag.hugo MCP server?

VerifyMCP ran 13 checks on frag.hugo, 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.