0.1.58 — reports say what the server answered

Reports say what the server answered, and why a scan stopped

• A dispatcher tool is named. When one tool runs other tools (for example exec(command)),
  the scan says INCOMPLETE rather than presenting that one tool as the whole server.
• Failures give the real reason. A sign-in you did not finish, a server asking you to sign in,
  and a server answering HTTP 5xx each say so.
• Signed in, but refused. When the server answers your stored sign-in with HTTP 403, mcpgawk
  says the sign-in worked and the server refuses this account, and it quotes the server's own
  reason (for example, an account with no organisation yet).
• One sign-in, every scan. After mcpgawk scan --login <url>, a plain
  mcpgawk scan --http <url> uses that sign-in.
• Writes are read from the declaration. A lone tool's annotations are honoured. A tool that
  declares destructive or idempotent hints without readOnlyHint counts as a write. A boolean
  parameter is never read as a destination.
• Server cards that list tools by name no longer produce "tools absent from its card".
• Counts, headings and footers agree. Matches found only in wording are shown but never
  counted. A failed scan gives no totals. A server is flagged as heavy only when it costs over
  5,000 tokens for what it does.
• Advice fits the server. A one-tool server is not told to disable its other tools, and a
  server that declines to close its session no longer prints an SDK error line.

pip install -U mcpgawk · uv tool upgrade mcpgawk