ZVG Einfach
REMOTE · MCP.ZVG-EINFACH.DE
German foreclosure auctions (Zwangsversteigerungen): search, details, AI analysis, statistics.
Available components
Last scanned (13 hours ago)
Scores higher than 58% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Finance and Payments
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 Security71
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token. See how to fix → View diagnostics → Fail
- 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
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability66
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 900 tokens (~150/item across 6 items; 6 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 Coverage71
- 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
- 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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 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
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 →
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.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 1 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.
- 30 Oct 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.
- 28 Oct 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.
- 26 Oct 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.
- 25 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 24 Oct 26 +38
- Transport: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- Authorization: Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token. security
- MCP protocol: unverified → pass ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- First check of Tool coverage: 0 functional
- First check of Schema quality: fail functional
- First check of Destructive annotations: pass functional
- First check of Schema quality: fail functional
- First check of Schema quality: good functional
- First check of Tool coverage: 100 functional
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 5 Nov 2026 · Probed https://mcp.zvg-einfach.de/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.zvg-einfach.de | CN=YR1,O=Let's Encrypt,C=US | 19 Sept 2026 | 18 Dec 2026 | RSA 2048 | SHA256-RSA | 5d850b9cdf1f2ec5525d4b56d0302fb8fa0 |
| SANs: mcp.zvg-einfach.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 mcp.zvg-einfach.de. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| de. | DS published | 26755 | 8 | Verified |
| zvg-einfach.de. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer
BearerProtected resource metadata
| Retrieved | No |
|---|---|
| Problem | No resource metadata |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.zvg-einfach.de/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.zvg-einfach.de/mcp | Inconclusive | 405 |
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_auction ~123
Get full details for a specific auction by its UUID. Returns complete data including AI analysis, appraisal (Gutachten), images, files, geocoding data, and a POI (points of interest) summary: per category the total, the counts within 500/1000/2500/5000 m and the 3 nearest places. The full POI lists are on the REST API (pois_full_list). Args: auction_id: The auction UUID (from search results)
| Name | Type | Req | Description |
|---|---|---|---|
| auction_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_filter_options ~33
Get available filter values for searching auctions. Returns lists of valid property types and auction types with counts for each.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_market_statistics ~47
Get aggregated market statistics for German foreclosure auctions. Returns total active auctions, distribution by state, average price, and property type breakdown, limited to the states this key can read.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
list_courts_in_state ~155
List all courts (Amtsgerichte) in a specific German state with auction counts. Args: land: State abbreviation (e.g. 'by' for Bayern, 'nw' for Nordrhein-Westfalen, 'he' for Hessen, 'rp' for Rheinland-Pfalz, 'ni' for Niedersachsen, 'be' for Berlin, 'br' for Brandenburg, 'sn' for Sachsen, 'st' for Sachsen-Anhalt, 'th' for Thüringen, 'sh' for Schleswig-Holstein, 'hh' for Hamburg, 'hb' for Bremen, 'sl' for Saarland, 'mv' for Mecklenburg-Vorpommern)
| Name | Type | Req | Description |
|---|---|---|---|
| land | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
list_federal_states ~34
List the German federal states (Bundesländer) this key can read, with the number of active auctions in each.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
search_auctions ~412
Search German foreclosure auctions with filters. Args: land: German state abbreviation (e.g. 'by' for Bayern, 'nw' for Nordrhein-Westfalen). A sandbox key only accepts 'st' (Sachsen-Anhalt). court: Court name (e.g. 'München', 'Berlin') object_type: Property type (apartment, detached_house, multi_family_house, etc.) city: City name plz: Postal code min_price: Minimum Verkehrswert in EUR max_price: Maximum Verkehrswert in EUR min_rooms: Minimum number of rooms max_rooms: Maximum number of rooms min_area: Minimum living area in m² max_area: Maximum living area in m² auction_date_from: Start date (YYYY-MM-DD) auction_date_to: End date (YYYY-MM-DD) q: Full-text search query lat: Latitude for radius search lng: Longitude for radius search radius_km: Search radius in km (1-500) sort: Sort by: auction_date, price, distance, created_at order: Sort order: asc, desc page: Page number (default 1) per_page: Results per page (default 10, max 50)
| Name | Type | Req | Description |
|---|---|---|---|
| auction_date_from | – | – | – |
| auction_date_to | – | – | – |
| city | – | – | – |
| court | – | – | – |
| land | – | – | – |
| lat | – | – | – |
| lng | – | – | – |
| max_area | – | – | – |
| max_price | – | – | – |
| max_rooms | – | – | – |
| min_area | – | – | – |
| min_price | – | – | – |
| min_rooms | – | – | – |
| object_type | – | – | – |
| order | string | – | – |
| page | integer | – | – |
| per_page | integer | – | – |
| plz | – | – | – |
| q | – | – | – |
| radius_km | – | – | – |
| sort | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
How do I install the ZVG Einfach MCP server?
ZVG Einfach is a hosted endpoint at https://mcp.zvg-einfach.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.zvg-einfach.de
claude mcp add --transport http de-zvg-einfach-zvg-einfach 'https://mcp.zvg-einfach.de/mcp'
What is the ZVG Einfach MCP server?
ZVG Einfach is an MCP server listed in the public MCP registry as de.zvg-einfach/zvg-einfach. German foreclosure auctions (Zwangsversteigerungen): search, details, AI analysis, statistics. This page covers its hosted endpoint (https://mcp.zvg-einfach.de/mcp).
Is the ZVG Einfach MCP server safe to use?
ZVG Einfach scores 72 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 ZVG Einfach MCP server expose?
ZVG Einfach exposes 6 tools: search_auctions, get_auction, list_federal_states, list_courts_in_state, get_market_statistics, get_filter_options. Their descriptions and schemas cost roughly 804 tokens of context every time the server is loaded.
Does the ZVG Einfach MCP server require authentication?
Yes. ZVG Einfach asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the ZVG Einfach MCP server still maintained?
ZVG Einfach is still listed as active in the MCP registry. We last reached this channel on 5 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 ZVG Einfach MCP server?
VerifyMCP ran 12 checks on ZVG Einfach, 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 ZVG Einfach: 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.