_ registry / mcp streamable-http · checked 1h ago

aegeanbot

https://app.aegeanbot.com

Registry code: ba23cd3aab312c0f

api record

Search and compare direct-booking vacation homes across Greece. Use search_listings first, then pass a returned listing_id or exact name to detail and availability tools. Never invent dates, party size, budget, availability, or price. Public sessions expose only read-only catalog tools; reservation and operational tools require scoped auth.

endpoint
https://app.aegeanbot.com/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 it live, free and safe measured by this hub
Is aegeanbot live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is aegeanbot free to use?
Yes — the hub reached it with no key and no payment.
What tools does aegeanbot have?
5 tools: check_availability_and_price, get_faq_answer, get_listing_details, get_listing_policies, search_listings.
Is aegeanbot 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
100%

90 days 99.5%· all time 99.5%

latency
207ms

last good check

priced tools
0

of 5 tools

_ answered our checks, 90 days 436 checks · signed record
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
topic
maps travel & places travel & transport
used for
  • search vacation rentals in greece
  • check availability and price for dates
  • get listing policies
  • answer questions about a stay
takes → gives
text → data
tools
5 reads
_ 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_listings reads open 23h ago

    Search available vacation rentals across Greece. Pass explicit destinations, dates, guest counts and filters as structured fields; use query only for preferences not represented by another field. Do not invent locations, dates, guest counts or budgets the guest never gave. Results include stable listing ids for follow-up calls (get_listing_details, check_availability_and_price).

    mcp-tool

    {
  "type": "object",
  "required": [],
  "properties": {
    "mood": {
      "enum": [
        "beach",
        "pools",
        "sunset",
        "night"
      ],
      "type": "string",
      "description": "holiday-mood collection: beach=steps from the sea/coves, pools=private pool/resort calm, sunset=golden-hour terraces/romance, night=chora/town stays with evening life"
    },
    "sort": {
      "enum": [
        "recommended",
        "price_low_to_high",
        "price_high_to_low"
      ],
      "type": "string",
      "description": "result ordering; default recommended"
    },
    "query": {
      "type": "string",
      "description": "optional free-text preferences NOT captured by the structured filters, e.g. 'quiet romantic vibe with sunset views' — do not repeat structured information here"
    },
    "adults": {
      "type": "integer",
      "minimum": 1,
      "description": "number of adult guests"
    },
    "guests": {
      "type": "integer",
      "description": "total guests (alternative to adults/children when the split is unknown)"
    },
    "checkin": {
      "type": "string",
      "format": "date",
      "description": "exact arrival date YYYY-MM-DD — ONLY when the guest gave real stay dates. If they only named a month/season ('in August'), leave dates out: availability is checked per night, so a whole month demands 30 free nights"
    },
    "infants": {
      "type": "integer",
      "minimum": 0,
      "description": "number of infants — noted but NOT counted toward sleeping capacity"
    },
    "setting": {
      "enum": [
        "island",
        "city",
        "mountain",
        "countryside",
        "beachfront"
      ],
      "type": "string",
      "description": "geography facet for generic wishes: 'στα νησιά'/'the islands' → island; combinable with budget/dates, replaces a location guess"
    },
    "bedrooms": {
      "type": "integer",
      "minimum": 1,
      "description": "minimum bedrooms requested"
    },
    "checkout": {
      "type": "string",
      "format": "date",
      "description": "exact departure date YYYY-MM-DD — same rule as checkin"
    },
    "children": {
      "type": "integer",
      "minimum": 0,
      "description": "number of children — counted toward capacity together with adults"
    },
    "currency": {
      "enum": [
        "EUR"
      ],
      "type": "string",
      "description": "currency used for price filters"
    },
    "location": {
      "type": "string",
      "description": "a PLACE the guest actually named: city, island, region, island complex ('Cyclades') or area ('Athens south coast'). For generic geography ('the islands', 'the mountains', 'by the sea') use setting instead — do NOT guess a region the guest never said. Omit if unknown"
    },
    "amenities": {
      "type": "array",
      "items": {
        "enum": [
          "private_pool",
          "pool",
          "heated_pool",
          "jacuzzi_hot_tub",
          "sea_view",
          "beachfront",
          "parking",
          "private_parking",
          "air_conditioning",
          "wifi",
          "full_kitchen",
          "washing_machine",
          "garden",
          "bbq",
          "balcony_terrace",
          "workspace",
          "baby_cot",
          "high_chair"
        ],
        "type": "string"
      },
      "description": "hard amenity requirements the guest explicitly asked for — every listed amenity must be present"
    },
    "bathrooms": {
      "type": "number",
      "minimum": 1,
      "description": "minimum bathrooms requested"
    },
    "near_metro": {
      "type": "boolean",
      "description": "true only when the guest wants to be near a metro/subway station (Athens & Thessaloniki only) — filters to homes within a 1 km walk of a station"
    },
    "property_type": {
      "enum": [
        "villa",
        "apartment",
        "house",
        "studio",
        "maisonette"
      ],
      "type": "string",
      "description": "requested property type"
    },
    "max_total_price": {
      "type": "number",
      "minimum": 0,
      "description": "maximum total stay price (EUR) when the guest gave a whole-trip budget — only applied when exact dates are also given (otherwise ignored with a note)"
    },
    "max_nightly_price": {
      "type": "number",
      "minimum": 0,
      "description": "maximum accommodation price per night (EUR)"
    }
  },
  "additionalProperties": false
}
    arguments 143 lines
  • check_availability_and_price reads unknown 15h ago

    Exact availability + total price for one listing and concrete dates, with the direct booking link.

    mcp-tool

    {
  "type": "object",
  "required": [
    "listing",
    "checkin",
    "checkout"
  ],
  "properties": {
    "checkin": {
      "type": "string",
      "description": "YYYY-MM-DD — never in the past; bare day numbers in a follow-up ('26 to 29') keep the month/year already under discussion, NOT the current month"
    },
    "listing": {
      "type": "string"
    },
    "checkout": {
      "type": "string",
      "description": "YYYY-MM-DD"
    }
  }
}
    arguments 21 lines
  • get_faq_answer reads unknown 15h ago

    Retrieve the host's own Q&A entries most relevant to a factual question about the stay, the house, or the host's services. Prefer this over guessing for any host-specific question.

    mcp-tool

    {
  "type": "object",
  "required": [
    "question"
  ],
  "properties": {
    "question": {
      "type": "string"
    },
    "listing_id": {
      "type": "string",
      "description": "scope to one listing (optional)"
    }
  }
}
    arguments 15 lines
  • get_listing_details reads unknown 23h ago

    Full facts for ONE listing already in play (amenities, description, capacity, base price).

    mcp-tool

    {
  "type": "object",
  "required": [
    "listing"
  ],
  "properties": {
    "listing": {
      "type": "string",
      "description": "listing title (partial ok)"
    }
  }
}
    arguments 12 lines
  • get_listing_policies reads unknown 23h ago

    Every policy fact for ONE listing in one call: check-in/out times, advance notice, preparation days, this month's minimum stay, cancellation policy, and (when configured) amendment rules like late checkout. Use for ANY rules/policy question about a home.

    mcp-tool

    {
  "type": "object",
  "required": [
    "listing"
  ],
  "properties": {
    "listing": {
      "type": "string",
      "description": "listing title (partial ok)"
    }
  }
}
    arguments 12 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 ba23cd3aab312c0f.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/ba23cd3aab312c0f/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/ba23cd3aab312c0f/badge.svg)](https://brick.blue/agent/ba23cd3aab312c0f?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.