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

meetbot-mcp

https://mcp.meet.bot

Registry code: 64dadb734c64d79f

api record

AI-native scheduling and booking: check availability, book meetings, share links.

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

endpoint
https://mcp.meet.bot
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 meetbot-mcp live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is meetbot-mcp free to use?
Not anonymously — it asks for a key or a login before it will serve. Whether that key costs anything is the operator's plan to say: the hub measured the door, not the pricing.
What tools does meetbot-mcp have?
8 tools: book_meeting, set_webhook, delete_webhook, list_webhooks, get_page_info, get_scheduling_pages, health_check, get_available_slots.
Is meetbot-mcp 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
63ms

last good check

priced tools
0

of 8 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ 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
8 auth-required 8 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.

  • book_meeting auth-required never probed

    Book a new meeting slot

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "page",
    "guest_email",
    "guest_name",
    "start"
  ],
  "properties": {
    "page": {
      "type": "string",
      "description": "The URL of the scheduling page (e.g. https://meet.bot/your-page)"
    },
    "notes": {
      "type": "string",
      "description": "Optional notes to include with the meeting (e.g. agenda, call details)"
    },
    "start": {
      "type": "string",
      "description": "Start time in ISO 8601 format (e.g. 2025-03-10T14:00:00Z); must be an available slot"
    },
    "guest_name": {
      "type": "string",
      "description": "Full name of the guest"
    },
    "guest_email": {
      "type": "string",
      "description": "Email address of the guest (used for calendar invite and confirmation)"
    }
  },
  "additionalProperties": false
}
    arguments 33 lines
  • set_webhook auth-required never probed

    Create or update an outbound booking webhook. Omit id to create (webhook_url required); pass id to update. Meet.bot POSTs a JWT-signed (HS256) JSON payload to the URL on each booking event.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "id": {
      "type": "number",
      "description": "Webhook id to update; omit to create a new one"
    },
    "pages": {
      "type": "array",
      "items": {
        "type": "number"
      },
      "description": "Page ids to cover when coverage='selected'"
    },
    "scope": {
      "enum": [
        "self",
        "team"
      ],
      "type": "string",
      "description": "'self' (default) your own pages; 'team' (team admins only) also fires for teammates' bookings"
    },
    "coverage": {
      "enum": [
        "all",
        "selected"
      ],
      "type": "string",
      "description": "'all' (default) fires for every page including ones created later; 'selected' only for the pages in `pages`"
    },
    "is_active": {
      "type": "boolean",
      "description": "Whether the webhook is active (default true)"
    },
    "description": {
      "type": "string",
      "description": "Optional label for the webhook"
    },
    "webhook_url": {
      "type": "string",
      "description": "HTTPS URL we POST booking events to (required when creating)"
    }
  },
  "additionalProperties": false
}
    arguments 46 lines
  • delete_webhook auth-required never probed

    Delete one of the authenticated user's webhooks by id

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "id"
  ],
  "properties": {
    "id": {
      "type": "number",
      "description": "The webhook id to delete"
    }
  },
  "additionalProperties": false
}
    arguments 14 lines
  • list_webhooks auth-required 1h ago

    List the authenticated user's outbound booking webhooks (fired on booking_received, booking_rescheduled and booking_cancelled)

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {},
  "additionalProperties": false
}
    arguments 6 lines
  • get_page_info auth-required never probed

    Get information about a specific scheduling page

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "page"
  ],
  "properties": {
    "page": {
      "type": "string",
      "description": "The URL of the scheduling page (e.g. https://meet.bot/your-page)"
    }
  },
  "additionalProperties": false
}
    arguments 14 lines
  • get_scheduling_pages auth-required 1h ago

    Get all scheduling pages for the authenticated user

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {},
  "additionalProperties": false
}
    arguments 6 lines
  • health_check auth-required 1h ago

    Check if the Meet.bot API client is healthy and the Bearer token is valid

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {},
  "additionalProperties": false
}
    arguments 6 lines
  • get_available_slots auth-required never probed

    Get available booking slots for a scheduling page

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "page"
  ],
  "properties": {
    "end": {
      "type": "string",
      "description": "End date for the range in YYYY-MM-DD format"
    },
    "page": {
      "type": "string",
      "description": "The URL of the scheduling page (e.g. https://meet.bot/your-page)"
    },
    "count": {
      "type": "number",
      "description": "Maximum number of slots to return (defaults to server limit)"
    },
    "start": {
      "type": "string",
      "description": "Start date for the range in YYYY-MM-DD format"
    },
    "timezone": {
      "type": "string",
      "description": "IANA timezone for slot times (e.g. America/New_York, Europe/London)"
    },
    "booking_link": {
      "type": "boolean",
      "description": "If true, include shareable booking links in the response"
    }
  },
  "additionalProperties": false
}
    arguments 34 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 64dadb734c64d79f.

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