EVM contract risk report
● Livefutureus.win
EVM contract risk report per paid call. Input {address, chainId} -> JSON {score.band: low|medium|high|extreme, score.dispositive, findings[]}. Signals: source verification, mutable logic via EIP-1967/1822/beacon upgrade slots (implementation replaceable post-deploy), owner privileges, mint/blacklist/pause/fee powers, honeypot + sell-tax transfer paths, LP burn/lock, rug patterns, Uniswap V4 hooks. Chains: Ethereum, Base, Arbitrum, Polygon, BSC, Optimism. Read-only.
- Price
- $0.002
- Asked in its payment challenge
- Chain
- Base
- Paid in
- USDC
- Live
- 4 of 4 checks
Endpoint
$0.002 asked in its payment challenge on 18 Nov 2026
curl -i -X POST 'https://oracle.futureus.win/api/assess-token-risk' \
-H 'Content-Type: application/json' \
-d '{"address":"0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913","chainId":8453}'Agents can find it through the Superstables MCP server and JSON API: GET /api/v1/services/oracle.futureus.win
Recent checks
- Median response
- 34 ms
- Last checked
- 18 Nov, 15:20 UTC
Our probes look for a payment challenge. They don't test payment or delivery.
All 4 checks
| When (UTC) | Result | HTTP | Response |
|---|---|---|---|
| 18 Nov, 15:20 UTC | Live | 402 | 43ms |
| 17 Nov, 03:21 UTC | Live | 402 | 43ms |
| 15 Nov, 15:21 UTC | Live | 402 | 24ms |
| 14 Nov, 00:27 UTC | Live | 402 | 23ms |
Questions
Did our last probe detect a payment challenge?
At our last probe on 18 Nov, 15:20 UTC, it returned HTTP 402 or another detected payment-challenge signal.
What payment terms does EVM Contract Risk Oracle advertise?
The listing advertises x402, Base and USDC. It names cdp as its facilitator. Check the seller's current payment challenge and authentication requirements before paying.
Something wrong on this page? Tell us.