Appointo MCP by usefulapi
REMOTE · APPOINTO.USEFULAPI.IO
Read Appointo bookings, availability and subscriptions; create, reschedule and cancel bookings.
Available components
Last scanned (48 minutes ago)
Scores higher than 46% of remote servers
Reachable. Last reached 25 Oct 2026.
Category Productivity and Notes
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security78
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability80
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1652 tokens (~165/item across 10 items; 10 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management3
- Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage99
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 97% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 25 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- Server version: 1.2.0 → 1.2.3 functional
- 24 Oct 26 62
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 25 Oct 2026 · Probed https://appointo.usefulapi.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=usefulapi.io | CN=WE1,O=Google Trust Services,C=US | 13 Sept 2026 | 12 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | d9be3287b0fde9630e825ba1f79bff3f |
| SANs: usefulapi.io, *.usefulapi.io | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of appointo.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 38690, 57355 | 8, 8 | Verified |
| usefulapi.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 302 |
WWW-Authenticate challenge Bearer realm="OAuth", resource_metadata="https://appointo.usefulapi.io/.well-known/oauth-protected-resource/mcp"
Bearer realm="OAuth", resource_metadata="https://appointo.usefulapi.io/.well-known/oauth-protected-resource/mcp"Protected resource metadata
| Document | https://appointo.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://appointo.usefulapi.io/mcp |
| Authorisation server | https://appointo.usefulapi.io |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://appointo.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/appointo/ |
| http (plaintext) | http://appointo.usefulapi.io/mcp | Inconclusive | 302 | http://appointo.usefulapi.io/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
appointo_cancel_booking Cancel booking ~120
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.
| Name | Type | Req | Description |
|---|---|---|---|
| booking_id | integer | yes | Booking id (from appointo_list_bookings). |
| customer_ids | array | – | Only cancel these customer ids of the booking; omit to cancel the whole booking. |
No output schema declared.
No examples provided.
appointo_create_booking Create booking ~227
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.
| Name | Type | Req | Description |
|---|---|---|---|
| appointment_id | integer | yes | Appointo appointment id (from appointo_list_appointments). |
| string | yes | Customer email. | |
| name | string | yes | Customer name. |
| phone | string | – | Customer phone number. |
| quantity | integer | – | Number of spots (default 1). |
| 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. |
No output schema declared.
No examples provided.
appointo_get_availability Get appointment availability ~101
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.
| Name | Type | Req | Description |
|---|---|---|---|
| appointment_id | integer | yes | Appointo appointment id (from appointo_list_appointments). |
| end_date | string | – | Last day, yyyy-mm-dd. |
| start_date | string | yes | First day, yyyy-mm-dd. |
No output schema declared.
No examples provided.
appointo_list_appointments List appointments (bookable services) ~159
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.
| Name | Type | Req | Description |
|---|---|---|---|
| appointment_id | integer | – | Fetch a single appointment by id. |
| limit | integer | – | Results per page, 1-100 (default 25). |
| offset | integer | – | Number of results to skip (default 0). Pass the previous reply's next_offset. |
| product_id | integer | – | Only appointments of this Appointo product id (the `id` from appointo_list_products). |
| search_term | string | – | – |
No output schema declared.
No examples provided.
appointo_list_bookings List bookings ~157
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.
| Name | Type | Req | Description |
|---|---|---|---|
| booking_id | integer | – | Fetch a single booking by id. |
| limit | integer | – | Results per page, 1-100 (default 25). |
| offset | integer | – | Number of results to skip (default 0). Pass the previous reply's next_offset. |
| search_term | string | – | Searches product name, customer name, email, phone and order name. |
| status | string | – | Only upcoming or only past bookings. |
No output schema declared.
No examples provided.
appointo_list_cancelled_bookings List cancelled bookings ~113
List cancelled bookings, same shape as appointo_list_bookings. GET /bookings/cancelled_bookings.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Results per page, 1-100 (default 25). |
| offset | integer | – | Number of results to skip (default 0). Pass the previous reply's next_offset. |
| search_term | string | – | Searches product name, customer name, email, phone and order name. |
| status | string | – | Only upcoming or only past bookings. |
No output schema declared.
No examples provided.
appointo_list_products List bookable products ~123
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Results per page, 1-100 (default 25). |
| offset | integer | – | Number of results to skip (default 0). Pass the previous reply's next_offset. |
| search_term | string | – | Filter by product name. |
No output schema declared.
No examples provided.
appointo_list_subscription_contracts List subscription contracts ~72
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.
| Name | Type | Req | Description |
|---|---|---|---|
| search_term | string | – | Product name, variant name, order number or customer name. |
No output schema declared.
No examples provided.
appointo_reschedule_booking Reschedule booking ~210
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.
| Name | Type | Req | Description |
|---|---|---|---|
| booking_id | integer | yes | Booking id (from appointo_list_bookings). |
| customer_ids | array | – | Only move these customer ids of the booking; omit to move the whole booking. |
| override | boolean | – | Force the slot even if unavailable (default false). |
| 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. |
No output schema declared.
No examples provided.
appointo_update_booking_buffers Update booking buffer times ~111
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}.
| Name | Type | Req | Description |
|---|---|---|---|
| booking_id | integer | yes | Booking id (from appointo_list_bookings). |
| end_buffer_time | integer | – | Buffer after the booking, minutes (> 0). |
| start_buffer_time | integer | – | Buffer before the booking, minutes (> 0). |
No output schema declared.
No examples provided.
How do I install the Appointo MCP by usefulapi server?
Appointo MCP by usefulapi is a hosted endpoint at https://appointo.usefulapi.io/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · appointo.usefulapi.io
claude mcp add --transport http io-usefulapi-appointo 'https://appointo.usefulapi.io/mcp'
What is the Appointo MCP by usefulapi server?
Appointo MCP by usefulapi is listed in the public MCP registry as io.usefulapi/appointo. Read Appointo bookings, availability and subscriptions; create, reschedule and cancel bookings. This page covers its hosted endpoint (https://appointo.usefulapi.io/mcp).
Is the Appointo MCP by usefulapi server safe to use?
Appointo MCP by usefulapi scores 62 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Appointo MCP by usefulapi server expose?
Appointo MCP by usefulapi exposes 10 tools: appointo_list_products, appointo_list_appointments, appointo_get_availability, appointo_list_bookings, appointo_list_cancelled_bookings, and 5 more. Their descriptions and schemas cost roughly 1,393 tokens of context every time the server is loaded.
Does the Appointo MCP by usefulapi server require authentication?
Yes. Appointo MCP by usefulapi asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the Appointo MCP by usefulapi server still maintained?
Appointo MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 25 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.