A

awardtravelfinder.com

Award Travel Finder is a travel search service focused on finding award-flight availability and related loyalty-program data using points and miles. It offers tools for AI agents and developers to search award seats, compare redemptions, and work with airline and hotel program information.

4 integrations · MCP · REST

awardtravelfinder.com exposes a REST API at `https://awardtravelfinder.com/api/v1` authenticated by `X-API-Key`, plus MCP endpoints at `https://mcp.awardtravelfinder.com/mcp` and a root-host variant `https://awardtravelfinder.com/mcp`; docs and metadata describe OAuth 2.1 for the subdomain MCP endpoint, while a seed probe reported both MCP endpoints as public/no-auth.

discovered 27d ago
MCP servers2
REST · OpenAPI2
Credentials
Award Travel Finder API keyapi_keyGet key ↗

For the easiest self-service path, POST to `https://awardtravelfinder.com/api/v1/agent/register` with an optional operator_email and agent_name; the 201 response returns an api_key once, so store it securely. A browser-based alternative is to sign in and use the API Key page to generate or rotate a key.

Award Travel Finder OAuth access for MCPoauth2Set up OAuth ↗

For MCP clients, the server supports self-onboarding OAuth: the client can dynamically register itself at `POST https://awardtravelfinder.com/oauth/register`, then send the user through the standard authorization flow at `/oauth/authorize` and `/oauth/token` with PKCE S256, requesting scope mcp:read. In practice, MCP clients such as Claude Desktop or Cursor should prompt for sign-in automatically; the user just approves access in the browser.

Award Travel Finder API Keyapi_keyGet key ↗

Sign up for a free account at awardtravelfinder.com, then visit the API Key page to generate your key. The key is shown only once, so store it securely. Free tier includes 50 API calls/month; paid plans offer higher limits.

OAuth 2.1 for MCP Accessoauth2

Connect via OAuth 2.1 flow. MCP clients (Claude Desktop, Cursor) will automatically prompt for sign-in and handle the authorization. The MCP endpoint requires the mcp:read scope. See MCP setup docs for client configuration.

conventions · 8/8 published

Publish these signals → /publishing