SolGuard Solana Token-2022 Scanner & Safe-Swap Router

The audit tool is clearly separate (read-only forensics vs. transaction building), but build_jito_safe_exit and build_jito_safe_swap overlap significantly: the swap tool explicitly supports side='sell' Token->SOL 'post-unwrap Safe-Exit', which is essentially the same operation as safe_exit. The descriptions do distinguish them (exit is the emergency path where the fee is paid from sale proceeds with near-zero free SOL), but an agent must read carefully to know when to pick the dedicated exit tool versus the sell side of the swap.

The two transaction-building tools share a clean, predictable build_jito_safe_* prefix, and the third uses a coherent verb_noun form (solana_token_forensic_audit). The audit tool deviates from the build_* prefix, but that reflects a genuinely different operation class (read-only vs. build), so the deviation is minor and readable rather than chaotic.

Three tools is on the low end, but for a narrow 'scanner + safe-swap router' domain each tool maps to a distinct phase: verify, trade, emergency exit. Nothing feels redundant in count terms, though the small surface means every ambiguity (exit vs. sell-side swap) is more costly.

The core lifecycle is covered (audit a token, build buy/sell, build emergency exit), all as unsigned transactions per the stated design. However, there is no standalone quote/preview tool (agents must build a transaction to inspect routes), no fee/partner-referral reporting or claim path, and no transaction status or submission helper — notable gaps for a router-style server.