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

TehProf Booking

https://booking.tehprof.kz

Registry code: 91123387150ae07e

api record

Remote MCP for TehProf Booking: browse resources & availability, create & cancel reservations.

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

endpoint
https://booking.tehprof.kz/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 TehProf Booking live?
Yes — it answered the hub's last check (checked 2h ago). It answered 99% of checks over the last 30 days.
Is TehProf Booking free to use?
Partly — some of its tools are open, others need a key or payment.
What tools does TehProf Booking have?
8 tools: create_reservation, cancel_reservation, list_groups, check_availability, get_branding, list_resources, get_reservation, list_reservations.
Is TehProf Booking 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.2%

90 days 98.4%· all time 98.4%

latency
629ms

last good check

priced tools
0

of 8 tools

_ answered our checks, 90 days 385 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
used for
  • check free time slots for a resource
  • book a room or service
  • cancel a reservation
  • list bookable resources
takes → gives
text → data
tools
6 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 8 tools
4 open2 auth-required 2 never probed 6 of 8 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.

  • list_groups reads open 11h ago

    List resource groups (categories) of a tenant by public slug — only groups with at least one publicly visible resource. No API key required.

    mcp-tool

    {
      "type": "object",
      "required": [
        "slug"
      ],
      "properties": {
        "slug": {
          "type": "string",
          "description": "Tenant public slug."
        }
      }
    }
    arguments 12 lines
  • check_availability reads open 4h ago

    Get free time slots for a resource on a given date. Returns bookable slots considering existing reservations. No API key required.

    mcp-tool

    {
      "type": "object",
      "required": [
        "resource_id",
        "date"
      ],
      "properties": {
        "date": {
          "type": "string",
          "description": "Date in YYYY-MM-DD."
        },
        "resource_id": {
          "type": "string",
          "description": "Resource UUID (from list_resources)."
        },
        "duration_minutes": {
          "type": "integer",
          "description": "Slot duration in minutes (5-1440, default 60)."
        }
      }
    }
    arguments 21 lines
  • get_branding reads open 4h ago

    Get public tenant profile and branding (name, logo, colors, tagline) by the tenant public slug. No API key required.

    mcp-tool

    {
      "type": "object",
      "required": [
        "slug"
      ],
      "properties": {
        "slug": {
          "type": "string",
          "description": "Tenant public slug, e.g. \"baiterekresort-bitrix24-kz\"."
        }
      }
    }
    arguments 12 lines
  • list_resources reads open 4h ago

    List bookable resources of a tenant (rooms, halls, services) by public slug. Optional filters: group_id, search, bed_type, resource_class, min_capacity, amenities (comma-separated). No API key required.

    mcp-tool

    {
      "type": "object",
      "required": [
        "slug"
      ],
      "properties": {
        "slug": {
          "type": "string",
          "description": "Tenant public slug."
        },
        "search": {
          "type": "string",
          "description": "Free-text name filter (1-100 chars)."
        },
        "bed_type": {
          "type": "string"
        },
        "group_id": {
          "type": "string",
          "description": "Resource group UUID, or \"none\" for ungrouped."
        },
        "amenities": {
          "type": "string",
          "description": "Comma-separated amenity keys."
        },
        "min_capacity": {
          "type": "integer",
          "description": "Minimum capacity."
        },
        "resource_class": {
          "type": "string"
        }
      }
    }
    arguments 34 lines
  • get_reservation reads auth-required 11h ago

    [Requires API key with the matching scope] Get a single reservation by its UUID. With the reservations:read scope and matching tenant, returns guest details; otherwise only public status fields.

    mcp-tool

    {
      "type": "object",
      "required": [
        "reservation_id"
      ],
      "properties": {
        "reservation_id": {
          "type": "string",
          "description": "Reservation UUID."
        }
      }
    }
    arguments 12 lines
  • list_reservations reads auth-required 11h ago

    [Requires API key with the matching scope] List reservations of the API key tenant. Requires the reservations:read scope. Optional filters: resource_id, from/to (YYYY-MM-DD), status, limit (1-200, default 50).

    mcp-tool

    {
      "type": "object",
      "properties": {
        "to": {
          "type": "string",
          "description": "End date filter YYYY-MM-DD."
        },
        "from": {
          "type": "string",
          "description": "Start date filter YYYY-MM-DD."
        },
        "limit": {
          "type": "integer",
          "description": "1-200, default 50."
        },
        "status": {
          "type": "string",
          "description": "Filter by status (e.g. confirmed, pending, cancelled)."
        },
        "resource_id": {
          "type": "string",
          "description": "Filter by resource UUID."
        }
      }
    }
    arguments 25 lines
  • create_reservation changes data unknown never probed

    [Requires API key with the matching scope] Create a reservation. Requires an API key with the reservations:write scope; the booking is bound to the key tenant and the resource must belong to it. Provide either check_in_date+check_out_date (overnight/rental) OR start_at+end_at ISO datetimes (time-slot).

    mcp-tool

    {
      "type": "object",
      "required": [
        "resource_id",
        "guest_name",
        "guest_phone"
      ],
      "properties": {
        "notes": {
          "type": "string",
          "description": "Free-text notes (max 1000 chars, optional)."
        },
        "end_at": {
          "type": "string",
          "description": "Slot end ISO datetime."
        },
        "locale": {
          "type": "string",
          "description": "Locale ru/en/kk (optional, default ru)."
        },
        "start_at": {
          "type": "string",
          "description": "Slot start ISO datetime (alternative to check_in_date)."
        },
        "guest_name": {
          "type": "string",
          "description": "Guest full name (2-200 chars)."
        },
        "guest_email": {
          "type": "string",
          "description": "Guest email (optional)."
        },
        "guest_phone": {
          "type": "string",
          "description": "Guest phone, 6-15 digits with optional +."
        },
        "resource_id": {
          "type": "string",
          "description": "Resource UUID to book."
        },
        "check_in_date": {
          "type": "string",
          "description": "Rental check-in date YYYY-MM-DD."
        },
        "check_out_date": {
          "type": "string",
          "description": "Rental check-out date YYYY-MM-DD."
        },
        "idempotency_key": {
          "type": "string",
          "description": "Optional client-generated key (e.g. a UUID) to make retries safe. Repeating the call with the same key returns the original reservation instead of creating a duplicate (24h window)."
        }
      }
    }
    arguments 54 lines
  • cancel_reservation changes data unknown never probed

    [Requires API key with the matching scope] Cancel a reservation by UUID. Requires the reservations:write scope and the reservation must belong to the key tenant (idempotent — cancelling an already-cancelled booking succeeds).

    mcp-tool

    {
      "type": "object",
      "required": [
        "reservation_id"
      ],
      "properties": {
        "reservation_id": {
          "type": "string",
          "description": "Reservation UUID to cancel."
        }
      }
    }
    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 91123387150ae07e.

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

_ also on tehprof.kz 2 entries

Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.