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

fostay

https://fostay.com

Registry code: e9baa2c063823495

api record

Fostay is an agent-bookable hotel store for Dubai and Abu Dhabi: live all-in prices (AED, taxes included — what you see is what the card is charged) and a demand calendar of dates when UAE hotels sell out. Booking flow: search_stays → get_live_rates (pick an offer_id) → confirm guest name + email with your user → prepare_booking (holds the rate, returns a payment_url) → the human pays in one tap on fostay.com → booking_status to verify. Never guess guest details; always confirm the final price from prepare_booking before sending the human to pay. Check demand_calendar before recommending…

endpoint
https://fostay.com/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 fostay live?
Yes — it answered the hub's last check (checked 6h ago). It answered 100% of checks over the last 30 days.
Is fostay free to use?
Yes — the hub reached it with no key and no payment.
What tools does fostay have?
6 tools: search_stays, prepare_booking, booking_status, get_live_rates, demand_calendar, when_to_go.
Is fostay 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 100%· all time 100%

latency
310ms

last good check

priced tools
0

of 6 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 6 tools
2 open 4 never probed 2 of 6 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.

  • demand_calendar open 6h ago

    Fostay's editorial demand calendar: the upcoming date windows where Dubai and Abu Dhabi hotels predictably spike or sell out (GITEX, F1, NYE, Eid, school breaks...), each with a suggested book-by deadline. Use it to warn users about expensive dates or find event stays.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "properties": {
        "city": {
          "enum": [
            "Dubai",
            "Abu Dhabi"
          ],
          "type": "string",
          "description": "Filter by city (default: both)"
        }
      }
    }
    arguments 14 lines
  • when_to_go open 6h ago

    Prices upcoming weekends (Fri–Sun, 2 nights) to find the cheapest times to stay. Pass hotel_id for one hotel across ~8 weekends, or just a city to compare Fostay's curated stays across the next ~6 weekends. Cheapest options first.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "properties": {
        "city": {
          "enum": [
            "Dubai",
            "Abu Dhabi"
          ],
          "type": "string",
          "description": "Used when hotel_id is omitted"
        },
        "hotel_id": {
          "type": "string",
          "maxLength": 40,
          "minLength": 3,
          "description": "Optional hotel id from search_stays"
        }
      }
    }
    arguments 20 lines
  • search_stays unknown never probed

    Search hotels in Dubai or Abu Dhabi. Returns Fostay's hand-curated edit first (8 flagship stays with editorial verdicts), then catalog matches (~2,000 bookable hotels). Use get_live_rates for prices. Results include a fostay_url where a human can view photos, live rates and book.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "city"
      ],
      "properties": {
        "city": {
          "enum": [
            "Dubai",
            "Abu Dhabi"
          ],
          "type": "string",
          "description": "City to search"
        },
        "limit": {
          "type": "integer",
          "maximum": 25,
          "minimum": 1,
          "description": "Max catalog results (default 10)"
        },
        "query": {
          "type": "string",
          "maxLength": 80,
          "description": "Optional hotel-name filter, e.g. 'Atlantis' or 'Rove'"
        },
        "min_rating": {
          "type": "number",
          "maximum": 10,
          "minimum": 0,
          "description": "Minimum guest rating on a 10 scale, e.g. 8"
        }
      }
    }
    arguments 34 lines
  • prepare_booking unknown never probed

    Books everything except the payment: holds the chosen offer (real prebook — the price is locked while the hold lasts), registers the guest details, and returns a payment_url. The human opens that link, sees the exact stay summary, and pays in one step — the agent never handles card details. Confirm the guest's name and email with the user before calling. If the held price differs from what you quoted, this returns the final price and any change warnings — tell the user before sending them to pay.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "offer_id",
        "guest_first_name",
        "guest_last_name",
        "guest_email"
      ],
      "properties": {
        "offer_id": {
          "type": "string",
          "maxLength": 4000,
          "minLength": 10,
          "description": "offer_id from get_live_rates"
        },
        "agent_name": {
          "type": "string",
          "maxLength": 40,
          "description": "Your client name for attribution, e.g. 'claude' or 'chatgpt'"
        },
        "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": 254,
          "description": "Guest's email — booking confirmation goes here"
        },
        "guest_phone": {
          "type": "string",
          "maxLength": 32
        },
        "guest_last_name": {
          "type": "string",
          "maxLength": 80,
          "minLength": 1
        },
        "guest_first_name": {
          "type": "string",
          "maxLength": 80,
          "minLength": 1
        }
      }
    }
    arguments 44 lines
  • booking_status unknown never probed

    Verify a completed booking: confirmation status, hotel confirmation code, stay and price. Requires the Fostay booking id AND the guest email it was booked under (both are in the guest's confirmation). Use after the human pays via a prepare_booking link.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "booking_id",
        "guest_email"
      ],
      "properties": {
        "booking_id": {
          "type": "string",
          "maxLength": 40,
          "minLength": 4,
          "description": "Fostay booking id, e.g. uzYG5ZTt9"
        },
        "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": 254,
          "description": "Guest email on the booking"
        }
      }
    }
    arguments 23 lines
  • get_live_rates unknown 6h ago

    Live bookable room offers for one hotel and stay dates: total all-in price (AED), board (breakfast etc.), refundability and exact free-cancellation deadlines. The booking_url takes a human straight to this hotel on fostay.com to complete the booking.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "hotel_id",
        "checkin",
        "checkout"
      ],
      "properties": {
        "adults": {
          "type": "integer",
          "maximum": 8,
          "minimum": 1,
          "description": "Adult guests (default 2)"
        },
        "checkin": {
          "type": "string",
          "description": "Check-in date, YYYY-MM-DD"
        },
        "checkout": {
          "type": "string",
          "description": "Check-out date, YYYY-MM-DD"
        },
        "children": {
          "type": "array",
          "items": {
            "type": "integer",
            "maximum": 17,
            "minimum": 0
          },
          "maxItems": 4,
          "description": "Children's ages at check-in, e.g. [7, 9]. IMPORTANT for families: child-inclusive rates price kids' breakfast and extras upfront — always pass ages when children travel."
        },
        "hotel_id": {
          "type": "string",
          "maxLength": 40,
          "minLength": 3,
          "description": "Hotel id from search_stays (e.g. lp6556acf7)"
        }
      }
    }
    arguments 41 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 e9baa2c063823495.

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

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.