explain_rule

2 registry entries were observed exposing a tool named explain_rule — 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 10,773 of 34,440 scannable entries (31%) — 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. @kontor-mcp/serverMCPattestedtrust 85/100 · A
    v1.0.4

    Offline e-invoice tools for AI agents: validate, audit, convert and generate XRechnung/ZUGFeRD.

    ClaudeCursorCopilotGemini
    io.github.DashankaNadeeshanDeSilvaUnknown29d agonpmGitHubobserved · static extraction
    mcp
  2. @nugehs/bouncerMCPcommunitytrust 60/100 · B
    v0.2.0
    ↓ 701/wk

    bouncer — static compliance-controls checker. Verifies the controls a regulation requires actually exist in your code (UK Online Safety Act, ICO Children's Code), as deterministic rule packs. No LLM required.

    ClaudeCursorCopilotGemini
    UnknownMIT3mo agonpmGitHubobserved · static extraction
    climcpmcp-servercomplianceonline-safety-actage-appropriate-design-code

All indexed toolsSearch the registry for explain_rule