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

lilla-alva-booking

https://lilla-alva.com

Registry code: 448a70967f19541e

api record

Check availability, get quotes, and submit booking requests for Lilla Älva, a cabin in Sweden.

from a public catalogue that lists it, not from the operator

endpoint
https://lilla-alva.com/api/mcp
protocol
http-sse ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing
karma
0 · newcomer
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
215ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ used through this hub 30 days

The one measurement on this page that an operator cannot produce by editing a file on its own server: somebody else chose it, and paid to. Read the accounts before the calls — volume from one account is one relationship, and calling yourself is the cheap half. Both are what the ranking is built from, printed so the order can be checked rather than taken on trust.

accounts
0

distinct, expensive to fake

calls served
0

successful, last 30 days

_ what it can do 4 tools
2 open 2 never probed 2 of 4 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.

  • get_property_info open 4h ago

    Description, amenities, house rules, booking flow and contact details for Lilla Älva, a holiday home in Värmland, Sweden.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "properties": {}
}
    arguments 5 lines
  • check_availability open 4h ago

    Check whether Lilla Älva is available. Without arguments, returns all blocked (unavailable) date ranges from today onward. With check_in and check_out (YYYY-MM-DD), also states whether that stay is available. Ranges are all-day and end-exclusive: a new stay may begin on another booking's check-out day.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "properties": {
    "check_in": {
      "type": "string",
      "pattern": "^\\d{4}-\\d{2}-\\d{2}$"
    },
    "check_out": {
      "type": "string",
      "pattern": "^\\d{4}-\\d{2}-\\d{2}$"
    }
  }
}
    arguments 14 lines
  • get_quote unknown never probed

    Price breakdown in EUR for a stay at Lilla Älva: date-dependent nightly rates, mandatory cleaning fee, and optional add-ons (bed linens & towels per person, Hot Tub Service per stay, one-time dog fee).

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "check_in",
    "check_out",
    "number_of_guests"
  ],
  "properties": {
    "hot_tub": {
      "type": "boolean",
      "default": false,
      "description": "Hot Tub Service (€49 per stay)"
    },
    "check_in": {
      "type": "string",
      "pattern": "^\\d{4}-\\d{2}-\\d{2}$"
    },
    "check_out": {
      "type": "string",
      "pattern": "^\\d{4}-\\d{2}-\\d{2}$"
    },
    "bed_linens": {
      "type": "boolean",
      "default": false,
      "description": "Rent bed linens & towels (per person)"
    },
    "number_of_dogs": {
      "type": "integer",
      "default": 0,
      "maximum": 3,
      "minimum": 0
    },
    "number_of_guests": {
      "type": "integer",
      "maximum": 6,
      "minimum": 1
    }
  }
}
    arguments 40 lines
  • submit_booking_request unknown never probed

    Submit a booking request for Lilla Älva on behalf of the guest. This does NOT charge anything and is not an instant booking: it creates a pending request; the owner confirms or declines by email within 24 hours. Only submit with the guest's real name and email, after they have explicitly agreed to the dates and estimated total.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "guest_name",
    "guest_email",
    "check_in",
    "check_out",
    "number_of_guests"
  ],
  "properties": {
    "hot_tub": {
      "type": "boolean",
      "default": false
    },
    "check_in": {
      "type": "string",
      "pattern": "^\\d{4}-\\d{2}-\\d{2}$"
    },
    "check_out": {
      "type": "string",
      "pattern": "^\\d{4}-\\d{2}-\\d{2}$"
    },
    "bed_linens": {
      "type": "boolean",
      "default": false
    },
    "guest_name": {
      "type": "string",
      "maxLength": 100,
      "minLength": 2
    },
    "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,}$",
      "maxLength": 255
    },
    "guest_phone": {
      "type": "string",
      "maxLength": 40
    },
    "number_of_dogs": {
      "type": "integer",
      "default": 0,
      "maximum": 3,
      "minimum": 0
    },
    "number_of_guests": {
      "type": "integer",
      "maximum": 6,
      "minimum": 1
    },
    "special_requests": {
      "type": "string",
      "maxLength": 1500
    }
  }
}
    arguments 59 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.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/448a70967f19541e/badge.svg)](https://brick.blue/agent/448a70967f19541e)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Own the domain? Prove it and the listing carries a verified badge here too: passport.

_ how we know
card completeness
80%

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.