wDOOM, 0x623c84A5E04bF715018203334b0eFE41696eBC3E) settlement history.SAFE_WITH_ESCROW, SAFE_NO_ESCROW, or QUARANTINE (fake/unpaid honeypots).This skill bundles no verifier implementation. Do not download bounty.py to a predictable /tmp path and execute it. Retrieve a pinned source revision through the approved source workflow, read the complete verifier and dependencies as inert files, verify origin/integrity and only then run an authorized read-only check in an isolated environment. Use a new private working directory and bounded network access. A checksum supplied beside a mutable download is not independent trust evidence.
For a reviewed checkout, the documented commands are python3 integrations/mcp/doomsday_mcp.py audit and python3 integrations/mcp/doomsday_mcp.py verify owner/repo#number; those paths are in the upstream repository, not this installed skill.
integrations/mcp/doomsday_mcp.py also runs as a read-only JSON-RPC 2.0 stdio MCP server exposing list_escrows, verify_issue_escrow, audit_doomsday_escrows, and get_pool_leaderboard:
{
"mcpServers": {
"doomsday-escrow": {
"command": "python3",
"args": ["/absolute/path/to/reviewed-checkout/integrations/mcp/doomsday_mcp.py", "--mcp"]
}
}
}
SAFE_WITH_ESCROW is the verifier's classification, not a guarantee that a bounty is safe or payable. Report concrete evidence and unknowns, not a binary financial endorsement. Escrow presence alone does not establish spend conditions, claimant entitlement, asset value, issuer solvency or future payment.list_escrows, verify_issue_escrow, audit_doomsday_escrows) is strictly read-only and uses Python's standard library (urllib.request and json) with zero third-party dependencies.github.com egress, doomsday_mcp.py and bounty.py automatically fall back to the GitHub-hosted public snapshot mirror (data/escrows_public_snapshot.json).