Interact with Microsoft 365 and Office services through the Microsoft Graph API.
Appointo MCP by usefulapi is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Read Appointo bookings, availability and subscriptions; create, reschedule and cancel bookings.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http appointo-mcp-by-usefulapi https://appointo.usefulapi.io/mcp
# 2 — ask your agent for something these tools do
# appointo_list_products, appointo_list_appointments, appointo_get_availability and 7 more
Appointo MCP by usefulapi costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http appointo-mcp-by-usefulapi https://appointo.usefulapi.io/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
10 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
List the Shopify products that are set up as bookable in Appointo: name, appointment type, whether the widget is shown, and each product's appointments (the bookable variants/services with price, currency and id). Use an appointment id for availability and bookings. GET /products.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| search_term | string | no | Filter by product name. |
| limit | integer | no | Results per page, 1-100 (default 25). |
| offset | integer | no | Number of results to skip (default 0). Pass the previous reply's next_offset. |
List appointments, i.e. the bookable services/variants, with name, price, currency and configuration. Filter by product or fetch one by id. These are the services customers book, not the bookings themselves (use appointo_list_bookings for those). GET /appointments.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| appointment_id | integer | no | Fetch a single appointment by id. |
| product_id | integer | no | Only appointments of this Appointo product id (the id from appointo_list_products). |
| search_term | string | no | — |
| limit | integer | no | Results per page, 1-100 (default 25). |
| offset | integer | no | Number of results to skip (default 0). Pass the previous reply's next_offset. |
The free time slots of one appointment (bookable service) from start_date, optionally to end_date. Use it before creating or rescheduling a booking. GET /appointments/{appointment_id}/calendar_availability.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| appointment_id | integer | yes | Appointo appointment id (from appointo_list_appointments). |
| start_date | string | yes | First day, yyyy-mm-dd. |
| end_date | string | no | Last day, yyyy-mm-dd. |
List bookings with time, product, duration, quantity, price and the customers (name, email, phone, address). Filter upcoming/past or search; pass booking_id for one booking. The customers' cancel/reschedule link ids are never returned. GET /bookings.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| booking_id | integer | no | Fetch a single booking by id. |
| status | string | no | Only upcoming or only past bookings. |
| search_term | string | no | Searches product name, customer name, email, phone and order name. |
| limit | integer | no | Results per page, 1-100 (default 25). |
| offset | integer | no | Number of results to skip (default 0). Pass the previous reply's next_offset. |
List cancelled bookings, same shape as appointo_list_bookings. GET /bookings/cancelled_bookings.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| status | string | no | Only upcoming or only past bookings. |
| search_term | string | no | Searches product name, customer name, email, phone and order name. |
| limit | integer | no | Results per page, 1-100 (default 25). |
| offset | integer | no | Number of results to skip (default 0). Pass the previous reply's next_offset. |
List the recurring booking subscription contracts (customers who subscribed to repeat appointments). Search by product, variant, order number or customer name. The API documents no paging for this list. GET /appointment_subscriptions.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| search_term | string | no | Product name, variant name, order number or customer name. |
WRITE: create a booking for a customer on an appointment (bookable service) at a time slot. This is a real booking: Appointo may email the customer a confirmation and reserve the slot; the booking can later be cancelled with appointo_cancel_booking. Check appointo_get_availability first. Not idempotent: calling twice creates two bookings. The docs cap this at 100 requests per day. POST /bookings.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| appointment_id | integer | yes | Appointo appointment id (from appointo_list_appointments). |
| timestring | string | yes | Start of the time slot, ISO 8601, e.g. 2026-11-03T14:00:00-05:00 (use a date only, 2026-11-03, for a day booking). Check appointo_get_availability for real slots. |
| name | string | yes | Customer name. |
| string | yes | Customer email. | |
| phone | string | no | Customer phone number. |
| quantity | integer | no | Number of spots (default 1). |
WRITE: move a booking (or only some of its customers) to a new time slot. Appointo may notify the customers of the change. override=true forces the booking into the slot even if it is unavailable or full, so leave it off unless the user explicitly asked for it. The docs cap this at 100 requests per day. PUT /bookings/reschedule.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| booking_id | integer | yes | Booking id (from appointo_list_bookings). |
| timestring | string | yes | Start of the time slot, ISO 8601, e.g. 2026-11-03T14:00:00-05:00 (use a date only, 2026-11-03, for a day booking). Check appointo_get_availability for real slots. |
| customer_ids | array | no | Only move these customer ids of the booking; omit to move the whole booking. |
| override | boolean | no | Force the slot even if unavailable (default false). |
WRITE: cancel a booking, or only some of its customers. The slot is freed and Appointo may notify the customers; whether a Shopify order is refunded is not controlled by this call. Cannot be undone through this server (create a new booking instead). The docs cap this at 100 requests per day. PUT /bookings/cancel.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| booking_id | integer | yes | Booking id (from appointo_list_bookings). |
| customer_ids | array | no | Only cancel these customer ids of the booking; omit to cancel the whole booking. |
WRITE: set the start and/or end buffer time (minutes blocked before/after) of one booking. At least one value is required. The docs cap this at 100 requests per day. PUT /bookings/{booking_id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| booking_id | integer | yes | Booking id (from appointo_list_bookings). |
| start_buffer_time | integer | no | Buffer before the booking, minutes (> 0). |
| end_buffer_time | integer | no | Buffer after the booking, minutes (> 0). |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Appointo MCP by usefulapi or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| appointo_list_products | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| appointo_list_appointments | untrusted-input | untrusted-input: keyword "fetch", declares openWorldHint: true (interacts with entities outside the server) |
| appointo_get_availability | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| appointo_list_bookings | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| appointo_list_cancelled_bookings | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| appointo_list_subscription_contracts | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| appointo_create_booking | external-sink | external-sink: declares readOnlyHint: false, destructiveHint: true, openWorldHint: true |
| appointo_reschedule_booking | external-sink | external-sink: declares readOnlyHint: false, destructiveHint: true, openWorldHint: true |
| appointo_cancel_booking | external-sink | external-sink: declares readOnlyHint: false, destructiveHint: true, openWorldHint: true |
| appointo_update_booking_buffers | external-sink | external-sink: declares readOnlyHint: false, destructiveHint: true, openWorldHint: true |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
Supply chain and provenance
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.19.0.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Appointo MCP by usefulapi can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.