# frag.hugo (remote · mcp.fraghugo.de)

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

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

## Components

- remote · `mcp.fraghugo.de`: 70/100 (this document), [markdown](https://verifymcp.io/servers/de-fraghugo-frag-hugo/mcp.md), [page](https://verifymcp.io/servers/de-fraghugo-frag-hugo/mcp)

## Channel facts

- Endpoint: `https://mcp.fraghugo.de/mcp`
- 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-21.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (report_data_breach).
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - 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**: 64/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 40/100
  - Stability observed for 12 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.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 14 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 15 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## 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.

### Claude

```bash
claude mcp add --transport http de-fraghugo-frag-hugo 'https://mcp.fraghugo.de/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "de-fraghugo-frag-hugo": {
      "url": "https://mcp.fraghugo.de/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "de-fraghugo-frag-hugo": {
      "type": "http",
      "url": "https://mcp.fraghugo.de/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.de-fraghugo-frag-hugo]
url = "https://mcp.fraghugo.de/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "de-fraghugo-frag-hugo": {
      "type": "remote",
      "url": "https://mcp.fraghugo.de/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add de-fraghugo-frag-hugo --url 'https://mcp.fraghugo.de/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  de-fraghugo-frag-hugo:
    url: "https://mcp.fraghugo.de/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "de-fraghugo-frag-hugo": {
      "Transport": "http",
      "Url": "https://mcp.fraghugo.de/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add de-fraghugo-frag-hugo -t streamable-http -u 'https://mcp.fraghugo.de/mcp'
```

### Other

```json
{
  "mcpServers": {
    "de-fraghugo-frag-hugo": {
      "type": "http",
      "url": "https://mcp.fraghugo.de/mcp"
    }
  }
}
```

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-20 (score 70, +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-11-17 (score 69, +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.

### 2026-11-15 (score 68, +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.

### 2026-11-13 (score 67, +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.

### 2026-11-11 (score 66, +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.

### 2026-11-10 (score 65, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-09 (score 65)

First indexed and scored.

## MCP tools (14)

### `search_gdpr_fines` (~281 tokens)

Search GDPR fines (DSGVO-Bußgelder)

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.

Input parameters:

- `artikel` (string): GDPR article, e.g. "Art. 32" or "32"
- `betrag_min` (number): Minimum fine in EUR
- `bis` (integer): To year (inclusive)
- `branche` (string): Industry (Branche), e.g. "Telekommunikation"
- `bundesland` (string): German federal state (Bundesland) or "Bund"
- `land` (string): Country, ISO 3166-1 alpha-2, e.g. DE, IE, FR
- `limit` (integer): Number of results, 1–20 (default 10)
- `sprache` (string): Output language. Default: German if the input is German, otherwise English.
- `suche` (string): Free text: company, facts, authority (max. 100 chars)
- `von` (integer): From year (inclusive)

Output parameters:

- `gesamt` (integer): Total number of matching cases
- `quelle` (object)
- `stand` (string)
- `treffer` (array)

### `get_compliance_deadlines` (~250 tokens)

Compliance deadlines (Fristenkalender)

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.

Input parameters:

- `bis` (string): To date (YYYY-MM-DD)
- `gesetz` (string): Law (Gesetz) key, e.g. "nis2", "ai-act", "dsgvo"
- `limit` (integer): Number of results, 1–30 (default 10)
- `sprache` (string): Output language. Default: German if the input is German, otherwise English.
- `status` (string): in-kraft = in force, kommt = upcoming, verschoben = postponed, entwurf = draft
- `von` (string): From date (YYYY-MM-DD). Default: today, unless "status" is set
- `zielgruppe` (string): Target group (Zielgruppe); deadlines for "alle" are always included

Output parameters:

- `fristen` (array)
- `gesamt` (integer)
- `naechste_pruefung` (string|null): Date of the next scheduled review of the calendar
- `quelle` (object)
- `stand` (string)

### `check_software_gdpr` (~145 tokens)

Check software for GDPR fitness (DSGVO-Prüfstand)

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.

Input parameters:

- `name` (string, required): Name of the software or cloud service, e.g. "Canva", "ChatGPT"
- `sprache` (string): Output language. Default: German if the input is German, otherwise English.

Output parameters:

- `dienst` (string|null): Name of the reviewed service, if found
- `geeigneter_tarif` (string|null)
- `geprueft` (string|null)
- `gesucht` (string)
- `hersteller` (string|null)
- `kriterien` (array)
- `kriterien_zum_selbst_pruefen` (array)
- `kurzurteil` (string|null): geeignet | mit-auflagen | ungeeignet (only if reviewed)
- `link` (string)
- `naechste_pruefung` (string|null)
- `quelle` (object)
- `status` (string)
- `ungeeignet` (string|null)
- `urteil` (string|null)

### `get_subprocessor_changes` (~161 tokens)

Subprocessor changes (Subprozessor-Monitor)

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.

Input parameters:

- `anbieter` (string): Provider ID; without it all 17 monitored providers are listed
- `seit` (string): Only providers whose subprocessor list changed on or after this date (YYYY-MM-DD)
- `sprache` (string): Output language. Default: German if the input is German, otherwise English.

Output parameters:

- `anbieter` (array)
- `gesamt` (integer)
- `quelle` (object)
- `stand` (string)

### `find_supervisory_authority` (~212 tokens)

Find data protection authority (Aufsichtsbehörde)

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.

Input parameters:

- `behoerde_id` (string): Authority ID from this tool
- `bundesland` (string): German federal state, name or code (e.g. "Bayern", "BY") or "Bund"
- `oeffentliche_stelle` (boolean): true for public bodies (only matters in Bavaria: BayLfD instead of BayLDA)
- `plz` (string): German postcode (PLZ) of the main establishment, 5 digits
- `sprache` (string): Output language. Default: German if the input is German, otherwise English.

Output parameters:

- `behoerde`
- `quelle` (object)
- `rueckfrage`
- `status` (string)

### `get_cyber_threat_picture` (~166 tokens)

Ransomware situation Germany (Cyber-Lagebild)

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.

Input parameters:

- `branche` (string): Industry (Branche), e.g. "Industrie", "Gesundheitswesen"
- `sprache` (string): Output language. Default: German if the input is German, otherwise English.
- `zeitraum` (string): 30t = last 30 days, 12m = last 12 months (default 30t)

Output parameters:

- `branche`
- `branchen` (array)
- `datenquelle` (object)
- `einordnung`
- `gruppen` (array)
- `hinweis` (string)
- `kennzahlen` (object)
- `methodik` (string)
- `quelle` (object)
- `stand` (string)
- `zeitraum` (string)

### `check_email_security` (~139 tokens)

Check email security of a domain (SPF, DKIM, DMARC)

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.

Input parameters:

- `domain` (string, required): Public domain name, e.g. "example.de" (an e-mail address or URL is reduced to its domain)
- `sprache` (string): Output language. Default: German if the input is German, otherwise English.

Output parameters:

- `anbieter` (string|null): Detected mail provider, if any
- `domain` (string)
- `empfehlungen` (array)
- `geprueft_am` (string)
- `gesamt` (object)
- `gespeichert` (boolean): Nothing about this check is stored by frag.hugo
- `hinweis` (string|null)
- `link` (string)
- `pruefungen` (array)

### `start_website_check` (~156 tokens)

Start website privacy check (Hugo Check)

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.

Input parameters:

- `sprache` (string): Output language. Default: German if the input is German, otherwise English.
- `url` (string, required): Public website address, http or https, e.g. "https://www.example.de"

Output parameters:

- `ergebnis`
- `link` (string): Full report in the browser on check.fraghugo.de (runs the check there again)
- `scan_id` (string)
- `status` (string)
- `url` (string|null)
- `wartezeit_s`
- `wiederverwendet` (boolean): true = same URL was checked within the last hour; that scan is returned

### `get_website_check_result` (~97 tokens)

Get website check result (Hugo Check)

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.

Input parameters:

- `scan_id` (string, required): scan_id returned by start_website_check
- `sprache` (string): Output language. Default: German if the input is German, otherwise English.

Output parameters:

- `ergebnis`
- `link` (string): Full report in the browser on check.fraghugo.de (runs the check there again)
- `scan_id` (string)
- `status` (string)
- `url` (string|null)
- `wartezeit_s`

### `vendor_profile` (~188 tokens)

Vendor due-diligence profile (Lieferanten-Steckbrief)

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.

Input parameters:

- `domain` (string, required): Main domain of the vendor, e.g. "stripe.com"
- `firmenname` (string): Company name (Firmenname) for matching fines and incidents
- `sprache` (string): Output language. Default: German if the input is German, otherwise English.
- `website_pruefen` (boolean): Also start a website check (Hugo Check) of the domain; counts against its hourly limit

Output parameters:

- `bussgelder` (array)
- `domain` (string)
- `firmenname` (string|null)
- `gesamtnote` (null): Deliberately none: each line stands with its own source
- `lagebild` (array)
- `mail_sicherheit`
- `pruefstand`
- `quellen_stand` (object): As-of date per data export used
- `subprozessor_monitor` (array)
- `website_check`

### `my_privacy_deadlines` (~179 tokens)

My open privacy deadlines (Fristen meiner Firma)

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).

Input parameters:

- `art` (string): Which deadlines: data breaches (72 h), data subject requests (one month), entries awaiting DPO review, or all
- `sprache` (string): Output language. Default: German if the input is German, otherwise English.

Output parameters:

- `anfragen`
- `datenpannen`: null = not requested or no permission
- `freigaben`
- `link` (string)
- `ohne_recht` (array)
- `organisation` (string): Organisation bound to this connection

### `report_data_breach` (~444 tokens)

Report a data breach (Datenpanne, Art. 33 GDPR)

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.

Input parameters:

- `anzahl_betroffene` (integer): Approximate number of affected persons
- `anzahl_unbekannt` (boolean): true if the number of affected persons is not yet known
- `beschreibung` (string, required): What happened, in plain words (20–4,000 characters). Avoid names of affected persons.
- `bestaetigung` (string): Value from the preview. Omit it to get the preview; send it unchanged to create the breach.
- `betroffene_daten` (array): Categories of personal data affected
- `entdeckt_am` (string, required): When 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_personen` (array): Categories of data subjects
- `massnahmen` (string): Measures already taken
- `risiko` (string, required): Risk to the rights and freedoms of persons as assessed by the organisation; "unklar" if not yet assessed
- `sprache` (string): Output language. Default: German if the input is German, otherwise English.
- `uebung` (boolean): true = practice case (drill): no deadline reminders, no notifications
- `vorfall_typ` (array, required): Type(s) of incident

Output parameters:

- `app_link` (string)
- `behoerde_freitext` (string|null)
- `benachrichtigt` (array)
- `bestaetigung` (string)
- `breach_id` (string)
- `entwurf_meldung` (string): Draft for the report under Art. 33(3) GDPR, in the order of the authority form
- `fehlende_pflichtfelder_der_behoerde` (array)
- `felder` (object)
- `frist` (string): End of the 72-hour reporting deadline (UTC)
- `gueltig_bis` (string)
- `meldeweg`
- `schritt` (string)
- `uebung` (boolean)
- `wiederholt` (boolean)
- `wird_benachrichtigt` (array)
- `zustaendige_behoerde`

### `create_data_subject_request` (~329 tokens)

Log a data subject request (Betroffenenanfrage, Art. 15–22 GDPR)

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.

Input parameters:

- `art` (string, required): Type of request: access (Art. 15), erasure (17), rectification (16), restriction (18), portability (20), objection (21)
- `beschreibung` (string): What the person asks for, in short
- `bestaetigung` (string): Value from the preview. Omit it to get the preview; send it unchanged to log the request.
- `eingegangen_am` (string, required): Date the request was received (YYYY-MM-DD). Starts the one-month deadline. Not in the future.
- `kanal` (string, required): How the request arrived
- `kontakt` (string, required): E-mail address or postal address for the reply
- `name` (string, required): Name of the requesting person as given in the request
- `sprache` (string): Output language. Default: German if the input is German, otherwise English.

Output parameters:

- `antwortentwurf`
- `app_link` (string)
- `benachrichtigt` (array)
- `bestaetigung` (string)
- `dsar_id` (string)
- `felder` (object)
- `frist` (string): Deadline for the answer (YYYY-MM-DD), one month from receipt
- `gueltig_bis` (string)
- `identitaetspruefung_hinweis` (string)
- `schritt` (string)
- `verlaengerung_moeglich` (object)
- `wiederholt` (boolean)
- `wird_benachrichtigt` (array)

### `plan_software_introduction` (~363 tokens)

Introduce new software (VVT entry and DPA review)

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.

Input parameters:

- `abteilungen` (array): Departments that will use it
- `anbieter` (string): Vendor, if known
- `bestaetigung` (string): Value from the preview. Omit it to get the preview; send it unchanged to create the entries.
- `betroffene` (array): Groups of persons concerned (e.g. "Beschäftigte", "Kunden")
- `datenarten` (array): Kinds of personal data processed (e.g. "Kontaktdaten", "Chatnachrichten")
- `software` (string, required): Name of the software or cloud service (e.g. "Slack", "HubSpot")
- `sprache` (string): Output language. Default: German if the input is German, otherwise English.
- `start` (string): Planned start (YYYY-MM-DD)
- `vorlage_ref` (string): Choose one of the templates offered in the preview (`vvt_vorlage.ref` or one of `weitere`) if the purpose fits better
- `zweck` (string, required): What the software will be used for

Output parameters:

- `app_links` (array)
- `avv_id` (string)
- `benachrichtigt` (array)
- `bestaetigung` (string)
- `dsb` (string|null)
- `felder` (object)
- `gueltig_bis` (string)
- `pruefstand`
- `schritt` (string)
- `vvt_id` (string)
- `vvt_vorlage`
- `wiederholt` (boolean)
- `wird_angelegt` (array)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/de-fraghugo-frag-hugo/mcp#diagnostics

## Score history

- 2026-11-21: 70
- 2026-11-20: 70
- 2026-11-19: 69
- 2026-11-18: 69
- 2026-11-17: 69
- 2026-11-16: 68
- 2026-11-15: 68
- 2026-11-14: 67
- 2026-11-13: 67
- 2026-11-12: 66
- 2026-11-11: 66
- 2026-11-10: 65
- 2026-11-09: 65

## 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.

## Links

- Remote endpoint: https://mcp.fraghugo.de/mcp
- Repository: https://github.com/Jens-KI-007/fraghugo-claude-plugin
- Website: https://www.fraghugo.de/en/ai-assistant/
- Changelog RSS feed: https://verifymcp.io/servers/de-fraghugo-frag-hugo/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/de-fraghugo-frag-hugo/mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/de-fraghugo-frag-hugo/mcp.json
- HTML version of this page: https://verifymcp.io/servers/de-fraghugo-frag-hugo/mcp
