MCP header authentication fixed, nine more tools documented

A client that sent its API key in the x-salience-api-key header could connect and list tools, but every tool call failed with "Invalid or revoked API key". The server was adding the header a second time, and the two values were merged. Fixed in MCP server 1.19.1; ?apiKey= and x-loglens-api-key were unaffected.

Also in this release:

• The MCP tools table in the help page now covers all 81 tools, including get_bot_access, get_url_detail, the Search Console and Google Analytics tools, create_website, start_trial, start_checkout, get_billing_status, get_outcomes, get_ai_landing_pages, get_crawl_links, search_urls and the site-context tools.
• The API docs show website IDs as the UUIDs they are, include org_id and feed_scope in the websites example, list POST /reports/seo with the other write endpoints, note that X-API-Key is accepted as well as Authorization: Bearer, and say that the AI funnel endpoint returns data_buffering: true while its queries are still running.
• API-key and MCP calls to api.salience.com now receive ingest.salience.com in setup responses, not the Salience mirror.
• Paid plans report trial_period_days: 14 on the billing endpoint, matching the trial you get.
• The help page and the September changelog name the previous MCP addresses correctly again.