UGC VZ Creator Search
REMOTE · UGC-VZ.DE · 2 COMPONENTS · SCANNED SEP 22
Find real UGC creators in the DACH region: profiles, pricing, reach, outreach. No API key.
Available components
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 Security80
- 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. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- 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 Usability61
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1625 tokens (~325/item across 5 items; 5 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 Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 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
How do I install the UGC VZ Creator Search MCP server?
UGC VZ Creator Search is a hosted endpoint at https://ugc-vz.de/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 · ugc-vz.de
claude mcp add --transport http de-ugc-vz-creator-search 'https://ugc-vz.de/api/mcp'
{
"mcpServers": {
"de-ugc-vz-creator-search": {
"url": "https://ugc-vz.de/api/mcp"
}
}
} {
"servers": {
"de-ugc-vz-creator-search": {
"type": "http",
"url": "https://ugc-vz.de/api/mcp"
}
}
} [mcp_servers.de-ugc-vz-creator-search] url = "https://ugc-vz.de/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"de-ugc-vz-creator-search": {
"type": "remote",
"url": "https://ugc-vz.de/api/mcp",
"enabled": true
}
}
} openclaw mcp add de-ugc-vz-creator-search --url 'https://ugc-vz.de/api/mcp' --transport streamable-http
mcp_servers:
de-ugc-vz-creator-search:
url: "https://ugc-vz.de/api/mcp" {
"McpServers": {
"de-ugc-vz-creator-search": {
"Transport": "http",
"Url": "https://ugc-vz.de/api/mcp"
}
}
} assistant mcp add de-ugc-vz-creator-search -t streamable-http -u 'https://ugc-vz.de/api/mcp'
{
"mcpServers": {
"de-ugc-vz-creator-search": {
"type": "http",
"url": "https://ugc-vz.de/api/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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 Sept 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.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 8 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 5 Sept 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.
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 22 Sept 2026 · Probed https://ugc-vz.de/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=ugc-vz.de | CN=YR1,O=Let's Encrypt,C=US | 1 Aug 2026 | 30 Oct 2026 | RSA 2048 | SHA256-RSA | 515752d005077a62a16d219b4f65d4ac8a0 |
| SANs: ugc-vz.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 ugc-vz.de. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| de. | present | 26755 | 8 | Verified |
| ugc-vz.de. | 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=63072000; includeSubDomains; preload |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline' https://analytics.polymarkt.de; style-src 'self' 'unsafe-inline'; img-src 'self' data: blob: https:; font-src 'self'; connect-src 'self' https://analytics.polymarkt.de; media-src 'self'; frame-src 'self' https://www.youtube-nocookie.com https://www.youtube.com; object-src 'none'; base-uri 'self'; form-action 'self'; frame-ancestors 'none'; upgrade-insecure-requests |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(self), geolocation=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://ugc-vz.de/api/mcp | Verified | 200 | |
| http (plaintext) | http://ugc-vz.de/api/mcp | HTTPS enforced | 308 | https://ugc-vz.de/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 →
get_creator ~250
Returns the public profile of a single UGC creator for a creator_public_id from a previous search_creators result: name, city, topics, industries, preferred content, equipment, experience since, fee and reach text, portfolio links, social accounts and the human_verification level. NEVER returns private contact details such as e-mail or real name - the brand receives those from UGC VZ by e-mail only after request_outreach. Use before request_outreach to inspect a match more closely. [DE] Liefert das oeffentliche Profil eines einzelnen UGC-Creators zu einer creator_public_id aus einem vorherigen search_creators-Ergebnis: Name, Stadt, Themen, Branchen, bevorzugter Content, Ausruestung, Erfahrung seit, Honorar- und Reichweitentext, Portfolio-Links, Social-Accounts sowie die human_verification-Stufe. Gibt NIEMALS private Kontaktdaten wie E-Mail oder echten Namen zurueck - diese erhaelt die Brand erst nach request_outreach per E-Mail von UGC VZ. Vor request_outreach verwenden, um einen Treffer aus search_creators naeher zu pruefen.
| Name | Type | Req | Description |
|---|---|---|---|
| creator_public_id | string | yes | – |
No output schema declared.
No examples provided.
get_outreach_status ~223
Returns the current status of a contact request previously triggered with request_outreach, by request_id: submitted (received, not yet processed), working (e-mail delivery in progress), completed (contact details delivered by e-mail) or failed (delivery failed or 48 hours without delivery). NEVER returns private contact details itself, only the lifecycle status with timestamps. Call repeatedly after request_outreach until the status is completed or failed. [DE] Liefert den aktuellen Status einer zuvor mit request_outreach ausgeloesten Kontaktanfrage anhand der request_id: submitted (eingegangen, noch nicht bearbeitet), working (E-Mail-Versand laeuft), completed (Kontaktdaten wurden per E-Mail zugestellt) oder failed (Versand fehlgeschlagen oder 48 Stunden ohne Zustellung). Gibt NIEMALS private Kontaktdaten selbst zurueck, nur den Lebenszyklus-Status samt Zeitstempeln. Nach request_outreach wiederholt aufrufen, bis der Status completed oder failed ist.
| Name | Type | Req | Description |
|---|---|---|---|
| request_id | string | yes | – |
No output schema declared.
No examples provided.
get_vocab ~231
Returns the currently valid vocabulary for search_creators: most common topics, industries and cities from active creator profiles, the definition of the human_verification levels (0 = self_reported, 1 = self_reported_with_portfolio, 2 = reserved, currently not assigned) and a note on pricing. Contains no creator or contact data. Call before a first search_creators request or when unsure about valid filter values (city, topics, human_verification_level_min). [DE] Liefert das aktuell gueltige Vokabular fuer search_creators: haeufigste Themen (topics), Branchen und Staedte aus aktiven Creator-Profilen sowie die Definition der human_verification-Stufen (0 = self_reported, 1 = self_reported_with_portfolio, 2 = reserviert, wird derzeit nicht vergeben) und einen Hinweis zur Preisgestaltung. Enthaelt keine Creator- oder Kontaktdaten. Vor einer ersten search_creators-Anfrage oder bei Unsicherheit ueber gueltige Filterwerte (city, topics, human_verification_level_min) aufrufen.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
request_outreach ~451
Triggers a deliberate brand request. UGC VZ then forwards the contact details of the selected creators to the brand by e-mail. Required: name, email, creator_public_ids from a previous search. Returns request_id for get_outreach_status. Creators must have been found via search_creators or get_creator before this call; request_outreach itself returns no creator details and no private contact data, only the request_id. message and search_query are optional free-text context for UGC VZ. Typical flow: search_creators -> get_creator -> request_outreach -> get_outreach_status. Call only for serious, genuine requests: the call triggers a real e-mail, and name and email must actually belong to the requesting brand. No bulk requests, no test calls. The terms of use at https://ugc-vz.de/agb (section 10) apply. [DE] Loest eine bewusste Brand-Anfrage aus. UGC VZ gibt daraufhin die Kontaktdaten der ausgewaehlten Creator per E-Mail an die Brand weiter. Pflicht: name, email, creator_public_ids aus vorheriger Suche. Gibt request_id fuer get_outreach_status zurueck. Vor diesem Aufruf muessen die Creator ueber search_creators oder get_creator ermittelt worden sein; request_outreach selbst liefert keine Creator-Details und keine privaten Kontaktdaten zurueck, sondern nur die request_id. message und search_query sind optionale Freitextfelder mit Kontext fuer UGC VZ. Typischer Ablauf: search_creators -> get_creator -> request_outreach -> get_outreach_status. Nur fuer ernsthafte, eigene Anfragen aufrufen: der Aufruf loest einen echten E-Mail-Versand aus, name und email muessen der anfragenden Brand tatsaechlich gehoeren. Keine Massenanfragen, keine Testaufrufe. Es gelten die Nutzungsbedingungen unter https://ugc-vz.de/agb (Ziffer 10).
| Name | Type | Req | Description |
|---|---|---|---|
| creator_public_ids | array | yes | – |
| string | yes | – | |
| message | string | – | – |
| name | string | yes | – |
| search_query | string | – | – |
No output schema declared.
No examples provided.
search_creators ~325
Searches the UGC-VZ directory of real, verified UGC creators in the German-speaking region (DACH). query is free text and the main path (e.g. "fitness creator 30+ for a TikTok product video"); a language model structures the request server-side. Optional: city (substring), topics (at least one match), human_verification_level_min (0 = self_reported, 1 = self_reported_with_portfolio; levels are derived from profile data, see get_vocab). Results NEVER contain private contact details. Use get_creator for details on a match; request_outreach for a contact request. [DE] Durchsucht das UGC-VZ-Verzeichnis realer UGC-Creator im deutschsprachigen Raum. query ist Freitext und der Hauptpfad (z. B. "Fitness-Creatorin ab 30 fuer TikTok-Produktvideo"); ein Sprachmodell strukturiert die Anfrage serverseitig. Optional: city (Substring), topics (mind. ein Treffer), human_verification_level_min (0 = self_reported, 1 = self_reported_with_portfolio; Stufen sind aus Profildaten abgeleitet, siehe get_vocab). Ergebnis enthaelt NIEMALS private Kontaktdaten. Fuer Details zu einem Treffer get_creator verwenden; fuer eine Kontaktanfrage request_outreach.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | – | – |
| human_verification_level_min | integer | – | – |
| max_results | integer | – | – |
| query | string | yes | – |
| topics | array | – | – |
No output schema declared.
No examples provided.
What is the UGC VZ Creator Search MCP server?
UGC VZ Creator Search is an MCP server listed in the public MCP registry as de.ugc-vz/creator-search. Find real UGC creators in the DACH region: profiles, pricing, reach, outreach. No API key. This page covers its hosted endpoint (https://ugc-vz.de/api/mcp).
Is the UGC VZ Creator Search MCP server safe to use?
UGC VZ Creator Search 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 UGC VZ Creator Search MCP server expose?
UGC VZ Creator Search exposes 5 tools: search_creators, get_creator, request_outreach, get_outreach_status, get_vocab. Their descriptions and schemas cost roughly 1,480 tokens of context every time the server is loaded.
Does the UGC VZ Creator Search MCP server require authentication?
No. We connected to UGC VZ Creator Search without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the UGC VZ Creator Search MCP server still maintained?
UGC VZ Creator Search is still listed as active in the MCP registry. We last reached this channel on 22 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.