Production MCP

Airline expertise for your agent.

SupportNav exposes 13 stateless, read-only MCP tools for triage, cached source lookup, authorized evidence-search planning, reviewed packets, X drafts, DOT drafts, follow-up reminders, and portable case review. It does not submit requests, connect inboxes, or persist cases. US-related cancellations cover 12 listed carriers. Complete delay assessment is limited to American, Delta, United and Southwest.

Connection

https://www.supportnav.com/mcp

Streamable HTTP. No authentication for these public stateless tools. Check the deployed health payload and discovered tool schemas before relying on a newly added capability.

Inspect deployed health

Host setup

The 13 tools

  1. triage_airline_support — Separate routine airline self-service from an unresolved dispute.
  2. assess_airline_issue — Check explicit US-related cancellation refund facts.
  3. assess_flight_delay — Assess a delay path for American, Delta, United and Southwest.
  4. get_policy_sources — Return cached DOT refund and escalation references.
  5. get_support_channels — Look up a cached official contact page.
  6. prepare_evidence_search — Plan authorized connected-email searches. Does not read inboxes.
  7. prepare_complaint_packet — Draft a confirmed cancellation refund packet.
  8. prepare_delay_packet — Draft a confirmed delay request.
  9. prepare_browser_handoff — Prepare official-site browser assistance after confirmation.
  10. prepare_social_post — Draft an X post or DM. Does not post.
  11. prepare_dot_complaint — Prepare a DOT complaint after the airline was contacted.
  12. prepare_follow_up — Return dated reminder windows and an .ics file.
  13. review_case_status — Review a portable existing-case summary. Does not store it.

Workflow contract

  1. Triage the issue. Routine transactions go to the airline.
  2. Plan only authorized evidence topics. The host executes email searches and retains exact source references.
  3. Assess cancellation or delay facts. Preserve unknowns and unresolved conflicts; never substitute another workflow to bypass a blocked result.
  4. Show the fact/source summary and wait for traveler confirmation.
  5. Call the matching packet tool. Add private identifiers only at the official destination.

Discovery and registry

Clients can fetch the SEP-2127 Server Card at /server-card or /mcp/server-card, and the catalog at /.well-known/mcp/catalog.json. A static A2A v1.0 Agent Card at /.well-known/agent-card.json lists skills and points at the MCP endpoint. It is not an A2A JSON-RPC agent.

Official MCP Registry publishing uses repo-root server.json under the com.supportnav namespace. HTTP domain verification is served at /.well-known/mcp-registry-auth. Josh still has to run mcp-publisher login http --domain supportnav.com --private-key … and mcp-publisher publish with the matching private key. The private key is not in this repository.

The hosted server is already stateless. Successful tools/list responses are cacheable for five minutes. The installed MCP SDK negotiates through protocol version 2025-11-25, not 2026-07-28, so this release does not advertise an unsupported protocol date.

Website guided help uses the same assessment and packet functions. Source review dates are returned with policy references; no runtime verification is implied.

OpenAI tool metadata guidanceOfficial Codex MCP documentationSource package, golden prompts, and host review casesCoverage and limitationsPrivacy policyTerms of useSupport