upgrade_impact

2 registry entries were observed exposing a tool named upgrade_impact — 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,892 of 43,724 scannable entries (29%) — 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. @vibgrate/cliMCPcommunitytrust 60/100 · B
    v2026.1014.1
    ↓ 1k/wk
    ★ 5

    Vibgrate CLI scans your manifests — never your source — and scores drift (DriftScore) and exposure (RiskScore) separately. Free, offline, in about a minute.

    ClaudeCursorCopilotGemini
    VibgrateApache-2.02d agonpmGitHubobserved · static extraction
    code-graphcodebase-intelligenceasttree-sittermcpai-agents
  2. cloud.coredls.vigia/vigiaMCPcommunitylivetrust 60/100 · B
    v0.6.0
    ★ 1

    What breaks between versions, vulnerabilities, compatible versions, EOL dates: npm, PyPI, Rust, PHP.

    ClaudeCursorCopilotChatGPTGemini
    cloud.coredls.vigiaUnknown7d agoGitHubobserved · static extraction
    mcp

All indexed toolsSearch the registry for upgrade_impact