Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Appty

REMOTE · GETAPPTY.COM

Find open slots on any appty link and book solo providers. Providers manage bookings by API key.

Available components

+3 this week 76 Trust /100

Last scanned (1 hour ago)

Scores higher than 66% of remote servers

Reachable. Last reached 5 Nov 2026.

Category CRM and Sales

Trust breakdown (7 categories)

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 Security63
Transport & Reachability100
Schema Quality & AI Usability73
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1324 tokens (~120/item across 11 items; 11 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 Management70
  • Stability observed for 21 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage95
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 84% 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
  • All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 12 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
Changelog

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 +1

    No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.

  • 3 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.

  • 1 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

  • 29 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

  • 27 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

  • 25 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

  • 23 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

  • 21 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

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://getappty.com/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=getappty.com CN=YR2,O=Let's Encrypt,C=US 7 Oct 2026 5 Jan 2027 RSA 2048 SHA256-RSA 6c1dff9033fd2247f978a75fdef11bfe56f
SANs: getappty.com
CN=YR2,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA 4ebd24947e24d394802d84a52fd5b319
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of getappty.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
getappty.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=63072000

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://getappty.com/api/mcp Verified 200
http (plaintext) http://getappty.com/api/mcp HTTPS enforced 308 https://getappty.com/api/mcp
MCP tools · 11 exposed · ~1,209 tokens

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 →

Tool Tokens
book_session ~167

Book a client into a service at a start time, the same way the dashboard books. Returns a preview first and only acts when confirm=true. A past start is saved as completed with no email. A future start emails the usual confirmation. No money moves through the assistant. Any pay link is only a request the client pays on Appty.

NameTypeReqDescription
client_idstringyesClient id from list_clients.
confirmboolean–Set true only after the caller has seen a preview and wants it done. Anything else, including the string "true", is a preview and changes nothing.
service_idstringyesService id. One-off shells are refused.
startstringyesSession start, ISO 8601. Does not have to be an open public slot.

No output schema declared.

No examples provided.

cancel_booking ~118

Cancel one booking under the provider's cancellation policy and email the client. Returns a preview first and only acts when confirm=true. No money moves through the assistant. Any refund or fee is applied by Appty, the same as the dashboard. The client pays anything still due on Appty.

NameTypeReqDescription
booking_idstringyes–
confirmboolean–Set true only after the caller has seen a preview and wants it done. Anything else, including the string "true", is a preview and changes nothing.
reasonstring––

No output schema declared.

No examples provided.

find_open_slots ~165

Open start times for a public service, using the same slot rules as the booking page. from_date and to_date are YYYY-MM-DD and at most 31 days apart. Each start is ISO 8601 with the provider's offset, plus a provider-local label.

NameTypeReqDescription
from_datestringyesFirst day to include, YYYY-MM-DD
service_idstringyesService id from get_provider
slugstringyesBooking link slug, the part after getappty.com/
timezonestring–IANA zone the dates are in. Defaults to the provider's zone. Slot labels stay in the provider's zone.
to_datestringyesLast day to include, YYYY-MM-DD. At most 31 days after from_date.

No output schema declared.

No examples provided.

get_booking_link ~96

Check that a start is still open, then return a link to the booking page with that service and time selected. The client confirms and pays on Appty. Nothing is booked here.

NameTypeReqDescription
service_idstringyesService id from get_provider
slugstringyesBooking link slug, the part after getappty.com/
startstringyesSlot start, ISO 8601, from find_open_slots

No output schema declared.

No examples provided.

get_provider ~58

Public booking page for a provider slug: name, headline, time zone, currency, services, upcoming group sessions, and the booking URL. No client data.

NameTypeReqDescription
slugstringyesBooking link slug, the part after getappty.com/

No output schema declared.

No examples provided.

list_bookings ~99

This provider's bookings. Omit from and to for upcoming sessions. Never includes pay or manage tokens.

NameTypeReqDescription
fromstring–Include sessions starting at or after this ISO 8601 time. When from and to are both omitted, this is now.
limitinteger–Default 50. Maximum 100.
statusstring––
tostring–Include sessions starting before this ISO 8601 time.

No output schema declared.

No examples provided.

list_clients ~60

This provider's clients: id, name, email, phone, billing currency, and default pay mode.

NameTypeReqDescription
limitinteger–Default 50. Maximum 100.
querystring–Case-insensitive match on the client's name or email.

No output schema declared.

No examples provided.

reschedule_booking ~112

Move a booking to an open slot. The client is not emailed. Returns a preview first and only acts when confirm=true. No money moves through the assistant.

NameTypeReqDescription
booking_idstringyes–
confirmboolean–Set true only after the caller has seen a preview and wants it done. Anything else, including the string "true", is a preview and changes nothing.
new_startstringyesNew start, ISO 8601. Must be an open slot for this booking's length.

No output schema declared.

No examples provided.

send_invoice ~150

Create one invoice per currency for a client's sessions (by id or by calendar month) and email it. Returns a preview first and only acts when confirm=true. No money moves through the assistant. The invoice only sends a request the client pays on Appty.

NameTypeReqDescription
booking_idsarray–Sessions to put on the invoice. Pass this or period.
client_idstringyes–
confirmboolean–Set true only after the caller has seen a preview and wants it done. Anything else, including the string "true", is a preview and changes nothing.
periodstring–Calendar month YYYY-MM in the provider's time zone. Uninvoiced sessions in that month.

No output schema declared.

No examples provided.

send_pay_link ~150

Email a pay link for one booking, or for a client's unpaid sessions and invoices. Returns a preview first and only acts when confirm=true. No money moves through the assistant. This only sends a request the client pays on Appty. Group spots, packages, and fees are not emailed.

NameTypeReqDescription
booking_id––Email a pay link for this booking. Pass this or client_id.
client_idstring–Email a pay reminder for each unpaid session and invoice this client has. Pass this or booking_id.
confirmboolean–Set true only after the caller has seen a preview and wants it done. Anything else, including the string "true", is a preview and changes nothing.

No output schema declared.

No examples provided.

who_owes ~34

Unpaid balances for this provider, grouped by client and currency. Same figures as the dashboard who-owes page.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Install

How do I install the Appty MCP server?

Appty is a hosted endpoint at https://getappty.com/api/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 · getappty.com

# add to Claude Code
claude mcp add --transport http com-getappty-appty 'https://getappty.com/api/mcp'
Common questions

What is the Appty MCP server?

Appty is an MCP server listed in the public MCP registry as com.getappty/appty. Find open slots on any appty link and book solo providers. Providers manage bookings by API key. This page covers its hosted endpoint (https://getappty.com/api/mcp).

Is the Appty MCP server safe to use?

Appty scores 76 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 Appty MCP server expose?

Appty exposes 11 tools: get_provider, find_open_slots, get_booking_link, list_bookings, list_clients, and 6 more. Their descriptions and schemas cost roughly 1,209 tokens of context every time the server is loaded.

Does the Appty MCP server require authentication?

No. We connected to Appty without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Appty MCP server still maintained?

Appty 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.