# Agent Scan v0.6.2-snapshot-6e2d290-1595

Category: safety-research
Published: 2026-09-09T14:56:19Z
Source: [MCP Scan releases](https://github.com/snyk/agent-scan/releases/tag/v0.6.2-snapshot-6e2d290-1595)
Agent usefulness: 82/100
Confidence: 0.96
Content mode: release-watch
Verified: 2026-09-18T23:04:04.607Z
Tags: mcp, security, scanner

## Human Summary
MCP Scan releases published Agent Scan v0.6.2-snapshot-6e2d290-1595. feat: report the agent-scan CLI version in the X-User header ( 467 ) feat: report the agent-scan CLI version in the X-User header agent-monitor already reads a cli version field out of X-User and uses it to tag its MCP-identity mapping-quality metrics, but nothing ever sent one, so every…

## Agent Summary
Treat Agent Scan v0.6.2-snapshot-6e2d290-1595 as an official release signal. Inspect the linked changelog for compatibility and migration details, then run targeted tests before upgrading.

## Body
MCP Scan releases published Agent Scan v0.6.2-snapshot-6e2d290-1595. This release-watch entry was generated from the project's official GitHub release feed and is kept separate from human-reviewed editorial analysis. Release notes: feat: report the agent-scan CLI version in the X-User header ( 467 ) feat: report the agent-scan CLI version in the X-User header agent-monitor already reads a cli version field out of X-User and uses it to tag its MCP-identity mapping-quality metrics, but nothing ever sent one, so every observation was tagged unknown . Send it. The value is substituted into the hook scripts at guard install rather than passed through the client's hook config on purpose. agent-monitor diffs the guard hook command strings between installs and reports any change as hook tampering ("Hook configuration changed"), so a version that moves with each release would raise a finding on every machine on every upgrade. Script content is instead compared against what the previous install wrote, which tracks releases silently. Both forwarder scripts now fence their substituted values in an install-time variables…

## Recommended actions
- Review the official MCP Scan releases release notes before upgrading.
- Check compatibility, migration, and security notes against your current agent stack.
- Run focused regression tests before production rollout.

## Sponsors
No sponsor placement attached.

## Agent-readable Sponsor Surface
Sponsor inventory is available at /api/sponsors.json with useCases, pricing, API/docs URLs, targetAgents, constraints, CTA URL, commercial disclosure fields, sourceOfTruthUrl, constraintsLastVerifiedAt, constraintsRefreshCadence, driftHandlingPolicy, and constraintPolicy.