io.usefulapi/checkfront
REMOTE · CHECKFRONT.USEFULAPI.IO · SCANNED OCT 4
Check Checkfront availability and rates, and manage booking sessions, bookings, customers and notes.
Available components
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 Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 429, which proves neither a plaintext path nor enforcement. 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
Transport & Reachability0
- Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http. See how to fix → View diagnostics → Unverified
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 6 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm. Claim this server and supply a read-only token to verify it and lift the score.
How do I install the io.usefulapi/checkfront MCP server?
io.usefulapi/checkfront is a hosted endpoint at https://checkfront.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 · checkfront.usefulapi.io
claude mcp add --transport http io-usefulapi-checkfront 'https://checkfront.usefulapi.io/mcp'
{
"mcpServers": {
"io-usefulapi-checkfront": {
"url": "https://checkfront.usefulapi.io/mcp"
}
}
} {
"servers": {
"io-usefulapi-checkfront": {
"type": "http",
"url": "https://checkfront.usefulapi.io/mcp"
}
}
} [mcp_servers.io-usefulapi-checkfront] url = "https://checkfront.usefulapi.io/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"io-usefulapi-checkfront": {
"type": "remote",
"url": "https://checkfront.usefulapi.io/mcp",
"enabled": true
}
}
} openclaw mcp add io-usefulapi-checkfront --url 'https://checkfront.usefulapi.io/mcp' --transport streamable-http
mcp_servers:
io-usefulapi-checkfront:
url: "https://checkfront.usefulapi.io/mcp" {
"McpServers": {
"io-usefulapi-checkfront": {
"Transport": "http",
"Url": "https://checkfront.usefulapi.io/mcp"
}
}
} assistant mcp add io-usefulapi-checkfront -t streamable-http -u 'https://checkfront.usefulapi.io/mcp'
{
"mcpServers": {
"io-usefulapi-checkfront": {
"type": "http",
"url": "https://checkfront.usefulapi.io/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 4 Oct 26 −10
- Transport: pass → unverified ▼ security
- 3 Oct 26 +10
- Transport: fail → pass ▲ security
- 1 Oct 26 −54
- Endpoint reachability: reachable → not serving MCP ▼ security
- Tool safety: pass → unverified ▼ security
- Authorization: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 30 Sept 26 +54
- Authorization: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- First check of Judged manipulation: pass security
- MCP protocol: unverified → fail ▼ 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
- 29 Sept 26 18
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 4 Oct 2026 · Probed https://checkfront.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 checkfront.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 8 | Verified |
| usefulapi.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|---|
| HTTP status | 429 |
| Header | Value |
|---|---|
| x-frame-options | SAMEORIGIN |
| referrer-policy | same-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://checkfront.usefulapi.io/mcp | Auth required | 401 | |
| http (plaintext) | http://checkfront.usefulapi.io/mcp | Inconclusive | 429 |
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 →
checkfront_add_booking_note Add a note to a booking ~88
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.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | yes | The note text, up to 3000 characters. |
| booking_id | string | yes | The booking code identifying the booking, e.g. CFPP-290317. |
No output schema declared.
No examples provided.
checkfront_add_to_booking_session Add items to a booking session (cart) ~242
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.
| Name | Type | Req | Description |
|---|---|---|---|
| alter | object | – | Changes keyed by line_id, e.g. {"3": 5, "2.1": "optin", "1": "remove"} (a number sets the quantity). |
| line_id | string | – | With a single slip: the session line to REPLACE with it (to change a regular item's options). |
| session_id | string | – | Existing session to modify. Omit to start a new session. |
| slip | array | – | One or more SLIP strings to add, e.g. ["18.20171005X1-adults.1-children.0"]. |
No output schema declared.
No examples provided.
checkfront_check_in_booking Check a booking in or out ~109
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.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | – | 'checkin' (default) or 'checkout'. |
| booking_id | string | yes | The booking code identifying the booking, e.g. CFPP-290317. |
No output schema declared.
No examples provided.
checkfront_create_booking Create a booking ~179
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.
| Name | Type | Req | Description |
|---|---|---|---|
| form | object | yes | Customer form fields, e.g. {"customer_name": "John Smith", "customer_email": "john@example.com"}. Sent as form[customer_name]=…. |
| session_id | string | – | The session holding the items to book. |
| slip | array | – | Instead of a session: SLIP strings to book directly. |
No output schema declared.
No examples provided.
checkfront_end_booking_session End or clear a booking session ~101
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.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | – | 'end' (default) closes the session; 'clear' empties it. |
| session_id | string | yes | The session to clear or end. |
No output schema declared.
No examples provided.
checkfront_get_availability_calendar Get an availability calendar ~177
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.
| Name | Type | Req | Description |
|---|---|---|---|
| category_id | integer | – | Instead of item ids, a category of items. |
| end_date | string | – | Range end date — YYYYMMDD, YYYY-MM-DD, or a relative date such as "today". |
| item_ids | array | – | Item ids. One id queries that item's calendar; several query them together. |
| start_date | string | – | Range start date — YYYYMMDD, YYYY-MM-DD, or a relative date such as "today". |
No output schema declared.
No examples provided.
checkfront_get_booking Get a booking ~70
Fetch extended information on one booking — status, dates, customer, form fields, line items and totals. Checkfront: GET /api/3.0/booking/{booking_id}.
| Name | Type | Req | Description |
|---|---|---|---|
| booking_id | string | yes | The booking code identifying the booking, e.g. CFPP-290317. |
No output schema declared.
No examples provided.
checkfront_get_booking_form Get the booking form fields ~77
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
checkfront_get_booking_session Get a booking session (cart) ~79
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.
| Name | Type | Req | Description |
|---|---|---|---|
| session_id | string | yes | The session_id returned by checkfront_add_to_booking_session. |
No output schema declared.
No examples provided.
checkfront_get_company Get company settings ~59
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
checkfront_get_customer Get a customer ~60
Fetch one customer's contact details and their bookings (codes with created dates). Checkfront: GET /api/3.0/customer/{customer_id}.
| Name | Type | Req | Description |
|---|---|---|---|
| customer_id | string | yes | The customer id (e.g. 25) or customer code. |
No output schema declared.
No examples provided.
checkfront_get_item Get an item (optionally with availability and rates) ~328
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}.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | – | (rated) Alias of start_date for same-day bookings — YYYYMMDD, YYYY-MM-DD, or a relative date such as "today". |
| discount_code | string | – | (rated) Discount code to apply to the price. |
| end_date | string | – | (rated) Booking end date — YYYYMMDD, YYYY-MM-DD, or a relative date such as "today". |
| end_time | string | – | (rated) End time, for hourly bookings. |
| item_id | integer | yes | The item id. |
| packages | boolean | – | Include package options. |
| param | object | – | Booking parameters (quantities) keyed by the parameter ids configured in your account, e.g. {"adults": 2, "children": 1}. Sent as param[adults]=2. |
| rules | string | – | 'soft' avoids date-based rule errors; 'off' disables rule checking. |
| start_date | string | – | (rated) Booking start date — YYYYMMDD, YYYY-MM-DD, or a relative date such as "today". |
| start_time | string | – | (rated) Start time, for hourly bookings. |
No output schema declared.
No examples provided.
checkfront_list_booking_notes List booking notes ~101
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.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | – | Filter by a day (YYYY-MM-DD or ISO-8601) or a whole month (e.g. "2026-09"). |
No output schema declared.
No examples provided.
checkfront_list_bookings List bookings ~396
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.
| Name | Type | Req | Description |
|---|---|---|---|
| created_date | string | – | Date the booking was created. A date string or unix timestamp; prefix with '<' or '>' for before/after (e.g. ">2026-01-01"). |
| customer_email | string | – | Only bookings for this customer email. |
| customer_id | integer | – | Only bookings for this customer id. |
| end_date | string | – | Booking end (check-out) date. A date string or unix timestamp; prefix with '<' or '>' for before/after (e.g. ">2026-01-01"). |
| item_id | integer | – | Only bookings containing this item. |
| last_modified | string | – | Date the booking last changed — useful for 'changed since' syncs. A date string or unix timestamp; prefix with '<' or '>' for before/after (e.g. ">2026-01-01"). |
| limit | integer | – | Bookings per page, 1-100 (default 100). |
| page | integer | – | Page number, starting at 1. |
| partner_id | string | – | Only bookings attributed to this partner account. |
| start_date | string | – | Booking start (check-in) date. A date string or unix timestamp; prefix with '<' or '>' for before/after (e.g. ">2026-01-01"). |
| status_id | string | – | Booking status code, e.g. PEND, HOLD, PART, PAID, WAIT, STOP, VOID. |
No output schema declared.
No examples provided.
checkfront_list_categories List item categories ~50
List the inventory categories (e.g. Tours, Rentals, Accommodations) with their ids, names, display order and item counts. Checkfront: GET /api/3.0/category.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
checkfront_list_events List events (seasons, specials, closures, discounts) ~68
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
checkfront_list_items List inventory items (optionally with availability and rates) ~393
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.
| Name | Type | Req | Description |
|---|---|---|---|
| available | integer | – | (rated) Only items with at least this many left in stock. |
| category_id | integer | – | Only items in this category. |
| date | string | – | (rated) Alias of start_date for same-day bookings — YYYYMMDD, YYYY-MM-DD, or a relative date such as "today". |
| discount_code | string | – | (rated) Discount code to apply to the price. |
| end_date | string | – | (rated) Booking end date — YYYYMMDD, YYYY-MM-DD, or a relative date such as "today". |
| end_time | string | – | (rated) End time, for hourly bookings. |
| item_id | string | – | Comma-separated list of item ids to filter to, e.g. 17,18. |
| keyword | string | – | Only items whose name contains this keyword. |
| packages | boolean | – | Include package options. |
| param | object | – | Booking parameters (quantities) keyed by the parameter ids configured in your account, e.g. {"adults": 2, "children": 1}. Sent as param[adults]=2. |
| rules | string | – | 'soft' avoids date-based rule errors; 'off' disables rule checking. |
| start_date | string | – | (rated) Booking start date — YYYYMMDD, YYYY-MM-DD, or a relative date such as "today". |
| start_time | string | – | (rated) Start time, for hourly bookings. |
No output schema declared.
No examples provided.
checkfront_list_staff_accounts List staff accounts ~63
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
checkfront_search_customers Search customers ~104
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.
| Name | Type | Req | Description |
|---|---|---|---|
| customer_email | string | – | Exact customer email address. |
| customer_id | string | – | Customer code/id. |
| customer_name | string | – | Exact full name. |
| customer_phone | string | – | Exact phone number. |
No output schema declared.
No examples provided.
checkfront_update_booking_status Change a booking's status ~176
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.
| Name | Type | Req | Description |
|---|---|---|---|
| booking_id | string | yes | The booking code identifying the booking, e.g. CFPP-290317. |
| notify | boolean | – | Send the account's notifications for this change (default false). |
| status_id | string | yes | The new status code. Defaults: PEND, HOLD, PART, PAID, WAIT, STOP, VOID (plus any custom statuses in Manage > Layout > Statuses). |
No output schema declared.
No examples provided.
What is the io.usefulapi/checkfront MCP server?
io.usefulapi/checkfront is an MCP server listed in the public MCP registry as io.usefulapi/checkfront. Check Checkfront availability and rates, and manage booking sessions, bookings, customers and notes. This page covers its hosted endpoint (https://checkfront.usefulapi.io/mcp).
Is the io.usefulapi/checkfront MCP server safe to use?
io.usefulapi/checkfront scores 18 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 io.usefulapi/checkfront MCP server expose?
io.usefulapi/checkfront exposes 20 tools: checkfront_get_company, checkfront_list_categories, checkfront_list_items, checkfront_get_item, checkfront_get_availability_calendar, and 15 more. Their descriptions and schemas cost roughly 2,920 tokens of context every time the server is loaded.
Does the io.usefulapi/checkfront MCP server require authentication?
Its publisher declares no required credentials for io.usefulapi/checkfront. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the io.usefulapi/checkfront MCP server still maintained?
io.usefulapi/checkfront is still listed as active in the MCP registry. We last reached this channel on 4 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.