An agent can connect on its own if it already holds AWARD_AVAILABILITY_TOKEN.Remote endpoint behind a static API key or header. The registry never sees the value; the agent fills the placeholder.
tools.description_length1 tools have descriptions over 1,024 characters, which crowds the context
pass
tools.schemasevery tool has an object input schema
fail
tools.annotationsno tool declares readOnlyHint or destructiveHint, so clients cannot tell safe calls from risky ones
fail
tools.directory_hintsno tool declares all four of readOnlyHint, destructiveHint, idempotentHint and openWorldHint; missing: search_award_availability (readOnlyHint, destructiveHint, idempotentHint, openWorldHint)
pass
tools.token_costabout 696 tokens to load every tool
pass
tools.api_dumptools are not a one-to-one API dump
stability100 · weight 15
pass
stability.changes1 tool changes in 30 days
pass
stability.rug_pullno tool changed its meaning under the same name
dependenciesn/a · weight 15
n/a
deps.known_vulns, deps.mcp_sdk_version, deps.resolvableno npm or PyPI package
1 tools, about 696 tokens to load them all · tool set b00f7b9c590a · tools last changed 2026-10-09 · checked 2026-10-20 09:31 UTC
Tool changes
search_award_availabilitychangeddescription
before
Look up award (points/miles) seat availability for ONE specific flight route on ONE specific date with ONE specific airline, sourced from a contracted GDS rather than scraped. 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 is in limited release and keys are issued individually. Do not invent availability, and do not substitute a guess for a result you could not retrieve.
after · 83% of words in common
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.
Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed. How it is computed.
Endpoints
remote
auth
reachable
uptime 30d
p50
protocol
last ok
https://awardsecrets.com/mcpstreamable-http
api_key ${AWARD_AVAILABILITY_TOKEN}
yes
100%
513 ms
2025-06-18
2026-10-20
Tools (1)
search_award_availability
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.