Security & Testing

rendraputra.dev

Performs pre-trade and due-diligence risk screening for EVM and Solana tokens, contracts, and wallets, including verification, proxy, and security-flag checks.

1 endpoint3 known toolsFirst detected September 23, 2026Last detected September 23, 2026

ENDPOINT 1

https://x402.rendraputra.dev/mcp

No auth detected

MCP server metadata

Name: 100pro-token-risk-screen
Version: 2.0.0

Capabilities

tools

Server instructions

Three paid read-only tools — token_risk_screen, contract_source_check, wallet_risk_screen. $0.1 USDC per single address, $0.25 per 2-5 address batch, on eip155:8453 via x402 v2. An unpaid tools/call returns HTTP 402 carrying the payment challenge; sign it and retry with the payment under params._meta ('x402/payment' or 'payment').

Known tools 3

token_risk_screen

Pre-trade risk screen for an EVM token contract or a Solana SPL mint (Base, Ethereum, BSC, Polygon, Arbitrum, Solana).

Potential side effects

contract_source_check

Contract-level due diligence for an EVM contract address: whether the source is verified and through which route (sourcify / verifier-alliance / eth-bytecode-db), fully vs partially verified, whether the deployed bytecode still matches the verified source, proxy pattern and implementation address, deployer address and creation tx, contract age, and a capability scan of the verified source (and of the proxy implementation) for mint, pause, blacklist, selfdestruct and delegatecall.

Inferred read-only

wallet_risk_screen

Wallet-level due diligence for an EVM address: externally-owned account vs contract (and proxy type), age from its first transaction, activity counters, native balance, funding source, how many contracts it has deployed, Blockscout scam/reputation/tags, and GoPlus address-security flags (sanctioned, phishing, mixer, money laundering, honeypot-related, malicious contracts created).

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.100pro-token-risk-screen]
url = "https://x402.rendraputra.dev/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "100pro-token-risk-screen": {
      "type": "http",
      "url": "https://x402.rendraputra.dev/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: 100pro-token-risk-screen
Remote MCP URL: https://x402.rendraputra.dev/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "100pro-token-risk-screen": {
      "url": "https://x402.rendraputra.dev/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "100pro-token-risk-screen": {
      "type": "http",
      "url": "https://x402.rendraputra.dev/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "100pro-token-risk-screen",
  "transport": "streamable-http",
  "url": "https://x402.rendraputra.dev/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.