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.

ThinkReservations MCP by usefulapi

REMOTE · THINKRESERVATIONS.USEFULAPI.IO

Read rooms, rates, inventory, reservations and price quotes in ThinkReservations.

18 Trust /100

Last scanned (9 hours ago)

Scores higher than 4% of remote servers

Reachable. Last reached 5 Nov 2026.

Category E-commerce

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 Security46
Transport & Reachability0
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: 5 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.

What we tested

Checks we ran (4)

  • TLS certificate
  • HSTS header
  • DNSSEC
  • Transport

Checks we could not complete (7)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation not yet verified: we couldn't confirm whether this endpoint requires it.
  • HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven.
  • Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
  • Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
  • Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
  • Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
  • Capabilities in Capabilities (scores 0 for this)Capabilities not yet verified: we couldn't read the endpoint's capabilities.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

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.

  • 1 Nov 26 −47
    • Endpoint reachability: reachable → not serving MCP ▼ security
    • Tool safety: pass → unverified ▼ security
    • Authorization: pass → unverified ▼ security
    • Schema quality: 100 → unverified ▼ functional
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
  • 31 Oct 26 65

    First indexed and scored.

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://thinkreservations.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 thinkreservations.usefulapi.io. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
io. DS published 38690 8 Verified
usefulapi.io. No DS 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 302

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://thinkreservations.usefulapi.io/mcp Redirected 302 https://usefulapi.io/thinkreservations/
http (plaintext) http://thinkreservations.usefulapi.io/mcp Inconclusive 302 http://thinkreservations.usefulapi.io/mcp
MCP tools · 11 exposed · ~806 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
thinkreservations_get_availability ~155

Search what the property can sell for a stay: per bookable unit, the rate types with price for the whole stay, fees, taxes, deposit and total. Read-only quote, books nothing. Needs scope read:availability.

NameTypeReqDescription
child_agesarray–One age per child.
coupon_codestring–A promotion code the hotel has published.
end_datestringyesCheck-out date, yyyy-mm-dd.
number_of_adultsinteger–Adults (default 2).
number_of_childreninteger–Children (default 0).
number_of_petsinteger––
start_datestringyesCheck-in date, yyyy-mm-dd.

No output schema declared.

No examples provided.

thinkreservations_get_daily_rates ~97

Get the day-by-day price, minimum-stay rules and closed-to-arrival restrictions of one rate type for a date range. Needs scope read:rate.

NameTypeReqDescription
end_datestringyesLast date, yyyy-mm-dd.
rate_type_idstringyesRate type id.
room_type_idstring–Only this room type.
start_datestringyesFirst date, yyyy-mm-dd.

No output schema declared.

No examples provided.

thinkreservations_get_hotel ~35

Get the basic details of the property (hotel) the API key is bound to. Needs scope read:hotel.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

thinkreservations_get_inventory ~74

Get the daily inventory (units left) per room type for a date range. Needs scope read:availability.

NameTypeReqDescription
end_datestringyesLast date, yyyy-mm-dd.
room_type_idstring–Only this room type.
start_datestringyesFirst date, yyyy-mm-dd.

No output schema declared.

No examples provided.

thinkreservations_get_rate_type ~47

Get one rate type and its policies by id. Needs scope read:rate.

NameTypeReqDescription
rate_type_idstringyesRate type id from thinkreservations_list_rate_types.

No output schema declared.

No examples provided.

thinkreservations_list_blackouts ~71

List the blackouts in a date range: room-specific blocked dates (room id and date pairs), not whole-property closures. Needs scope read:availability.

NameTypeReqDescription
end_datestringyesLast date, yyyy-mm-dd.
start_datestringyesFirst date, yyyy-mm-dd.

No output schema declared.

No examples provided.

thinkreservations_list_promotions ~26

List the promotions configured for the property. Needs scope read:rate.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

thinkreservations_list_rate_types ~30

List the rate types the property offers, with their policies. Needs scope read:rate.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

thinkreservations_list_reservations ~197

List reservations (paged). Filter by stay dates, creation time or last-modified time (give at least one filter). Guest contact details appear only if the key has scope read:customer; otherwise customer is null. Needs scope read:reservation.

NameTypeReqDescription
created_at_end_date_timestring––
created_at_start_date_timestring––
pageinteger–Page number, starts at 0.
sizeinteger–Reservations per page (default 10).
sortstring–Sort expression, as the API reference describes.
stay_on_end_datestring–Reservations with a stay on or before this date.
stay_on_start_datestring–Reservations with a stay on or after this date.
updated_at_end_date_timestring––
updated_at_start_date_timestring–Last modified from this time. Use for incremental sync.

No output schema declared.

No examples provided.

thinkreservations_list_room_types ~37

List the room types (name and id). Use the ids to filter inventory and daily rates. Needs scope read:room.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

thinkreservations_list_rooms ~37

List the rooms of the property: name, description, room type and whether the room is active. Needs scope read:room.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Install

How do I install the ThinkReservations MCP by usefulapi server?

ThinkReservations MCP by usefulapi is a hosted endpoint at https://thinkreservations.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 · thinkreservations.usefulapi.io

# add to Claude Code
claude mcp add --transport http io-usefulapi-thinkreservations 'https://thinkreservations.usefulapi.io/mcp'
Common questions

What is the ThinkReservations MCP by usefulapi server?

ThinkReservations MCP by usefulapi is listed in the public MCP registry as io.usefulapi/thinkreservations. Read rooms, rates, inventory, reservations and price quotes in ThinkReservations. This page covers its hosted endpoint (https://thinkreservations.usefulapi.io/mcp).

Is the ThinkReservations MCP by usefulapi server safe to use?

ThinkReservations MCP by usefulapi 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 ThinkReservations MCP by usefulapi server expose?

ThinkReservations MCP by usefulapi exposes 11 tools: thinkreservations_get_hotel, thinkreservations_list_rooms, thinkreservations_list_room_types, thinkreservations_list_rate_types, thinkreservations_get_rate_type, and 6 more. Their descriptions and schemas cost roughly 806 tokens of context every time the server is loaded.

Does the ThinkReservations MCP by usefulapi server require authentication?

Its publisher declares no required credentials for ThinkReservations MCP by usefulapi. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.

Is the ThinkReservations MCP by usefulapi server still maintained?

ThinkReservations MCP by usefulapi 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.

What did VerifyMCP test on the ThinkReservations MCP by usefulapi server?

VerifyMCP ran 4 checks on ThinkReservations MCP by usefulapi, covering TLS certificate, HSTS header, DNSSEC and Transport. 7 items could not be completed, a gap on our side rather than a finding about ThinkReservations MCP by usefulapi: Authorization, HTTPS, Schema quality, Stability and 3 more. 5 categories score 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.