RMCP.DEV
← rendraputra.dev

INDIVIDUAL MCP TOOL

token_risk_screen

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

rendraputra.devnone authenticationAvailability not checked

LIVE ENDPOINT

https://x402.rendraputra.dev/mcp

No auth detected

Connect to this endpoint to inspect the live schema for token_risk_screen and invoke it with your own arguments.

Indexed input schema

{}

Risk classification

Potential side effects detected · medium confidence · heuristic, not a guarantee.

  • A tool name, description or schema mentions credentials.
  • A tool name or description suggests a financial action.

Parent server

rendraputra.dev

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.

Related tools

  • 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.
  • 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).