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 12,342 of 40,590 scannable entries (30%) — 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-validatorMCPattestedtrust 85/100 · A

   v2.3.0

   ↓ 158/wk

   Mathematical constraint validator for design systems — ensuring consistency, accessibility, and logical coherence

   ClaudeCursorCopilotGemini

   Cseperke PappMIT4mo agonpmGitHub+compareobserved 2026-06-14 · static extraction

   design-constraintsdesign-systemsconstraint-validationdesign-tokensaccessibilitywcag
2. @memharness/mcpMCPcommunitytrust 60/100 · B

   v0.1.2

   Bi-temporal, provenance-carrying long-term memory for AI agents, in one SQLite file.

   ClaudeCursorCopilotGemini

   io.github.las7Unknown3mo agonpmGitHub+compareobserved 2026-08-10 · static extraction

   mcp
3. io.github.Antmanbuilds/ari-mcpMCPcommunitytrust 60/100 · B

   v0.1.3

   Fair-price checks, leaderboards, and Ed25519 receipt verification for x402/MPP services.

   ClaudeCursorCopilotGemini

   io.github.AntmanbuildsUnknown4mo agonpmGitHub+compareobserved 2026-06-13 · static extraction

   mcp

All indexed toolsSearch the registry for why