v0.6.0

What's changed in v0.6.0

npm: npm install ctscout-mcp-server@0.6.0 or npx ctscout-mcp-server@0.6.0

Added

• Every tool description ends with a "Corrections" line, and every API 4xx
  about the answer (400, 404, an unmapped status) ends with the same
  sentence: a wrong attribution is an issue on the package's tracker, a
  missing entity an email to pro@ctscout.dev, with the query, the result and
  why it is wrong. The path itself is unchanged (LIMITATIONS "Corrections and
  contact"); it is now in-band, where an agent that got a wrong answer reads.
  Key and quota refusals (401, 403, 429), 5xx and timeouts do not carry it:
  they already say what to do (#102).

• ctscout_lookup_lei by name: the API's normalizer_mismatch (null, or the
  { index, lookup } normalizer versions when the index was keyed by one this
  API does not reproduce) is now in the output schema, rendered as one line
  above the markdown result — so a none under a drifted index reads as a
  possible spelling miss, not a true miss — and kept by the overflow envelope.
  The JSON path already passed it through.

Changed

• ctscout_search_company: the org_match_field description now states what
  normalized compares since the API moved it to the research normalizer
  (X-API-Version: 2026-09-07): the normalizer's key of the query against the
  normalized column, with legal forms stripped at the edges, &/and and
  hyphen/space unified, a leading "The" dropped and a generic tail such as
  "Holdings" kept. It used to promise the locale normalizer.

• Pro is described as it is sold: 3,000 /scan lookups a month for $49,
  subscribed through Stripe from https://ctscout.dev/#tiers, with the key
  sent by email. The "unlimited" and "concierge-only" wording is gone from
  the README, LIMITATIONS, the tool descriptions, the 429 and 403 texts and
  the batch quota footer (which now says the count is not reported for the key when
  the API sends remaining_quota: null). A /scan 429 quotes the API's own
  detail — which cap, and when it resets — instead of assuming the free
  daily quota, since a Pro key meets one too. The README tiers table mirrors
  the product page row for row and the Pro example table is the renderer's
  verbatim output; tests/docs-claims.test.ts pins those and the transport
  parity exception, the confirmed-vendor definition's two paths, the caps and
  quotas, the npm scripts and the handshake example to the code (#116).