_ registry / mcp http-sse · checked 3h ago

wanakahaus

https://wanakahaus.nz

Registry code: eb42d79c8dec72b3

api record

Direct booking for Wanaka Haus, an Architectural Passive home in Wānaka, New Zealand (sleeps 8, NZ$950/night + NZ$180 cleaning, GST included). Typical flow: search_availability → get_quote → create_booking → hand the returned checkout_url to the user for payment → get_booking to confirm. No API key or account is needed. Payment happens only on the hosted Stripe Checkout page — never ask the user for card details.

endpoint
https://wanakahaus.nz/api/mcp
protocol
http-sse ·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 it live, free and safe measured by this hub
Is wanakahaus live?
Yes — it answered the hub's last check (checked 3h ago). It answered 99% of checks over the last 30 days.
Is wanakahaus free to use?
Yes — the hub reached it with no key and no payment.
What tools does wanakahaus have?
5 tools: get_quote, cancel_booking, get_booking, create_booking, search_availability.
Is wanakahaus 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.
reachable
live
uptime, 30 days
99.4%

90 days 99.3%· all time 99.3%

latency
278ms

last good check

priced tools
0

of 5 tools

_ answered our checks, 90 days 278 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
used for
  • check holiday home availability
  • get stay quote
  • book a holiday home
  • cancel a booking
takes → gives
data → data
tools
3 reads2 changes data
_ usage and payments 30 days

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.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 5 tools
1 open 4 never probed 1 of 5 classified

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_availability reads open 25h ago

    Open and booked nights for Wanaka Haus (sleeps 8, Wānaka NZ) in a date window, up to 18 months ahead. Ranges are check-in inclusive, check-out exclusive.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "to": {
          "type": "string",
          "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
          "description": "Window end, YYYY-MM-DD. Defaults to 18 months out."
        },
        "from": {
          "type": "string",
          "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
          "description": "Window start, YYYY-MM-DD. Defaults to today."
        }
      }
    }
    arguments 16 lines
  • get_quote reads unknown 25h ago

    Itemised NZD total for a stay at Wanaka Haus. Validates the stay rules (minimum nights, peak-season minimum, guest cap) and checks the dates are open, before you commit to a booking.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "check_in",
        "check_out",
        "guests"
      ],
      "properties": {
        "guests": {
          "type": "integer",
          "maximum": 8,
          "minimum": 1
        },
        "check_in": {
          "type": "string",
          "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
          "description": "YYYY-MM-DD"
        },
        "check_out": {
          "type": "string",
          "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
          "description": "YYYY-MM-DD, exclusive — the morning the guests leave"
        }
      }
    }
    arguments 26 lines
  • cancel_booking changes data unknown never probed

    Cancel a Wanaka Haus booking under the published policy (full refund to 14 days before arrival, 50% to 7 days, none inside 7). Requires the guest email the booking was made with.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "id",
        "guest_email"
      ],
      "properties": {
        "id": {
          "type": "string"
        },
        "guest_email": {
          "type": "string",
          "format": "email",
          "pattern": "^(?!\\.)(?!.*\\.\\.)([A-Za-z0-9_'+\\-\\.]*)[A-Za-z0-9_+-]@([A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$",
          "description": "Must match the email the booking was made with"
        }
      }
    }
    arguments 19 lines
  • get_booking reads unknown never probed

    Status of a Wanaka Haus booking: held, confirmed, cancelled or lapsed.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "id"
      ],
      "properties": {
        "id": {
          "type": "string",
          "description": "The booking id, e.g. bk_1a2b3c4d5e6f"
        }
      }
    }
    arguments 13 lines
  • create_booking changes data unknown never probed

    Book Wanaka Haus: atomically holds the dates for 30 minutes and returns a Stripe Checkout URL. The booking confirms only when payment completes on that URL — give it to your user to pay (or pay with an agent wallet's one-time card). No account or API key needed.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "check_in",
        "check_out",
        "guests",
        "guest_name",
        "guest_email"
      ],
      "properties": {
        "notes": {
          "type": "string",
          "maxLength": 2000
        },
        "guests": {
          "type": "integer",
          "maximum": 8,
          "minimum": 1
        },
        "check_in": {
          "type": "string",
          "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
          "description": "YYYY-MM-DD"
        },
        "check_out": {
          "type": "string",
          "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
          "description": "YYYY-MM-DD"
        },
        "guest_name": {
          "type": "string",
          "maxLength": 200,
          "minLength": 2,
          "description": "The guest's full name"
        },
        "guest_email": {
          "type": "string",
          "format": "email",
          "pattern": "^(?!\\.)(?!.*\\.\\.)([A-Za-z0-9_'+\\-\\.]*)[A-Za-z0-9_+-]@([A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$",
          "description": "The guest's real email — confirmation and door code go here, and it is required to cancel"
        }
      }
    }
    arguments 44 lines
_ try it through the hub, ceiling 0

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.

_ is this your agent? claim it: badge, payouts, history

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.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. 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.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id eb42d79c8dec72b3.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/eb42d79c8dec72b3/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/eb42d79c8dec72b3/badge.svg)](https://brick.blue/agent/eb42d79c8dec72b3?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.

_ how we know
card completeness
90%

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.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
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.