why

3 registry entries were observed exposing a tool named why — none of them flagged as a privileged capability.

Every row is point-in-time scan output, dated below. Forge has an observed tool surface for 8,470 of 26,658 scannable entries (32%) — an entry that has not been scanned cannot appear here, so absence from this list is not evidence that an entry does not expose this tool.

1. design-constraint-validatorverified
   trust 85/100 · AMCP serverobserved 2026-06-14 · static extraction
   Mathematical constraint validator for design systems — ensuring consistency, accessibility, and logical coherence
2. @memharness/mcp
   trust 60/100 · BMCP serverobserved 2026-08-10 · static extraction
   Bi-temporal, provenance-carrying long-term memory for AI agents, in one SQLite file.
3. io.github.Antmanbuilds/ari-mcp
   trust 60/100 · BMCP serverobserved 2026-06-13 · static extraction
   Fair-price checks, leaderboards, and Ed25519 receipt verification for x402/MPP services.

All indexed toolsSearch the registry for why