Add Ignav hosted MCP server

[gusgordon]

Adds Ignav's hosted MCP endpoint to the toolkit MCP configs for Claude Code, Codex plugin installs, and OpenCode.

I'm Gus, the Ignav founder. The toolkit already has an Ignav REST skill, and this adds the hosted MCP server so agents can call live flight prices and booking links directly with no setup.

Checks:

• jq validation for touched JSON files
• bash scripts/gen-skill-tables.sh --check
• bash scripts/smoke-test.sh --quick started cleanly and passed the first six static checks, but hung without output after that, so I stopped it and ran the focused checks above

[borski]

Hey @gusgordon! thanks for this, and for the gusgordon/ignav-skill repo, which is a helpful reference. Before merging I want to get the "no setup" framing right, because I tested the hosted endpoint and it doesn't match what you wrote in the PR

Unauthenticated tool calls return a hard HTTP 401 / api_key_required (no rate-limit headers), so the "anonymous testing, rate-limited" tier in your llms-install.md didn't return data for me. And per your own README it's 1,000 free requests then $2/1k, i.e. a freemium paid API. So listing Ignav among the toolkit's zero-key servers (Skiplagged, Kiwi, Trivago, Ferryhopper, Airbnb) in the README/CLAUDE.md isn't accurate; those need no account at all.

I want to represent the MCP fairly, so two questions:

1. Your error mentions OAuth for cloud clients: in Claude Code specifically, does adding the server trigger a browser OAuth flow that then works (account required, but no key to paste)? If so I'll document it that way. For the Codex/OpenCode installs you mention, it still needs X-Api-Key, right?
2. Is the anonymous tier meant to be live? It returned 401 for me across several clean attempts.

Given the existing REST skill already covers Ignav with the same account/key, I'm trying to figure out why or where the MCP is the better path (my guess: the Claude Code OAuth convenience). Is that accurate? It doesn't seem it provides any data the REST API doesn't, and so limiting the skill to the REST API seems better at first glance.

Unrelated but useful: the smoke-test hang you hit (no output after ~six checks) is a stock-macOS bug; the script called bare timeout, which macOS doesn't ship. Fixed on main now (#25), so a fresh pull runs clean.