Checkfront MCP by usefulapi
io.usefulapi/checkfrontusefulapi.iostreamable-httpv1.40.4Scanned
Check Checkfront availability and rates, and manage booking sessions, bookings, customers and notes.
20 tools: 6 can delete or cancel things and 14 only read.
- Reads private data · 6
- Reads text others write · 4
- Can send data out · 0
- 1 finding
The remote endpoint did not answer the last look. Remote posture
Anlyon alternative
6 of these tools change something. Run those as governed actions.
Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.
Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.
Import an OpenAPI spec →What the Checkfront MCP by usefulapi can do
The Checkfront MCP by usefulapi is published by usefulapi.io, a domain the MCP Registry verified. It has 20 tools. It can delete or cancel things (6 tools: checkfront_add_to_booking_session, checkfront_end_booking_session, checkfront_create_booking, checkfront_update_booking_status and 2 more). 14 tools only read.
6 tools read private data (checkfront_get_availability_calendar, checkfront_list_booking_notes, checkfront_get_booking_form and 3 more); 4 tools bring in text other people can write (checkfront_get_company, checkfront_get_booking_form, checkfront_search_customers and 1 more).
The fixed checks matched 1 finding (credentials-mention). Each one comes with the text it matched.
Last scanned Oct 25, 2026, version 1.40.4.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
20 tools
Deletes or cancels 6Claude Code: deny
checkfront_add_booking_noteAdd a note to a booking, logged under the staff account the API acts on behalf of.No findings
Why it is in this group
- The name "checkfront_add_booking_note" says "add": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Add a note to a booking, logged under the staff account the API acts on behalf of. Checkfront: POST /api/3.0/booking/{booking_id}/note.
Annotations the server declares
- title: Add a note to a booking
- destructiveHint: true
checkfront_add_to_booking_sessionStart or modify a booking session: add one or more SLIPs (from a rated checkfront_get_item / checkfront_list_items call), replace a line with a new SLIP (line_id + slip), or alter …No findings
Why it is in this group
- The name "checkfront_add_to_booking_session" says "add": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Start or modify a booking session: add one or more SLIPs (from a rated checkfront_get_item / checkfront_list_items call), replace a line with a new SLIP (line_id + slip), or alter lines (quantity, 'remove', 'optin'/'optout' for package add-ons). Holds the inventory while the session is open; NOTHING is booked until checkfront_create_booking. Returns the session_id to reuse. Checkfront: POST /api/3.0/booking/session.
Annotations the server declares
- title: Add items to a booking session
- destructiveHint: true
checkfront_check_in_bookingMark a guest as arrived (check in) or departed (check out).No findings
Why it is in this group
- The description's first verb is "mark": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Mark a guest as arrived (check in) or departed (check out). Checkfront adds a note under the acting account. VOID and cancelled bookings cannot be checked in or out. Checkfront: POST /api/3.0/booking/{booking_id}/checkin or /checkout.
Annotations the server declares
- title: Check a booking in or out
- destructiveHint: true
checkfront_create_bookingCommit a booking: from a session_id (built with checkfront_add_to_booking_session) or directly from SLIPs, plus the customer form fields (see checkfront_get_booking_form for which …No findings
Why it is in this group
- The name "checkfront_create_booking" says "create": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Commit a booking: from a session_id (built with checkfront_add_to_booking_session) or directly from SLIPs, plus the customer form fields (see checkfront_get_booking_form for which are required — typically customer_name and customer_email). Creates a real reservation that consumes inventory and may notify the customer; change it later with checkfront_update_booking_status. Returns the new booking's ids and any invoice/payment URL. Checkfront: POST /api/3.0/booking/create.
Annotations the server declares
- title: Create a booking
- destructiveHint: true
checkfront_end_booking_sessionAbandon a booking session: 'clear' empties its items, 'end' closes it.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Abandon a booking session: 'clear' empties its items, 'end' closes it. Releases the inventory it was holding; no booking is affected. Checkfront: POST /api/3.0/booking/session/clear or /booking/session/end.
Annotations the server declares
- title: End or clear a booking session
- destructiveHint: true
checkfront_update_booking_statusSet a booking's status — e.g.No findings
Why it is in this group
- The name "checkfront_update_booking_status" says "update": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Set a booking's status — e.g. confirm a pending booking (PAID/PART), put it on HOLD or WAIT(list), or cancel it (VOID/STOP). Reversible: set it back to the previous status the same way. Does NOT record a payment. Optionally triggers the account's customer notifications. Checkfront: POST /api/3.0/booking/{booking_id}/update.
Annotations the server declares
- title: Change a booking's status
- destructiveHint: true
Only reads 14Show 14 read-only tools
checkfront_get_availability_calendarDay-by-day available inventory over a date range — for one item (item_ids with a single id), several items, or a whole category.Reads private dataNo findings
Why it is in this group
- The name "checkfront_get_availability_calendar" says "get": a word for reading.
What it can reach
- private-dataThe name "checkfront_get_availability_calendar" says "get" and "calendar": it reads calendars.
Description, as the server wrote it Day-by-day available inventory over a date range — for one item (item_ids with a single id), several items, or a whole category. Use it to answer 'which days next month still have space?'. Checkfront: GET /api/3.0/item/{item_id}/cal or GET /api/3.0/item/cal.
Annotations the server declares
- title: Get an availability calendar
- readOnlyHint: true
checkfront_get_bookingFetch extended information on one booking — status, dates, customer, form fields, line items and totals.No findings
Why it is in this group
- The name "checkfront_get_booking" says "get": a word for reading.
Description, as the server wrote it Fetch extended information on one booking — status, dates, customer, form fields, line items and totals. Checkfront: GET /api/3.0/booking/{booking_id}.
Annotations the server declares
- title: Get a booking
- readOnlyHint: true
checkfront_get_booking_formFetch the customer-details form for a booking (booking_form_ui): every field id (customer_name, customer_email, …), its label, type and whether it is required.Reads private dataReads text others writeNo findings
Why it is in this group
- The name "checkfront_get_booking_form" says "get": a word for reading.
What it can reach
- private-dataThe description's first sentence says "fetch" and "email": it reads mail.
- untrusted-inputThe description's first sentence says "fetch" and "email": it reads inbound email, which other people can write.
Description, as the server wrote it Fetch the customer-details form for a booking (booking_form_ui): every field id (customer_name, customer_email, …), its label, type and whether it is required. Call this before checkfront_create_booking to know which `form` fields to send. Checkfront: GET /api/3.0/booking/form.
Annotations the server declares
- title: Get the booking form fields
- readOnlyHint: true
checkfront_get_booking_sessionRead a booking session — the in-progress 'cart' — with its line items (keyed by line_id), dates, sub_total, tax, total and amount due.No findings
Why it is in this group
- The name "checkfront_get_booking_session" says "get": a word for reading.
Description, as the server wrote it Read a booking session — the in-progress 'cart' — with its line items (keyed by line_id), dates, sub_total, tax, total and amount due. Checkfront: GET /api/3.0/booking/session.
Annotations the server declares
- title: Get a booking session
- readOnlyHint: true
checkfront_get_companyFetch the connected Checkfront account's company configuration — name, URL, plan, currency, timezone, locale and date/time formats.Reads text others write1 finding
Why it is in this group
- The name "checkfront_get_company" says "get": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "fetch" and "url": it reads web pages, which anyone can write.
Findings
- Info
The description mentions "credentials".
What this check looks forMatched text
description: "...ts. A cheap way to confirm the host and credentials work. Checkfront: GET /api/3.0/company."
Description, as the server wrote it Fetch the connected Checkfront account's company configuration — name, URL, plan, currency, timezone, locale and date/time formats. A cheap way to confirm the host and credentials work. Checkfront: GET /api/3.0/company.
Annotations the server declares
- title: Get company settings
- readOnlyHint: true
checkfront_get_customerFetch one customer's contact details and their bookings (codes with created dates).Reads private dataNo findings
Why it is in this group
- The name "checkfront_get_customer" says "get": a word for reading.
What it can reach
- private-dataThe description's first sentence says "fetch" and "contact": it reads contacts.
Description, as the server wrote it Fetch one customer's contact details and their bookings (codes with created dates). Checkfront: GET /api/3.0/customer/{customer_id}.
Annotations the server declares
- title: Get a customer
- readOnlyHint: true
checkfront_get_itemFetch one inventory item's details.No findings
Why it is in this group
- The name "checkfront_get_item" says "get": a word for reading.
Description, as the server wrote it Fetch one inventory item's details. Pass start_date / end_date and param quantities (e.g. {"adults": 2}) for a RATED response with availability (rate.status, rate.available), the price breakdown and the SLIP used to book it. For parent/child grouped items, rate the CHILD item. Checkfront: GET /api/3.0/item/{item_id}.
Annotations the server declares
- title: Get an item
- readOnlyHint: true
checkfront_list_booking_notesList the notes left on bookings across the account (default: the past 30 days), each with its booking code, author account id (0 = customer), date, body and whether it is private.Reads private dataNo findings
Why it is in this group
- The name "checkfront_list_booking_notes" says "list": a word for reading.
What it can reach
- private-dataThe name "checkfront_list_booking_notes" says "list" and "note": it reads notes.
- private-dataThe description's first sentence says "list" and "note": it reads notes.
Description, as the server wrote it List the notes left on bookings across the account (default: the past 30 days), each with its booking code, author account id (0 = customer), date, body and whether it is private. Checkfront: GET /api/3.0/booking/notes.
Annotations the server declares
- title: List booking notes
- readOnlyHint: true
checkfront_list_bookingsList bookings, newest filters first — by status, customer, dates, item or partner.No findings
Why it is in this group
- The name "checkfront_list_bookings" says "list": a word for reading.
Description, as the server wrote it List bookings, newest filters first — by status, customer, dates, item or partner. Each row has the booking code, status, totals (total, tax_total, paid_total), customer name/email, summary and date_desc. Paged (default 100/page); the response's request.pages tells you how many pages exist. Checkfront: GET /api/3.0/booking/index.
Annotations the server declares
- title: List bookings
- readOnlyHint: true
checkfront_list_categoriesList the inventory categories (e.g.No findings
Why it is in this group
- The name "checkfront_list_categories" says "list": a word for reading.
Description, as the server wrote it List the inventory categories (e.g. Tours, Rentals, Accommodations) with their ids, names, display order and item counts. Checkfront: GET /api/3.0/category.
Annotations the server declares
- title: List item categories
- readOnlyHint: true
checkfront_list_eventsList the date-based events that change price or availability — seasonal rates (SE), specials (SP), discounts (DC), closures (status U) — with their dates, recurrence, pricing rule …No findings
Why it is in this group
- The name "checkfront_list_events" says "list": a word for reading.
Description, as the server wrote it List the date-based events that change price or availability — seasonal rates (SE), specials (SP), discounts (DC), closures (status U) — with their dates, recurrence, pricing rule and the items/categories they apply to. Checkfront: GET /api/3.0/event.
Annotations the server declares
- title: List events
- readOnlyHint: true
checkfront_list_itemsList the enabled inventory items (tours, activities, rentals, rooms).No findings
Why it is in this group
- The name "checkfront_list_items" says "list": a word for reading.
Description, as the server wrote it List the enabled inventory items (tours, activities, rentals, rooms). With NO dates this is the plain catalogue. Pass start_date (and end_date / param quantities) to get a RATED response: per-item availability, pricing and a SLIP token — the SLIP is what checkfront_add_to_booking_session needs to book the item. Checkfront: GET /api/3.0/item.
Annotations the server declares
- title: List inventory items
- readOnlyHint: true
checkfront_list_staff_accountsList the staff (and partner) accounts on the Checkfront account — ids, names, emails, login ids and whether enabled.Reads private dataReads text others writeNo findings
Why it is in this group
- The name "checkfront_list_staff_accounts" says "list": a word for reading.
What it can reach
- private-dataThe description's first sentence says "list" and "email": it reads mail.
- untrusted-inputThe description's first sentence says "list" and "email": it reads inbound email, which other people can write.
Description, as the server wrote it List the staff (and partner) accounts on the Checkfront account — ids, names, emails, login ids and whether enabled. The account_id is what CHECKFRONT_ON_BEHALF takes. Checkfront: GET /api/3.0/account.
Annotations the server declares
- title: List staff accounts
- readOnlyHint: true
checkfront_search_customersLook up customers by exact email, full name or phone number (exact matches; non-unique fields such as name can return several).Reads private dataReads text others writeNo findings
Why it is in this group
- The name "checkfront_search_customers" says "search": a word for reading.
What it can reach
- private-dataThe description's first sentence says "email": it reads mail.
- untrusted-inputThe description's first sentence says "email": it reads inbound email, which other people can write.
Description, as the server wrote it Look up customers by exact email, full name or phone number (exact matches; non-unique fields such as name can return several). Results are in the `customers` object. Checkfront: GET /api/3.0/customer.
Annotations the server declares
- title: Search customers
- readOnlyHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.
- Reads private data6
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write4
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:34 UTC, unchanged since Oct 29, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- no
- HTTP status of an anonymous initialize
- not observed
- tools/list served without credentials
- no
- Tools that change things, listed without credentials
- 0
- Protocol version
- not observed
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
The probe stopped: The server redirected a POST to a different request.
Posture changes
- Oct 29, 2026
- Reachable: yes to no
- HTTP status of an anonymous initialize: 200 to none
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 6 to 0
- Protocol version: 2025-06-18 to none
- RFC 9728 protected resource metadata: https://checkfront.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
- Authorization servers: https://checkfront.usefulapi.io to none
- Dynamic client registration: yes to not observed
- Client ID metadata documents: no to not observed
Findings
Matches of fixed checks, with the text they matched.
The description mentions "credentials".
What this check looks forMatched text
description: "...ts. A cheap way to confirm the host and credentials work. Checkfront: GET /api/3.0/company."
History
Changes to its tool definitions and to its remote endpoint, newest first.
PostureRemote posture changed. Reachable: yes -> no; HTTP status of an anonymous initialize: 200 -> none; tools/list served without credentials: yes -> no (and 6 more).View diff
- Reachable: yes to no
- HTTP status of an anonymous initialize: 200 to none
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 6 to 0
- Protocol version: 2025-06-18 to none
- RFC 9728 protected resource metadata: https://checkfront.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
- Authorization servers: https://checkfront.usefulapi.io to none
- Dynamic client registration: yes to not observed
- Client ID metadata documents: no to not observed
Install
Pinned to version 1.40.4. Values in angle brackets are yours to fill in.
claude mcp add --transport http checkfront https://checkfront.usefulapi.io/mcpclaude mcp add --transport http checkfront https://checkfront.usefulapi.io/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__checkfront__checkfront_get_company",
"mcp__checkfront__checkfront_list_categories",
"mcp__checkfront__checkfront_list_items",
"mcp__checkfront__checkfront_get_item",
"mcp__checkfront__checkfront_get_availability_calendar",
"mcp__checkfront__checkfront_list_bookings",
"mcp__checkfront__checkfront_get_booking",
"mcp__checkfront__checkfront_list_booking_notes",
"mcp__checkfront__checkfront_get_booking_form",
"mcp__checkfront__checkfront_get_booking_session",
"mcp__checkfront__checkfront_search_customers",
"mcp__checkfront__checkfront_get_customer",
"mcp__checkfront__checkfront_list_events",
"mcp__checkfront__checkfront_list_staff_accounts"
],
"ask": [],
"deny": [
"mcp__checkfront__checkfront_add_to_booking_session",
"mcp__checkfront__checkfront_end_booking_session",
"mcp__checkfront__checkfront_create_booking",
"mcp__checkfront__checkfront_update_booking_status",
"mcp__checkfront__checkfront_add_booking_note",
"mcp__checkfront__checkfront_check_in_booking"
]
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as checkfront. Review it before you use it.
Capability tags behind 7 rules
- mcp__checkfront__checkfront_get_company untrusted-input
- mcp__checkfront__checkfront_get_availability_calendar private-data
- mcp__checkfront__checkfront_list_booking_notes private-data
- mcp__checkfront__checkfront_get_booking_form private-data, untrusted-input
- mcp__checkfront__checkfront_search_customers private-data, untrusted-input
- mcp__checkfront__checkfront_get_customer private-data
- mcp__checkfront__checkfront_list_staff_accounts private-data, untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.usefulapi/checkfront/verify?hash=c9d24b0ac132c4761f9a8aa99493fb38c080d6caa0e433ad42256d8a3da51cad" | jq -e '.changed == false'Pinned hash c9d24b0ac132, from Oct 25, 2026, 23:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.usefulapi/checkfront/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.usefulapi/checkfront)Source: MCP Registry · repository. Synced Nov 18, 2026, 11:18 UTC.
Checkfront MCP by usefulapi: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Checkfront MCP by usefulapi safe?
- No scan can promise that. What its definitions show: 20 tools, 6 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Checkfront MCP by usefulapi delete data?
- Yes. 6 tools can delete, cancel or revoke something: checkfront_add_to_booking_session, checkfront_end_booking_session, checkfront_create_booking, checkfront_update_booking_status, checkfront_add_booking_note and checkfront_check_in_booking.
Can the Checkfront MCP by usefulapi do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Checkfront MCP by usefulapi have?
- 20 tools: 6 destructive, 14 read. checkfront_add_to_booking_session, checkfront_end_booking_session, checkfront_create_booking, checkfront_update_booking_status, checkfront_add_booking_note, checkfront_check_in_booking, checkfront_get_company, checkfront_list_categories and 12 more.
Does the Checkfront MCP by usefulapi need sign-in or OAuth?
- Its remote endpoint did not answer the last anonymous look.
Does the Checkfront MCP by usefulapi send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Checkfront MCP by usefulapi changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Oct 25, 2026.