Easy!Appointments
REMOTE · EA-MCP-DEMO.QIYUANLABS.AI
Find open slots, book, move and cancel Easy!Appointments bookings, with OAuth and a call log.
Available components
Last scanned (8 hours ago)
Scores higher than 69% of remote servers
Reachable. Last reached 5 Nov 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 Security89
- 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 is enforced; there's no plaintext access path. View diagnostics → Pass
- 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 & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability69
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1399 tokens (~199/item across 7 items; 7 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 Management10
- Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 5 Nov 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 4 Nov 26 +1
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 3 Nov 26 0
- Stability: unverified → 0.03 ▲ functional
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 2 Nov 26 +40
- Transport: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- Authorization: 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. security
- MCP protocol: unverified → pass ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- First check of Schema quality: fail functional
- First check of Schema quality: excellent functional
- First check of Destructive annotations: pass functional
- First check of Schema quality: fail functional
- First check of Tool coverage: 100 functional
- 1 Nov 26 36
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 5 Nov 2026 · Probed https://ea-mcp-demo.qiyuanlabs.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=ea-mcp-demo.qiyuanlabs.ai | CN=YE2,O=Let's Encrypt,C=US | 1 Nov 2026 | 30 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 549e9ef7154d5a3a281b64dde2f8e648caf |
| SANs: ea-mcp-demo.qiyuanlabs.ai | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of ea-mcp-demo.qiyuanlabs.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 1814, 3799 | 8, 8 | Verified |
| qiyuanlabs.ai. | 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 | 200 |
WWW-Authenticate challenge Bearer realm="mcp", resource_metadata="https://ea-mcp-demo.qiyuanlabs.ai/.well-known/oauth-protected-resource/mcp"
Bearer realm="mcp", resource_metadata="https://ea-mcp-demo.qiyuanlabs.ai/.well-known/oauth-protected-resource/mcp"| Header | Value |
|---|---|
| x-content-type-options | nosniff |
| referrer-policy | strict-origin-when-cross-origin |
Protected resource metadata
| Document | https://ea-mcp-demo.qiyuanlabs.ai/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://ea-mcp-demo.qiyuanlabs.ai/mcp |
| Authorisation server | https://ea-mcp-demo.qiyuanlabs.ai |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://ea-mcp-demo.qiyuanlabs.ai/mcp | Verified | 200 | |
| http (plaintext) | http://ea-mcp-demo.qiyuanlabs.ai/mcp | HTTPS enforced | 308 | https://ea-mcp-demo.qiyuanlabs.ai/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 →
book_appointment Book an appointment ~338
Books an appointment for an existing customer (customer_id) or a new one (new_customer). Two steps: first call without confirm to get a preview and show it to the person; only after they agree, call again with the same arguments, confirm: true, the confirmation_token from the preview and an idempotency_key. Easy!Appointments then sends its usual confirmation emails.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm | boolean | – | Leave false (the default) to get a preview without changing anything. Set true only after the person has seen the preview and agreed. |
| confirmation_token | string | – | Required when confirm is true: the confirmation_token from the preview of exactly these arguments. It expires after a few minutes; if it has, get a new preview. |
| customer_id | integer | – | An existing customer, from find_customer. Give this or new_customer. |
| idempotency_key | string | – | Required when confirm is true. Any unique string, for example a UUID. Reusing it with the same arguments returns the first result instead of acting twice. |
| new_customer | object | – | Details for someone not yet in the system. If the email already belongs to a customer, that customer is used. Some businesses also require phone, address, city or zip_code; the preview says which are… |
| notes | string | – | Optional note visible to staff. |
| provider_id | integer | yes | From list_services or find_open_slots. |
| service_id | integer | yes | From list_services. |
| start | string | yes | Start time "YYYY-MM-DD HH:MM" in the provider's time zone, exactly as find_open_slots returned it. |
No output schema declared.
No examples provided.
cancel_appointment Cancel an appointment ~222
Cancels an upcoming appointment. Easy!Appointments deletes it and emails the customer a cancellation notice; this cannot be undone. Two steps: call without confirm for a preview, then, after the person agrees, again with confirm: true, the confirmation_token from the preview and an idempotency_key.
| Name | Type | Req | Description |
|---|---|---|---|
| appointment_id | integer | yes | From list_appointments. |
| confirm | boolean | – | Leave false (the default) to get a preview without changing anything. Set true only after the person has seen the preview and agreed. |
| confirmation_token | string | – | Required when confirm is true: the confirmation_token from the preview of exactly these arguments. It expires after a few minutes; if it has, get a new preview. |
| idempotency_key | string | – | Required when confirm is true. Any unique string, for example a UUID. Reusing it with the same arguments returns the first result instead of acting twice. |
| reason | string | – | Optional reason. It is kept in this server's call log; Easy!Appointments has nowhere to store it. |
No output schema declared.
No examples provided.
find_customer Find a customer ~60
Searches customers by name, email or phone and returns up to 10 matches with their customer_id. If several people match, ask which one is meant before booking.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Part of a name, an email address or a phone number. |
No output schema declared.
No examples provided.
find_open_slots Find open appointment slots ~158
Finds open start times for one service over a range of days, across every provider who offers it or just one. Times are in the time zone of each provider, given in the result. Use this before booking or rescheduling.
| Name | Type | Req | Description |
|---|---|---|---|
| date_from | string | – | First day to search, YYYY-MM-DD. Defaults to today. |
| days | integer | – | How many days to search, 1 to 14. Default 7. |
| part_of_day | string | – | morning is before 12:00, afternoon 12:00 to 17:00, evening from 17:00. |
| provider_id | integer | – | Optional: only this provider. |
| service_id | integer | yes | The service, from list_services. |
No output schema declared.
No examples provided.
list_appointments List appointments ~118
Lists appointments for a customer, a provider and/or a date range, earliest first. Give at least one of customer_id, provider_id or date_from. Without dates it shows the next 30 days.
| Name | Type | Req | Description |
|---|---|---|---|
| customer_id | integer | – | From find_customer. |
| date_from | string | – | YYYY-MM-DD. Defaults to today; give an earlier date to see past visits. |
| date_to | string | – | YYYY-MM-DD, inclusive. Defaults to 30 days after date_from. |
| provider_id | integer | – | From list_services. |
No output schema declared.
No examples provided.
list_services List services and providers ~62
Lists the services this business offers (length, price) and which providers offer each one. Call this first to get the service_id and provider_id that the other tools need.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | – | Optional words to filter services by name, for example "massage". |
No output schema declared.
No examples provided.
reschedule_appointment Reschedule an appointment ~253
Moves an appointment to a new start time, optionally with another provider who offers the same service. Two steps: call without confirm for a preview, then, after the person agrees, again with confirm: true, the confirmation_token from the preview and an idempotency_key. Easy!Appointments emails the customer about the change.
| Name | Type | Req | Description |
|---|---|---|---|
| appointment_id | integer | yes | From list_appointments. |
| confirm | boolean | – | Leave false (the default) to get a preview without changing anything. Set true only after the person has seen the preview and agreed. |
| confirmation_token | string | – | Required when confirm is true: the confirmation_token from the preview of exactly these arguments. It expires after a few minutes; if it has, get a new preview. |
| idempotency_key | string | – | Required when confirm is true. Any unique string, for example a UUID. Reusing it with the same arguments returns the first result instead of acting twice. |
| new_start | string | yes | New start "YYYY-MM-DD HH:MM" in the time zone of the provider it moves to, from find_open_slots. |
| provider_id | integer | – | Optional: move to this provider. Defaults to the current one. |
No output schema declared.
No examples provided.
How do I install the Easy!Appointments MCP server?
Easy!Appointments is a hosted endpoint at https://ea-mcp-demo.qiyuanlabs.ai/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 · ea-mcp-demo.qiyuanlabs.ai
claude mcp add --transport http ai-qiyuanlabs-easyappointments 'https://ea-mcp-demo.qiyuanlabs.ai/mcp'
What is the Easy!Appointments MCP server?
Easy!Appointments is an MCP server listed in the public MCP registry as ai.qiyuanlabs/easyappointments. Find open slots, book, move and cancel Easy!Appointments bookings, with OAuth and a call log. This page covers its hosted endpoint (https://ea-mcp-demo.qiyuanlabs.ai/mcp).
Is the Easy!Appointments MCP server safe to use?
Easy!Appointments scores 77 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 Easy!Appointments MCP server expose?
Easy!Appointments exposes 7 tools: list_services, find_open_slots, find_customer, list_appointments, book_appointment, and 2 more. Their descriptions and schemas cost roughly 1,211 tokens of context every time the server is loaded.
Does the Easy!Appointments MCP server require authentication?
Yes. Easy!Appointments 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 Easy!Appointments MCP server still maintained?
Easy!Appointments is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.