get_anchor_status

2 registry entries were observed exposing a tool named get_anchor_status — 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,336 of 40,577 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. io.github.smq9sn5jck-cloud/causallayer-mcpMCPcommunitylivetrust 60/100 · B
    v0.2.0
    ★ 2

    Deterministic AI-liability attribution: signed, Bitcoin-anchored vendor/deployer/user fault split.

    ClaudeCursorCopilotChatGPTGemini
    io.github.smq9sn5jck-cloudUnknown4mo agoGitHubobserved · static extraction
    mcp
  2. io.github.Zk-nd3r/zcash-mcpMCPcommunitytrust 60/100 · B
    v0.2.2
    ★ 1

    Zcash shielded operations for AI agents. Memo decoding, attestation, proof verification.

    ClaudeCursorCopilotGemini
    io.github.Zk-nd3rUnknown6mo agonpmGitHubobserved · static extraction
    mcp

All indexed toolsSearch the registry for get_anchor_status