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

Booking Server

https://ai.upsalt.io

Registry code: d0327b793a3f2317

api record

This server lets you book at businesses (restaurants and other venues) on behalf of a guest. Typical flow: 1) find-company with the company slug to get its profile and company_id; 2) list-available-slots with the company_id and a YYYY-MM-DD date to get shifts and hours; 3) create-booking with the chosen slot (note: booking date uses YYYY/MM/DD with slashes) and the guest contact details — it returns a management token; 4) get-booking-info or cancel-booking with that token to manage the reservation. Always confirm guest details and the chosen slot with the user before creating or cancelling a…

endpoint
https://ai.upsalt.io/mcp/booking
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 Booking Server live?
Yes — it answered the hub's last check (checked 8h ago). It answered 100% of checks over the last 30 days.
Is Booking Server free to use?
Yes — the hub reached it with no key and no payment.
What tools does Booking Server have?
5 tools: get-booking-info, create-booking, cancel-booking, list-available-slots, find-company.
Is Booking Server 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.5%

90 days 99.4%· all time 99.4%

latency
494ms

last good check

priced tools
0

of 5 tools

_ answered our checks, 90 days 317 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
  • find a restaurant booking profile
  • list available booking slots
  • book a table for a guest
  • cancel a booking
takes → gives
text, 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

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 5 tools
5 never probed 0 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.

  • get-booking-info reads unknown never probed

    Retrieve the details of an existing booking using the management token returned by create-booking.

    mcp-tool

    {
      "type": "object",
      "required": [
        "company_id",
        "token"
      ],
      "properties": {
        "token": {
          "type": "string",
          "description": "The booking management token returned by create-booking."
        },
        "company_id": {
          "type": "integer",
          "description": "The company id the booking belongs to."
        }
      }
    }
    arguments 17 lines
  • create-booking changes data unknown never probed

    Create a booking for a company as a guest. Requires a date (YYYY/MM/DD), an hour and shift_id obtained from list-available-slots, and the guest contact details. On success, returns the reservation details including a token that can be used with get-booking-info and cancel-booking.

    mcp-tool

    {
      "type": "object",
      "required": [
        "company_id",
        "date",
        "hour",
        "shift_id",
        "adults",
        "name",
        "surname",
        "email",
        "phone"
      ],
      "properties": {
        "city": {
          "type": "string",
          "description": "Guest city."
        },
        "date": {
          "type": "string",
          "description": "Booking date in YYYY/MM/DD format (e.g. 2026/07/20). Note the slashes."
        },
        "hour": {
          "type": "string",
          "description": "Booking hour in HH:MM format, taken from list-available-slots."
        },
        "name": {
          "type": "string",
          "description": "Guest first name."
        },
        "pets": {
          "type": "integer",
          "description": "Number of pets."
        },
        "email": {
          "type": "string",
          "description": "Guest email address. The booking confirmation and management token are sent here."
        },
        "optin": {
          "type": "integer",
          "description": "Marketing opt-in flag (1 or 0)."
        },
        "phone": {
          "type": "string",
          "description": "Guest phone number."
        },
        "vegan": {
          "type": "boolean",
          "description": "Whether the party includes vegan guests."
        },
        "adults": {
          "type": "integer",
          "description": "Number of adults."
        },
        "babies": {
          "type": "integer",
          "description": "Number of babies."
        },
        "country": {
          "type": "string",
          "description": "Guest country."
        },
        "message": {
          "type": "string",
          "description": "Optional message for the business."
        },
        "surname": {
          "type": "string",
          "description": "Guest last name."
        },
        "children": {
          "type": "integer",
          "description": "Number of children."
        },
        "latitude": {
          "type": "number",
          "description": "Guest latitude, if known."
        },
        "shift_id": {
          "type": "integer",
          "description": "The shift id, taken from list-available-slots."
        },
        "highchair": {
          "type": "integer",
          "description": "Number of highchairs."
        },
        "longitude": {
          "type": "number",
          "description": "Guest longitude, if known."
        },
        "pushchair": {
          "type": "integer",
          "description": "Number of pushchairs."
        },
        "company_id": {
          "type": "integer",
          "description": "The company id, as returned by the find-company tool."
        },
        "vegetarian": {
          "type": "boolean",
          "description": "Whether the party includes vegetarian guests."
        },
        "wheelchair": {
          "type": "integer",
          "description": "Number of wheelchairs."
        },
        "gluten_free": {
          "type": "boolean",
          "description": "Whether the party needs gluten-free options."
        },
        "guest_token": {
          "type": "string",
          "description": "Existing guest token, if the guest has booked before."
        },
        "nuts_allergy": {
          "type": "boolean",
          "description": "Whether the party has a nut allergy."
        }
      }
    }
    arguments 120 lines
  • cancel-booking changes data unknown never probed

    Cancel an existing booking using the management token returned by create-booking. This action is irreversible; confirm with the guest before calling it.

    mcp-tool

    {
      "type": "object",
      "required": [
        "token"
      ],
      "properties": {
        "token": {
          "type": "string",
          "description": "The booking management token returned by create-booking."
        }
      }
    }
    arguments 12 lines
  • list-available-slots reads unknown 28h ago

    List the available booking slots for a company on a given date. Returns shifts and bookable hours; use the shift_id and hour when creating a booking.

    mcp-tool

    {
      "type": "object",
      "required": [
        "company_id",
        "date"
      ],
      "properties": {
        "date": {
          "type": "string",
          "description": "The date to check, in YYYY-MM-DD format (e.g. 2026-07-20)."
        },
        "company_id": {
          "type": "integer",
          "description": "The company id, as returned by the find-company tool."
        }
      }
    }
    arguments 17 lines
  • find-company reads unknown 28h ago

    Find a company by its slug and return its public profile: services, opening hours, and booking configuration. Use this first to obtain the company_id needed by the other tools.

    mcp-tool

    {
      "type": "object",
      "required": [
        "slug"
      ],
      "properties": {
        "slug": {
          "type": "string",
          "description": "The company slug, as found in its booking page URL."
        },
        "business_type": {
          "type": "string",
          "description": "Optional business type filter."
        }
      }
    }
    arguments 16 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 d0327b793a3f2317.

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