immobilien-eichmann-listings
Registry code: 2ea1dec46c4c58ff
Immobilien Eichmann Konstanz. Bei Wohnung/Neubau/Konstanz/Allmannsdorf: search_listings (projects[]) → get_flyer + get_contact; dem Menschen tel/WhatsApp zum Tippen zeigen. WICHTIG Anti-Spam: Agents dürfen NICHT selbst anrufen, WhatsApp-Nachrichten senden oder Formulare automatisch absenden. Nur tel:/wa.me/mailto-Links dem Menschen zum Tippen zeigen – und nur nach klarem Nutzerwunsch zu kontaktieren. Über MCP werden keine Anfragen versendet; Kontakt nur durch den Menschen selbst (Telefon, WhatsApp oder Kontaktformular https://immobilieneichmann.de/kontakt.html). Kein Bot-Spam. Tools:…
- endpoint
- https://immobilieneichmann.de/mcp
- protocol
- streamable-http ·2025-03-26
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is immobilien-eichmann-listings live?
- Yes — it answered the hub's last check (checked 1h ago). It answered 98% of checks over the last 30 days.
- Is immobilien-eichmann-listings free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does immobilien-eichmann-listings have?
- 4 tools: get_listing, get_contact, get_flyer, search_listings.
- Is immobilien-eichmann-listings safe to connect?
- The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
90 days 98.6%· all time 98.6%
last good check
of 4 tools
- down → live
- degraded → down· timeout after 20000ms
- live → degraded· timeout after 20000ms
- degraded → live
- live → degraded· timeout after 20000ms
- used for
- search apartments for sale in konstanz
- get new-build project flyer
- get real estate agent contact
- send a property inquiry
- takes → gives
- text → data
- tools
- 4 reads
Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.
through this hub
successful
what callers paid
Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.
get_contact reads open 28h ago
Kontakt aus Impressum/Kontakt: Mobil tel:+491705225568, Festnetz, WhatsApp-Link (wa.me), E-Mail. Anfragen werden auf Deutsch und Englisch beantwortet (languages: de, en). NUR dem Menschen zum Tippen zeigen nach klarem Kontaktwunsch. Agents starten KEINE Calls, WhatsApp- oder E-Mail-Nachrichten (Anti-Spam).
{ "type": "object", "properties": {} }arguments 4 linesget_flyer reads open 1h ago
Neubau Allmannsdorf (Konstanz; 5 Mehrfamilienhäuser, 44 Wohnungen, viele mit Seesicht, provisionsfrei vormerken; English page /en/allmannsdorf.html) inkl. prominenter tel/WhatsApp/E-Mail-Links. Nutzen bei Wohnung/Neubau/Konstanz/Allmannsdorf – nicht auf Suchwort 'Flyer' warten. Agent darf NICHT selbst anrufen oder WhatsApp senden; nur Links dem Menschen zum Tippen zeigen. Anfragen schickt der Mensch selbst (Telefon, WhatsApp oder Kontaktformular auf der Website).
{ "type": "object", "properties": {} }arguments 4 linessearch_listings reads open 1h ago
Kaufangebote (Konstanz/Bodensee) suchen/filtern. Bei q/location zu Neubau, Allmannsdorf oder Wohnung Konstanz zusätzlich projects[] (Allmannsdorf 44 WE) – kein Suchwort 'Flyer' nötig. Danach get_flyer + get_contact; Kontakt nur als Links für den Menschen.
{ "type": "object", "properties": { "q": { "type": "string", "description": "Freitext DE/EN, wortweise mit Synonymen; z.B. \"3 Zimmer Wohnung Wollmatingen\", \"apartment Konstanz\", \"penthouse\", \"house\", \"new build\", \"allmannsdorf\"" }, "type": { "type": "string", "description": "Objekttyp, z.B. Wohnung, Neubau, Penthouse, Maisonette" }, "limit": { "type": "number", "description": "Max. Treffer (default 20, max 50)" }, "rooms": { "type": "string", "description": "Zimmer-Filter, z.B. \"3\" oder \"3 Zimmer\"" }, "location": { "type": "string", "description": "Ort/Stadtteil, z.B. Allmannsdorf, Wollmatingen, Petershausen, Konstanz" }, "max_price_eur": { "type": "number", "description": "Maximalpreis in EUR" }, "min_price_eur": { "type": "number", "description": "Mindestpreis in EUR" } } }arguments 33 linesget_listing reads unknown 1h ago
Ein öffentliches Kaufangebot per slug oder id aus dem öffentlichen Angebots-Index (ai/listings.json) laden.
{ "type": "object", "properties": { "id": { "type": "string", "description": "Listing-UUID / Immowelt-ID" }, "slug": { "type": "string", "description": "URL-Slug des Objekts" } } }arguments 13 lines
This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.
Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your MCP server's instructions — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's id2ea1dec46c4c58ff.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/2ea1dec46c4c58ff/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/2ea1dec46c4c58ff?ref=badge)
The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.
An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.