schweden-ferienhaeuser-ferienhaus-api
https://www.schweden-ferienhaeuser.de
Registry code: c7e1e409c699106b
Read-only MCP tools for searching Schweden-Ferienhäuser vacation rentals, supported search fields, public property details, and availability/pricing with direct booking links.
from a public catalogue that lists it, not from the operator
- endpoint
- https://www.schweden-ferienhaeuser.de/api/mcp
- protocol
- streamable-http ·2025-06-18
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is schweden-ferienhaeuser-ferienhaus-api live?
- Yes — it answered the hub's last check (checked 4h ago). It answered 98% of checks over the last 30 days.
- Is schweden-ferienhaeuser-ferienhaus-api free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does schweden-ferienhaeuser-ferienhaus-api have?
- 4 tools: get_property, check_availability, search_properties, get_object_search_fields.
- Is schweden-ferienhaeuser-ferienhaus-api 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.9%· all time 98.9%
last good check
of 4 tools
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- used for
- search swedish vacation rentals
- check holiday house availability and price
- get holiday house details
- takes → gives
- text, data → 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.
search_properties reads open 13h ago
Sucht oeffentliche Ferienhaeuser nach Gaesten, Reisedaten, Ort, Region, Kategorie, Ausstattung und weiteren Filtern.
{ "type": "object", "properties": { "end": { "type": "string", "description": "Abreisedatum im Format YYYY-MM-DD." }, "dogs": { "type": "integer", "description": "Anzahl Hunde." }, "page": { "type": "integer", "description": "Seitennummer." }, "sort": { "enum": [ "price_asc", "price_desc", "rating", "newest" ], "type": "string", "description": "Sortierung." }, "group": { "type": "string", "description": "Kommagetrennte Objektgruppen-Slugs aus get_object_search_fields." }, "place": { "type": "string", "description": "Kommagetrennte Ort-Slugs aus get_object_search_fields." }, "start": { "type": "string", "description": "Anreisedatum im Format YYYY-MM-DD." }, "guests": { "type": "integer", "description": "Anzahl Personen." }, "offers": { "type": "boolean", "description": "Nur Objekte mit Angeboten." }, "region": { "type": "string", "description": "Kommagetrennte Region-Slugs aus get_object_search_fields." }, "search": { "type": "string", "description": "Freitextsuche." }, "feature": { "type": "string", "description": "Kommagetrennte Merkmal-Slugs aus get_object_search_fields." }, "bedrooms": { "type": "integer", "description": "Mindestanzahl Schlafzimmer." }, "category": { "type": "string", "description": "Kommagetrennte Kategorie-Slugs aus get_object_search_fields." }, "per_page": { "type": "integer", "description": "Ergebnisse pro Seite, maximal 100." }, "equipment": { "type": "string", "description": "Kommagetrennte Ausstattungs-Slugs aus get_object_search_fields." }, "locations": { "type": "string", "description": "Kommagetrennte Lagefilter aus get_object_search_fields." } } }arguments 79 linesget_object_search_fields reads open 13h ago
Gibt Suchparameter und erlaubte Listenwerte fuer die Ferienhaus-Suche zurueck.
{ "type": "object", "properties": [] }arguments 4 linesget_property reads unknown 4h ago
Gibt oeffentliche Detailinformationen fuer ein einzelnes Ferienhaus zurueck.
{ "type": "object", "required": [ "identifier" ], "properties": { "identifier": { "type": "string", "description": "Sichtbare Objekt-ID oder URL-Slug." } } }arguments 12 linescheck_availability reads unknown 13h ago
Prueft Verfuegbarkeit, Preis, enthaltene Leistungen und direkten Checkout-Link fuer ein Objekt und einen Reisezeitraum.
{ "type": "object", "required": [ "identifier", "start", "end", "guests" ], "properties": { "end": { "type": "string", "description": "Abreisedatum im Format YYYY-MM-DD." }, "dogs": { "type": "integer", "description": "Anzahl Hunde." }, "start": { "type": "string", "description": "Anreisedatum im Format YYYY-MM-DD." }, "guests": { "type": "integer", "description": "Anzahl Personen." }, "identifier": { "type": "string", "description": "Sichtbare Objekt-ID oder URL-Slug." } } }arguments 31 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 idc7e1e409c699106b.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/c7e1e409c699106b/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/c7e1e409c699106b?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.