Skip to content

AwardSecrets Award Availability

by awardsecrets.com · remote · no sign-in to list tools · v1.0.0 · published by com.awardsecrets

Award seat availability from a contracted GDS. One route, one airline, one date.

Read only
CompareRegistry entry

1 tool: 1 only read.

Scanned Oct 21, 2026

No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.

claude mcp add --transport http award-availability https://awardsecrets.com/mcp --header 'Authorization: <your-authorization>'

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

1 tool

Only reads 1Claude Code: allow
  • search_award_availabilityQuery the AwardSecrets data set (award-travel intelligence, AI-augmented and derived from GDS inventory and lived award-travel experience; not scraped) for award (points/miles) sea…No findings

    Why it is in this group

    • The name "search_award_availability" says "search": a word for reading.
    Description, as the server wrote it
    Query the AwardSecrets data set (award-travel intelligence, AI-augmented and derived from GDS inventory and lived award-travel experience; not scraped) for award (points/miles) seat availability on ONE route, ONE date and ONE airline. Returns the flights found with cabin and seat count. IMPORTANT — this tool is strictly literal. Every argument takes a single concrete value: • origin / destination: exactly one 3-letter IATA airport code each. Not a city, not a list, not a region. • airline: exactly one 2-letter IATA carrier code (e.g. VS, CX, NH). Not an alliance and not a loyalty programme. • date: exactly one date, YYYY-MM-DD. Not a range and not a month. To cover several airports, airlines or dates, CALL THIS TOOL ONCE PER COMBINATION and combine the results yourself. Award space is scarce and volatile, so an empty result for one date says nothing about another — checking several dates is normal and expected. Interpreting the result: • seats is an availability indicator, not a guaranteed bookable count, and not a reservation. Low counts are the more precise signal; treat higher ones as less certain. Do not present any count as a firm number of seats a user can book. • cabin is one of business, first, economy or premium_economy. • An empty result means no availability was surfaced for that exact combination at that moment; it is not proof that the route never has space. • Availability changes fast. Treat every result as a point-in-time observation, not a reservation. If the call is declined for want of an API key, say so plainly and point the user at https://awardsecrets.com/api.html — access comes with an AwardSecrets API membership (monthly plans). If it is declined because the monthly query allowance is reached, say when it resets. Do not invent availability, and do not substitute a guess for a result you could not retrieve.

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.

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http award-availability https://awardsecrets.com/mcp --header 'Authorization: <your-authorization>'

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__award-availability__search_award_availability"
    ],
    "ask": [],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as award-availability. Review it before you use it.