Assetfy MCP-Server

• Nur lesen
• Ändert und löscht nichts
• Idempotent

Look up a parcel (Flurstück) from the Liegenschaftskataster / Flurkarte and its SIZE (Grundstücksgröße, Flurstücksfläche). This answers "how many m²/qm does Gemarkung X, Flur Y, Flurstück Z have" — the most common cadastral question — and returns area in m², coordinates, gml_id and the cadastral identity (Gemarkung, Flur, Flurstücksnummer). Also searches by postal code with an area range, or within a radius of a coordinate. Covers 15 of the 16 German states, including Brandenburg, Berlin, Bremen and Hamburg — only BAYERN is missing, because its cadastre is not openly licensed; a Bayern lookup answers "No parcel table for Bayern" and says what is available there instead. Do not confuse this coverage with assetfy_db_find_parcels_by_use, assetfy_db_find_industrial_sites or assetfy_db_screen_sites, which are limited to the states reporting the use attribute. Leading zeros are irrelevant: Flur "3" finds "003". A search by gemarkung is resolved through the precomputed Gemarkung index first and then runs geometrically around that Gemarkung — the result reports the zone and its suchradius_m, and an unknown name comes back with did_you_mean instead of a timeout. In the few states not yet in that index the name search still scans the state and can exceed the time limit; adding zip or lat/lon + radius_m avoids that.

Beispiel: Wie groß ist das Flurstück Gemarkung List, Flur 30, Flurstück 44/11 in Hannover?

• Nur lesen
• Ändert und löscht nichts
• Idempotent

Find the cadastral parcel (Flurstück) at a street address or coordinate — what the Flurkarte / Liegenschaftskarte (ALKIS-Kataster) shows there: Gemarkung, Flur, Flurstücksnummer, Grundstücksgröße in m² and the parcel outline. Takes the address directly; the tool resolves it itself.

Beispiel: Welches Flurstück liegt an der Koordinate 48.1986, 16.3417 in Wien?

• Nur lesen
• Ändert und löscht nichts
• Idempotent

Retrieve one cadastral parcel (Flurstück) by its ALKIS GML id: Gemarkung, Flur, Flurstücksnummer, Grundstücksgröße and outline, as in the Flurkarte / Liegenschaftskataster.

• Nur lesen
• Ändert und löscht nichts
• Idempotent

Find cadastral parcels by postal code and plot area. Answers questions like "which parcels in ZIP 12683 have exactly 1026 m2". Use this to map an exposé without a street address to a concrete parcel. The ZIP is matched against the parcel polygons via de_zipcodes geometry, never by town name, and the Bundesland follows from the ZIP — no coordinates needed. Exact area first, then a small tolerance, because exposés round.

• Nur lesen
• Ändert und löscht nichts
• Idempotent

Derive plot shape metrics from the parcel polygon: bounding rectangle (width x depth), all edge lengths, compactness and a street frontage estimate. Answers "Zuschnitt", "Grundstücksbreite/-tiefe", "Grundstücksform" and "erste Reihe / Strassenfront" questions.

• Nur lesen
• Ändert und löscht nichts
• Idempotent

Resolve German place names or postal codes (Ort, Stadt, Gemeinde, PLZ) into search center points with a radius derived from the size of the place. Useful to check how a location will be interpreted before searching; assetfy_search_property_candidates does this resolution itself.

• Nur lesen
• Ändert und löscht nichts
• Idempotent

Full development fact sheet for one parcel in a single call: cadastral identity (Gemarkung/Flur/Flurstueck), area, actual land use (ALKIS), buildings with footprint, Geschosszahl, Gebäudehöhe, Traufhöhe and Firsthöhe über Grund (from LoD2 where available), GRZ/GFZ (Grundflächenzahl/Geschossflächenzahl) existing vs. neighbourhood percentiles, development potential traffic light (Bebauungspotenzial, Nachverdichtung, Aufstockung), B-plan hit, or Paragraph 34/35 BauGB where the municipality is covered by our B-plan data — where it is not (eckdaten.planungsrecht.regime "unbekannt", daten_vorhanden false), the planning law is unknown and no B-plan hit says nothing, Bodenrichtwert incl. zone GFZ, plus computed land value (Grundstückswert) and buildable-BGF (Bruttogeschossfläche) headroom, and Umgebungslärm from the strategic noise maps (umgebungslaerm). Preferred tool for "Eckdaten zur Bebaubarkeit", "was darf ich hier bauen", Baurecht, Baulücke and Innenbereich/Außenbereich. Parcel outline and building footprints as GeoJSON only on request (include_geometry).

Beispiel: Erstelle mir einen Steckbrief zur Bebaubarkeit von Flurstück 44/11 in Hannover-List: GRZ, GFZ, Bodenrichtwert, Gebäude und Potenzial.

• Nur lesen
• Ändert und löscht nichts
• Idempotent

Aggregated profile of one parcel (Flurstück): Kataster data, tatsächliche Nutzung / Grundstücksnutzung, Bodenrichtwert, development potential (Bebaubarkeit, GRZ/GFZ, Nachverdichtung) and every building (Gebäude) on it with function, Geschosszahl (oberirdisch/unterirdisch, flagged when estimated), Gebäudehöhe, Traufhöhe and Firsthöhe über Grund, Dachform, Baujahr, Grundfläche, BGF (Bruttogeschossfläche), Nutzfläche and Volumen, plus Umgebungslärm (noise) from the strategic noise maps. Heights come from the LoD2 3D building models where the state publishes them (e.g. Bayern, Hessen, Berlin, Brandenburg, Sachsen); where a source only has elevations above sea level (Niedersachsen) the fields stay empty.

Beispiel: Welche Gebäude stehen auf Flurstück 44/11 in Hannover-List, mit Geschossen und Höhen?

• Nur lesen
• Ändert und löscht nichts
• Idempotent

Buildings (Gebäude) from the cadastre (ALKIS-Kataster) with their address (Adresse, Hausnummer), function (Gebäudefunktion, e.g. Wohnhaus, Garage, Lagerhalle), floors (Geschosse) and footprint (Gebäudegrundfläche). Either every building on one parcel (gml_id) or all buildings within a radius of a coordinate. Use this to confirm which parcel a listing refers to — the HTTP API does not return addresses. Floors here are the ALKIS attribute only, empty in several states; for Traufhöhe, Firsthöhe, Gebäudehöhe and the Geschosszahl derived from the LoD2 3D models use assetfy_get_parcel_profile or assetfy_get_parcel_overview.

• Nur lesen
• Ändert und löscht nichts
• Idempotent

Bebauungsplan polygons covering a coordinate or a parcel, with plan name, type and date. It is built for the Bebauungsplan. Where a state register also carries the Flächennutzungsplan (e.g. NRW), it comes back as a hit with planart "Flächennutzungsplan"; most states do not publish the FNP as data, and there it is held by the Gemeinde. Use it to prove whether a parcel is governed by a B-plan (then its rules apply) or falls under §34/§35 BauGB — but only where our data covers the municipality: the result reports gemeinde_abdeckung, and where the state or the Gemeinde is not in our B-plan data, beurteilung says so and no hit is NOT evidence of §34. Hessen, Niedersachsen, Bremen, Saarland, Sachsen-Anhalt and Bayern have no B-plan data here at all. Every hit carries planunterlagen: the direct PDF links of that plan — Planzeichnung, textliche Festsetzungen, Begründung, taken from the source record or from the portal pages it links to, in the spelling the municipality publishes them. They belong to that plan. assetfy_get_plan_document returns the content of a document itself, as text and page images; a web fetch of these links is typically refused, as they appear only in a tool result. The links are not checked for reachability, so an occasional one is stale. The list can be empty even for a plan in force: not every municipality publishes its documents, and a few portals need a login. quelle_url is the link the state register itself carries — usually a portal page rather than a document — and is the fallback when planunterlagen is empty. datum belongs to the record, not necessarily to the plan: where the name marks an amendment ("Änderung Nr. 4 des Bebauungsplanes Ma 110", "2. Änderung"), it is the date that amendment took effect, and the original plan is usually older — in NRW it is missing from the register entirely for 5.341 of 6.254 amendments. The amendment date is therefore not the age of the planning law.

Beispiel: Gibt es für den Punkt 50.62618, 6.94504 in Rheinbach einen Bebauungsplan? Zeig mir die Planunterlagen.

• Nur lesen
• Ändert und löscht nichts
• Idempotent

Returns the content of one Bebauungsplan document — Planzeichnung, textliche Festsetzungen, Begründung — fetched by the Assetfy server as text and page images. The url is one from planunterlagen of assetfy_db_planning_at_point (or planzeichnung_pdf / document_links of the other tools), unchanged. Those links point to the municipality's server; a web fetch of a URL that appears only in a tool result is typically refused, while this tool delivers the document inside its result. Pages with a text layer come as text (text_layer: "included", "truncated" or "none"). Pages without one — most plans are scans — come as JPEG images to be read directly. A plan sheet larger than A3 comes as the whole sheet reduced, followed by overlapping tiles of about 1568 px in reading order, each announced with its row and column: the Nutzungsschablonen and printed Festsetzungen of an A0 sheet are legible only in the tiles. One call carries a limited number of images; pages_not_included and more name the pages left out, which a second call with pages returns. noise_mentions names the pages of the whole document whose text layer mentions noise requirements (Lärmpegelbereich, Emissionskontingent, dB(A), DIN 4109 …), with short excerpts, so those pages can be requested directly; pages_without_text_layer were not searched. Only documents Assetfy has on record can be opened, up to 20 MB.

• Nur lesen
• Ändert und löscht nichts
• Idempotent

Bodenrichtwert zones (BORIS, Gutachterausschuss) at a coordinate or parcel, including value per m2 (Bodenwert, Grundstückspreis pro Quadratmeter), reference date (Stichtag), permitted use (Art der Nutzung, e.g. Bauland, Wohnbaufläche, Gewerbe, Acker) and the zone GFZ used for the land value calculation.

Beispiel: Wie hoch ist der Bodenrichtwert für Flurstück 44/11 in Hannover-List?

• Nur lesen
• Ändert und löscht nichts
• Idempotent

Find parcels (Flurstücke) by their actual cadastral use AND several further criteria AT ONCE — the multi-criteria variant of assetfy_db_find_parcels_by_use, and the tool for a site profile rather than a single lookup. Returns only the parcels that pass every criterion: the use, how much of the parcel that use covers, the parcel size, how densely it is already built (Bebauungsgrad), and whether a Bebauungsplan applies. Example: "Lagerflächen, die mindestens 80 % des Flurstücks einnehmen, 10.000 bis 100.000 m², 5 bis 30 % bebaut, mit B-Plan, deutschlandweit". It replaces chaining assetfy_db_find_parcels_by_use with per-parcel calls to assetfy_db_planning_at_point and assetfy_db_buildings: every criterion is evaluated in one database pass, so a nationwide screening costs one call per state instead of three per candidate — chaining is what exhausts the call budget before the last criterion is reached. Every hit reports the measured figures it passed on (nutzung_anteil_prozent, bebauungsgrad_prozent, the Bebauungsplan) so the numbers can be checked, plus assetfy_url. The distance to the nearest Autobahn junction is covered by max_autobahn_km and measured in the database; there is no need to query Overpass or another OSM service for it. Noise from the strategic noise maps is covered by max_laerm_lden_db / max_laerm_lnight_db, and every hit reports its loudest mapped band as umgebungslaerm. The criteria this tool does NOT cover — distance to a substation, to a railway line — apply to the RESULT, not to the search: screen here first, then check the few survivors, or use near_use in assetfy_db_find_parcels_by_use for a second cadastral use nearby. Coverage: the states with their own detailed land-use dataset (see the coverage note in the result); other states record only the coarse use category at the parcel and are reported as skipped rather than silently omitted.

• Nur lesen
• Ändert und löscht nichts
• Idempotent

Search parcels by their ACTUAL cadastral use (ALKIS "tatsächliche Nutzung", also called Nutzungsart, Grundstücksnutzung or Flächennutzung), nationwide or within a region — cemeteries, quarries, sports grounds, landfills, allotments, power stations, industrial land, anything the cadastre records as a use. This is a discovery tool for sites matching a use profile; to look up ONE known parcel by Gemarkung/Flur/Flurstücksnummer or to get its size, use assetfy_db_find_parcels instead, which covers all states. Spelling differences between states are handled: the states write the same use as "Industrie- und Gewerbefläche", "Industrie Und Gewerbeflaeche", "IndustrieUndGewerbeflaeche" or "Industrie und Gewerbe", and any of those spellings finds all of them. Search broadly and with the stem of a word — "friedhof" also finds "Parkfriedhof" and "Historischer Friedhof". Note the coverage: NRW, Hessen, Brandenburg, Mecklenburg-Vorpommern and Baden-Württemberg are searched in their own ALKIS land-use datasets and carry the detailed designation (e.g. "Lagerfläche") plus further attributes such as Zustand; Niedersachsen, Hamburg, Saarland, Sachsen, Sachsen-Anhalt, Thüringen and (sparsely) Rheinland-Pfalz are searched through the coarser parcel attribute, which knows only the main category. Baden-Württemberg records Funktion and Vegetationsmerkmal but no Zustand. Bayern, Berlin, Bremen and Schleswig-Holstein are not covered: their land-use import has not landed yet, and in Schleswig-Holstein the parcel attribute is empty, so the state comes back in skipped_states rather than as an empty result. A nationwide search is therefore not exhaustive, and absence of a hit is not evidence of absence. This tool knows nothing about listings; for railway land that is for sale (Grundstücke mit Gleisanlagen zum Verkauf) use assetfy_db_rail_listings. SEVERAL CRITERIA AT ONCE — a use PLUS a share of the parcel ("must cover at least 80 % of the Flurstück"), a size window, a building coverage (Bebauungsgrad), or a Bebauungsplan — is covered by assetfy_db_screen_sites, which evaluates all of them in one database pass per state. Checking candidates from here one by one with assetfy_db_planning_at_point and assetfy_db_buildings runs out of calls before the last criterion is reached, which is the reason assetfy_db_screen_sites exists. This tool is for a single use as the question: which parcels carry it, where, and how large. If a nationwide search times out on a common use, split it by bundesland rather than retrying — and say in the answer which states you actually covered.

• Nur lesen
• Ändert und löscht nichts
• Idempotent

Search industrial and commercial parcels (Industriefläche, Gewerbegrundstück, Gewerbefläche, Logistikfläche) by their ACTUAL cadastral use — assetfy_db_find_parcels_by_use with the use preset to "Industrie". This is the entry point for finding sites for data centres, battery storage, solar or charging parks: a parcel whose use includes "Versorgungsanlage" or "Umspannstation" already carries grid infrastructure, which is the scarce resource. For any other use — cemeteries, quarries, sports grounds, allotments — use assetfy_db_find_parcels_by_use, which takes a free nutzungsart. Same coverage and same caveats as that tool.

• Nur lesen
• Ändert und löscht nichts
• Idempotent

Railway lines (Bahnstrecken, Gleise) of the German federal rail network from the Infrastrukturregister (ISR) of DB InfraGO: route number (Streckennummer), sections (Streckenabschnitt von–bis, km), number of tracks (eingleisig / zweigleisig), line speed, electrification, traffic type (Personenverkehr, Güterverkehr, S-Bahn), line class, ETCS and TEN classification — plus stations and junctions (Betriebsstellen: Bahnhof, Haltepunkt, Abzweig, Überleitstelle) and, on request, bridges and tunnels and the line geometry. Search by Streckennummer, by a station or section name, by Landkreis, bbox or around a coordinate. Answers "welche Bahnstrecken verlaufen durch X", "wie ist die Strecke 6088 ausgebaut", "wo ist die Strecke eingleisig". For the parcels along a line — the railway land itself and whether there is room for another track — use assetfy_db_rail_corridor_parcels.

• Nur lesen
• Ändert und löscht nichts
• Idempotent

Parcels (Flurstücke) along railway lines whose actual use (tatsächliche Nutzung) is "Bahnverkehr" — the railway land, as a rule owned by DB InfraGO — measured ACROSS the track: how wide that land is beside the outermost existing track, on each side. Answers "welche Bahngrundstücke sind breit genug für ein weiteres Gleis", "wo passt ein Überholgleis / eine Kreuzungsstelle / ein drittes Gleis", "wo reicht der Bahnkorridor für einen Gleisausbau". The line is sampled every step_m with a cross-section (Querprofil); in each, the existing tracks come from the ISR and the free width is the contiguous Bahnverkehr land beyond the outer track. Returns (1) abschnitte: continuous stretches where the free width on one side stays ≥ required_free_width_m for at least min_run_length_m — the candidate sites — with side (e.g. "östlich der Gleise"), length, free width, nearest station and the parcels involved; and (2) flurstuecke: those parcels with Gemarkung/Flur/Flurstück, area, Bahnverkehr share, free width and length along the track. Needs a region (landkreis, lat/lon + radius_m or bbox) and/or strecke_nr; at most 80 km of line per call — split by strecke_nr if the region holds more (the refusal lists the lines). The use comes from the parcel attribute where the state has it, otherwise from the state’s own land-use dataset (NRW, Hessen, Brandenburg, Mecklenburg-Vorpommern, Baden-Württemberg, Berlin, Bayern) and only then live from the state ALKIS WFS; where none exists the parcels the track runs over are used instead, and the result says so (tn_quelle). This is a screening, not a plan: the ISR draws double track schematically 6 m apart (real 4.0–4.5 m, so the real free width is about 1 m larger), station tracks and sidings are not in the ISR, and terrain, embankments, masts and buildings are not considered — check candidates with assetfy_db_buildings, the planning tools and assetfy_get_aerial_image (the start and ende of an abschnitt span its bbox).

• Nur lesen
• Ändert und löscht nichts
• Idempotent

Listings FOR SALE (zum Verkauf) — Grundstücke, Gewerbeobjekte, Häuser and BVVG land from the Assetfy listing stock (real_estates_*) — that involve railway land: alte Gleisanlagen, Gleise, Gleisanschluss, Anschlussgleis, Bahngelände, Bahnbrache, ehemaliger Güterbahnhof, Bahntrasse, Bahndamm, Stellwerk, Lokschuppen. This is the tool that joins the property market with railway and cadastral data; it answers "Grundstücke zum Verkauf mit alten Gleisanlagen", "Gewerbefläche mit Gleisanschluss kaufen", "ehemaliges Bahngelände zu verkaufen". Every hit carries its evidence: (1) the listing names railway facilities — the title, for BVVG also the description; "Bahnhofsnähe", "Bahnhofstraße" or "S-Bahn" do not count; (2) the parcel (Flurstück) under the listing coordinate has the actual use (tatsächliche Nutzung) Bahnverkehr — only where the coordinate is not a locality geocode shared with other listings, and checked against the advertised plot area; (3) the nearest operating line from the Infrastrukturregister (ISR) of DB InfraGO — railway land without an operating line within 100 m points to disused, dismantled, siding or station tracks, and the NRW cadastre adds the state "außer Betrieb, stillgelegt"; (4) where the listing has an exact address with house number (as for the exact markers on the Assetfy map, but not when the geocoder put a business or institution in front of the street — that is the address of a POI, not of the property), its distance to the nearest operating line counts by itself: up to 100 m "stark", up to 500 m "mittel" — proximity to a line, not proof of tracks on the plot. evidenz is "stark", "mittel" or "schwach"; "schwach" — a railway parcel at the coordinate that is much larger than the listing or cannot be compared because the listing states no plot area (usually a geocode on the neighbouring track), or a railway term only in a long BVVG description (usually the transport connection) — is left out unless include_weak is set. Nationwide by default, or within a Landkreis, bbox or radius. The cadastral check runs where the state cadastre in the database carries the actual use; elsewhere only the listing text counts, and the result lists which states were checked. No source says whether tracks are still on site — confirm with the exposé and the aerial image (assetfy_get_aerial_image at the listing coordinate). For railway land that is not on the market use assetfy_db_rail_corridor_parcels or assetfy_db_find_parcels_by_use with nutzungsart "Bahnverkehr".

• Nur lesen
• Ändert und löscht nichts
• Idempotent

Search Assetfy real estate listings around named places and rank them against structured criteria (price, plot and living area, rooms) — the tool for "finde mir eine Wohnung/ein Haus/ein Grundstück in X für unter Y". Takes place names or coordinates plus those criteria and returns a scored shortlist. The free-text query is only echoed back: it neither filters nor ranks, so words like "Gleisanschluss" or "Altbau" in it change nothing. Needs locations or center_points — without a place use assetfy_db_search_listings for the whole listing stock, and assetfy_db_rail_listings for listings involving railway land (alte Gleisanlagen, Gleisanschluss, Bahngelände). Covers listings for sale (Kaufangebote, Verkaufsangebote, Immobilien, Objekte): Wohnung/apartmentbuy, Haus/housebuy, Grundstück/Bauplatz/landbuy, Garage/Stellplatz/garagebuy, Gewerbe/Büro/officebuy, Zwangsversteigerung/official_foreclosure. This searches MARKETED PROPERTIES, not the cadastre: for parcels by Gemarkung/Flur/Flurstücksnummer use assetfy_db_find_parcels, and for parcels by their recorded use use assetfy_db_find_parcels_by_use — neither of those knows anything about prices or listings. Use assetfy_search_real_estates instead when you already have a coordinate and just want what is nearby, without ranking.

• Nur lesen
• Ändert und löscht nichts
• Idempotent

Find real estate listings near a coordinate — Immobilien, Wohnungen, Häuser, Grundstücke, Garagen und Gewerbeobjekte zum Kauf (Kaufangebote, Verkaufsangebote, Inserate, Exposés) in der Umgebung eines Punktes. Returns the listings with price, area, rooms and platform URL. Types are apartmentbuy (Eigentumswohnung), housebuy (Haus), landbuy (Grundstück, Bauplatz), garagebuy (Garage, Stellplatz), officebuy (Gewerbe, Büro). Requires lat/lon and returns by distance, unranked — when the user describes what they want in words or names a town instead of a coordinate, use assetfy_search_property_candidates, which resolves places and scores the results. This tool covers the PROPERTY MARKET, not the cadastre: it does not find parcels by Gemarkung/Flur/Flurstücksnummer (assetfy_db_find_parcels) nor by their recorded use such as Industrie or Friedhof (assetfy_db_find_parcels_by_use), and those cadastral tools carry no prices.

Beispiel: Welche Wohnungen werden in der Nähe von 52.3906, 9.7517 in Hannover zum Kauf angeboten?

• Nur lesen
• Ändert und löscht nichts
• Idempotent

Search real estate listings (Immobilien, Angebote, Inserate, Exposés) directly in the database with structured filters — the tool for "vermietete Wohnungen mit positivem Cashflow", "Zwangsversteigerungen im Raum X", "Garagen unter 20.000 €", "BVVG-Flächen", "Gewerbeobjekte", "Grundstücke ab 800 m²". Pick the market with `type`: housebuy (Haus), apartmentbuy (Eigentumswohnung), landbuy (Grundstück, Bauplatz), garagebuy (Garage, Stellplatz), officebuy (Gewerbe, Büro), agriculture (BVVG-Flächen, landwirtschaftliche Flächen der Bodenverwertungs- und -verwaltungs GmbH). Boolean filters cover the special cases: foreclosure for Zwangsversteigerungen, rented for vermietete Kapitalanlagen, private_offer for Angebote ohne Makler, price_reduced, leasehold for Erbbaurecht. Cashflow, gross yield and return on equity are returned for every hit where the platform reported them. Not every filter exists for every type — BVVG parcels carry no foreclosure or rented flag, only houses and apartments have rooms — and any filter that cannot apply is reported back in ignored_filters instead of being silently dropped. For prices per m² across a whole postcode area rather than single listings, use assetfy_db_price_heatmap; for cadastral parcels rather than marketed properties, use assetfy_db_find_parcels. For listings involving railway land — alte Gleisanlagen, Gleisanschluss, Bahngelände — use assetfy_db_rail_listings, which joins them with the cadastre and the rail network.

• Nur lesen
• Ändert und löscht nichts
• Idempotent

Retrieve one real estate listing (Immobilien-Inserat, Exposé, Angebot) from the Assetfy listing database by its platform URL, e.g. an ImmobilienScout24, Immowelt or Kleinanzeigen link — price, area, rooms, year built, condition, coordinates, images and the full exposé description text (expose.description) where the portal published one. The URL is only the lookup key: the tool never contacts the portal or a portal API, it calls the Assetfy API (GET https://assetfy.com/api/v1/real-estates/by-url), which searches the listings Assetfy has already collected. A listing that is not in that stock returns success false with the reason and the way to match it by its exposé facts instead.

• Nur lesen
• Ändert und löscht nichts
• Idempotent

All stored exposé attributes for a listing URL, including the ones the HTTP API drops: number of floors, construction year, condition, cellar, building type, private/agent offer — plus the platform image URLs. Use it when ZIP + plot area leave several candidate parcels: floors and construction year discriminate, and the images can be inspected for the building type described in the title. Also returns the exposé description text (Beschreibung) where the portal published one — outbuildings, renovation state, rental status, heating and plot details often appear only there. Not available for Zwangsversteigerungen.

• Nur lesen
• Ändert und löscht nichts
• Idempotent

Score a real estate candidate (Immobilienangebot, Exposé) against buyer criteria — Kaufpreis, Grundstücksgröße, Wohnfläche, Zimmer — and optionally enrich it with parcel data (Flurstück, Bodenrichtwert).

• Nur lesen
• Ändert und löscht nichts
• Idempotent

Resolve a real estate listing (Immobilien-Inserat, Exposé) to the cadastral parcel (Flurstück) at the listing's coordinate and assess whether that match is plausible. Input is the listing's platform URL, e.g. an ImmobilienScout24, Immowelt or Kleinanzeigen link. The URL is only the lookup key — the tool never contacts the portal or a portal API. It calls the Assetfy API — GET https://assetfy.com/api/v1/real-estates/by-url for the listing (same lookup as assetfy_get_real_estate, so the listing must be in the Assetfy listing stock), then /api/v1/flurstueck and the /api/v1/grundstueck/{gml_id} endpoints for the parcel. The tool reads the listing coordinate, looks up the Flurstück there in the ALKIS cadastre and adds its parcel profile: area, GFZ/GRZ potential, Bodenrichtwert, buildings and actual land use. match_assessment returns status plausible_match, needs_review, unlikely_match or no_match with a confidence, from comparing the listed plot area with the parcel area and a house listing with the buildings on the parcel. Portal coordinates are often only approximate — when the status is not plausible_match, use assetfy_match_listing_to_parcel, which searches by ZIP and plot area instead.

• Nur lesen
• Ändert und löscht nichts
• Idempotent

Match a real estate listing to the most plausible cadastral parcel and return the full development fact sheet for it. Give either a listing_url or the exposé facts (zip, plot area, living area, floors, building type). Step a) searches the cadastre for parcels with that plot area inside the ZIP polygon — exact area first, then a small tolerance, matched geometrically and never by town name. Coordinates are optional. Step b) runs only when a) leaves more than one candidate: it compares each candidate's buildings against the exposé, ranks them and explains why the others are ruled out. When several candidates still fit, the result says so — confirming the address from photos, public sources or the provider is then up to the caller.

• Nur lesen
• Ändert und löscht nichts
• Idempotent

Asking prices per m² for a postcode area — the data behind the price heatmap on the Assetfy map. Answers "was kostet der Quadratmeter in X", "Preisniveau PLZ Y", "ist das Angebot teuer für die Gegend": average, minimum and maximum €/m² plus the number of listings, separately for Häuser, Wohnungen, Grundstücke and Gewerbe, across roughly 8.000 postcode areas. Based on active portal listings from the last nine months with outliers removed, so it reflects what sellers currently ask, not what buyers paid and not the official land value. For the official Bodenrichtwert of the Gutachterausschuss use assetfy_db_land_values; for the individual listings behind these figures use assetfy_db_search_listings. Requires zip, ort or a coordinate.

• Nur lesen
• Ändert und löscht nichts
• Idempotent

Aerial image (Luftbild, Luftaufnahme, Orthofoto — what users often call a Satellitenbild; digitales Orthophoto DOP20 — 20 cm ground resolution, Bremen and Nordrhein-Westfalen 10 cm) of a location in Germany, fetched live from the official WMS of the state survey office — the imagery of the aerial layer on the Assetfy map. Returns the image itself (JPEG, north up, true to scale) together with its footprint: bbox in WGS84, metres per pixel, state and the required attribution. Use it to check the results of the other tools by eye: whether tracks still lie on railway land from assetfy_db_rail_corridor_parcels or assetfy_db_rail_listings, whether the free strip beside the track is really free (embankment, trees, buildings, masts, roads, station tracks), whether a parcel is built on, what a site looks like. Give either lat/lon with size_m — a square centred on the coordinate — or a bbox [west, south, east, north], e.g. spanned by start and ende of a corridor abschnitt; a bbox is padded by 10 % (at least 25 m) and widened to an aspect ratio of at most 2:1 so the surroundings stay visible. Up to 3000 m edge length per image — split longer stretches. Keep size_m near 100–300 m to see tracks, masts and small buildings; above about 1000 m only the coarse layout remains. Parcel boundaries are not drawn in: relate them through the bbox. The imagery is the state's current flight, as a rule one to three years old; the service supplies no capture date.

Beispiel: Zeig mir ein Luftbild von 50.62618, 6.94504 in Rheinbach.

• Nur lesen
• Ändert und löscht nichts
• Idempotent

Which data this server covers, per German state (Bundesland): Liegenschaftskataster/ALKIS (Flurstücke, Gebäude, tatsächliche Nutzung), Bebauungspläne, Bodenrichtwerte, Luftbilder and real estate listings.

• Nur lesen
• Ändert und löscht nichts
• Idempotent

Which datasets exist in the connected database and how current they are: row counts per category and Bundesland plus the latest import log entries. Mirrors assetfy.com/datenaktualitaet.

• Nur lesen
• Liest das eigene Konto
• Ändert und löscht nichts
• Idempotent

The signed-in user's own map markers ("Meine Orte") with their titles and notes — places the user pinned on the Assetfy map or saved with assetfy_my_places_add. Not the same as assetfy_my_favorites: favourites are saved listings, places are free coordinates. Use it when the user asks about "meine Orte", "meine Marker", what they noted at a place, or before saving a place, to see whether it is already there. Optional lat/lon + radius_m restricts to markers near a point. Identity comes from the access token; there is no way to query another account.

Beispiel: Welche Orte habe ich gespeichert?

• Nur lesen
• Liest das eigene Konto
• Ändert und löscht nichts
• Idempotent

The signed-in user's saved properties ("Favoriten") with their private notes, enriched with the listing data. The notes are the user's own assessment of a property and exist nowhere else — use them when the user asks about "my" properties, what they noted, or wants their saved properties compared. To save a listing as a favourite use assetfy_my_favorites_add. Identity comes from the access token; there is no way to query another account.

Beispiel: Welche Angebote habe ich als Favoriten gespeichert, und was habe ich dazu notiert?

• Speichert im eigenen Konto · braucht mcp:write
• Ändert und löscht nichts
• Idempotent

Save a place with an optional note to the signed-in user's "Meine Orte" on the Assetfy map — a red marker the user sees in their own account. Writes only to the caller's own account and never changes or deletes anything. It is meant for explicit requests from the user to save something. Typical requests: "merk dir den Ort", "leg einen Marker an", "notier dir beim Flurstück …". Give lat/lon, or a gml_id — the marker is then set on the centre of that Flurstück. The title is what the marker is labelled with: use the Lagebezeichnung and/or the Flurstück (e.g. "Flurstück 377, Hauptstraße 12, Neustadt a. d. W."). The note is the user's text, verbatim. Calling it twice with identical input does not create a duplicate. For a listing (an exposé from a portal) use assetfy_my_favorites_add instead. The result carries assetfy_url, which opens the saved marker on the map.

Beispiel: Speichere Flurstück 44/11 in Hannover-List in meinen Orten mit der Notiz „Besichtigung im Oktober“.

• Speichert im eigenen Konto · braucht mcp:write
• Ändert und löscht nichts
• Idempotent

Save a listing to the signed-in user's favourites ("Favoriten", the heart on the Assetfy map), optionally with a note. The counterpart of assetfy_my_favorites. Writes only to the caller's own account. It is meant for explicit requests from the user to save something. Typical requests: "merk dir das Angebot", "pack das in meine Favoriten", "notier dir zu dem Exposé …". Identify the listing by listing_url — the portal link (platform_url) that the listing tools return or the user pasted — or by real_estate_id + real_estate_type as assetfy_my_favorites returns them. Only listings in the Assetfy database can be saved; an unknown URL is reported, not stored. An existing favourite is kept: a new note is APPENDED to the user's note, never replaces it, and an identical note is not added twice. For a free location without a listing use assetfy_my_places_add.