Counterparty risk scoring for agentic commerce via x402 micropayments.
Counterparty risk scoring for agentic commerce. One API call answers: "Should this agent send money to this counterparty?" Revettr scores counterparties by analyzing domain intelligence, IP reputation, on-chain wallet history, and sanctions lists. It's designed for AI agents transacting via x402 on Base. Send any combination of inputs. More data = higher confidence. Input | Signal Group | What It…
Inferred from the transports this listing declares (stdio, streamable-http). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Forge read 0 source files from the published package tarball and matched no MCP tool registrations. Extraction is pattern-based over shipped source: a server that builds its tool list at runtime, or that ships only bundled or minified code, registers nothing this can see. Treat it as “not detected”, not as “exposes none”.
Counterparty risk scoring for agentic commerce. One API call answers: "Should this agent send money to this counterparty?" Revettr scores counterparties by analyzing domain intelligence, IP reputation, on-chain wallet history, and sanctions lists. It's designed for AI agents transacting via x402 on Base. Send any combination of inputs. More data = higher confidence. Input | Signal Group | What It Checks | -------|-------------|----------------| | Domain Intelligence | WHOIS age, DNS config (MX,…
Forge's dependency resolver reads npm metadata only, so this PyPI package has no resolved tree. That is a gap in coverage, not a clean bill of health.