hammergut-neidberg
https://www.ferien-in-der-saechsischen-schweiz.de
Registry code: ef45efb62e6332b4
Holiday apartments and a holiday house in the historic Hammergut Neidberg (since 1470), Bielatal, Saxon Switzerland, Germany – booked directly with the hosts, no portal fees. Use check_availability for live prices. Only create a booking request after the guest explicitly agreed; the guest must confirm it by e-mail within 15 minutes.
- endpoint
- https://www.ferien-in-der-saechsischen-schweiz.de/mcp.php
- 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 hammergut-neidberg live?
- Yes — it answered the hub's last check (checked 53m ago). It answered 100% of checks over the last 30 days.
- Is hammergut-neidberg free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does hammergut-neidberg have?
- 4 tools: create_booking_request, get_property_info, list_accommodations, check_availability.
- Is hammergut-neidberg 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 100%· all time 100%
last good check
of 4 tools
- unknown → live
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_property_info open 53m ago
Facts about Hammergut Neidberg in Saxon Switzerland, Germany: location, check-in/out, what is included, tourist tax, pets, payment, cancellation and how booking works. Call this first when planning a stay.
{ "type": "object", "properties": {} }arguments 4 lineslist_accommodations open 53m ago
The 5 bookable units (4 apartments in the historic Hammergut + holiday house Waldhaus) with capacity, bedrooms, beds, pets, amenities (German) and photo URLs.
{ "type": "object", "properties": {} }arguments 4 linescheck_availability open 53m ago
Live availability and exact prices (EUR, incl. VAT) for a stay. Returns per unit: available, total price, tourist tax, grand total, minimum stay, next free period if booked, and a pre-filled booking link. Without dates it returns the next free period per unit.
{ "type": "object", "properties": { "lang": { "enum": [ "en", "de", "fr", "cs", "nl", "pl", "it" ], "type": "string", "default": "en", "description": "Language of the guest (texts and booking page)." }, "pets": { "type": "integer", "minimum": 0 }, "adults": { "type": "integer", "minimum": 0, "description": "Adults (18+)" }, "guests": { "type": "integer", "minimum": 0, "description": "Total guests if the age split is unknown" }, "checkin": { "type": "string", "pattern": "^\\d{4}-\\d{2}-\\d{2}$", "description": "Arrival date YYYY-MM-DD" }, "checkout": { "type": "string", "pattern": "^\\d{4}-\\d{2}-\\d{2}$", "description": "Departure date YYYY-MM-DD" }, "children_3_6": { "type": "integer", "minimum": 0 }, "children_7_17": { "type": "integer", "minimum": 0 } } }arguments 51 linescreate_booking_request unknown never probed
Creates a booking request on behalf of the guest for one or more units (ids from list_accommodations / check_availability). Nothing is charged. The guest immediately receives an e-mail and must click the confirmation link within 15 minutes – only then is the booking binding; otherwise it expires. ONLY call this after the guest explicitly asked to book, confirmed unit, dates, guests and the total price, and agreed to the privacy policy (https://www.ferien-in-der-saechsischen-schweiz.de/datenschutz.html). Tell the guest to check the inbox right away.
{ "type": "object", "required": [ "unit_ids", "checkin", "checkout", "adults", "guest", "privacy_consent" ], "properties": { "lang": { "enum": [ "en", "de", "fr", "cs", "nl", "pl", "it" ], "type": "string", "default": "en", "description": "Language of the guest (texts and booking page)." }, "pets": { "type": "integer", "minimum": 0 }, "guest": { "type": "object", "required": [ "name", "email", "street", "zip", "city" ], "properties": { "zip": { "type": "string" }, "city": { "type": "string" }, "name": { "type": "string" }, "email": { "type": "string", "format": "email" }, "phone": { "type": "string" }, "street": { "type": "string" }, "country": { "type": "string" } } }, "adults": { "type": "integer", "minimum": 1 }, "checkin": { "type": "string", "pattern": "^\\d{4}-\\d{2}-\\d{2}$" }, "baby_cot": { "type": "boolean" }, "checkout": { "type": "string", "pattern": "^\\d{4}-\\d{2}-\\d{2}$" }, "unit_ids": { "type": "array", "items": { "type": "string" }, "maxItems": 4, "minItems": 1 }, "high_chair": { "type": "boolean" }, "bike_garage": { "type": "boolean" }, "children_0_2": { "type": "integer", "minimum": 0, "description": "Infants, do not count as guests" }, "children_3_6": { "type": "integer", "minimum": 0 }, "children_7_17": { "type": "integer", "minimum": 0 }, "guests_per_unit": { "type": "array", "items": { "type": "integer" }, "description": "Only for several units: guests per unit in the order of unit_ids" }, "privacy_consent": { "type": "boolean", "const": true, "description": "Guest agreed to the privacy policy" } } }arguments 119 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 idef45efb62e6332b4.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/ef45efb62e6332b4/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/ef45efb62e6332b4?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.