# dev.rendraputra/100pro-token-risk (remote · x402.rendraputra.dev)

Read-only risk tools: token screen, contract source, wallet. $0.10 USDC on Base.

- Trust score: 67/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-28

## Components

- remote · `x402.rendraputra.dev`: 67/100 (this document), [markdown](https://verifymcp.io/servers/dev-rendraputra-100pro-token-risk/x402.md), [page](https://verifymcp.io/servers/dev-rendraputra-100pro-token-risk/x402)

## Channel facts

- Endpoint: `https://x402.rendraputra.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.4`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-28.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 402, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 65/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 857 tokens (~285/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 17/100
  - Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the dev.rendraputra/100pro-token-risk MCP server?

dev.rendraputra/100pro-token-risk is a hosted endpoint at https://x402.rendraputra.dev/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http dev-rendraputra-100pro-token-risk 'https://x402.rendraputra.dev/mcp'
```

### Cursor

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

### VS Code

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

### Codex

```toml
[mcp_servers.dev-rendraputra-100pro-token-risk]
url = "https://x402.rendraputra.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dev-rendraputra-100pro-token-risk": {
      "type": "remote",
      "url": "https://x402.rendraputra.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add dev-rendraputra-100pro-token-risk --url 'https://x402.rendraputra.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  dev-rendraputra-100pro-token-risk:
    url: "https://x402.rendraputra.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "dev-rendraputra-100pro-token-risk": {
      "Transport": "http",
      "Url": "https://x402.rendraputra.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add dev-rendraputra-100pro-token-risk -t streamable-http -u 'https://x402.rendraputra.dev/mcp'
```

### Other

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

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-28 (score 67, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-27 (score 67, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-25 (score 66, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-24 (score 65, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-09-23 (score 65)

First indexed and scored.

## MCP tools (3)

### `token_risk_screen` (~273 tokens)

Token risk screen (EVM + Solana, read-only)

Pre-trade risk screen for an EVM token contract or a Solana SPL mint (Base, Ethereum, BSC, Polygon, Arbitrum, Solana). Returns a markdown report: honeypot/tax/owner flags, LP-lock state, mint and freeze authority, transfer fee/hook, holder concentration, liquidity depth, wash-trade flags, and a final **Verdict** line. Up to 5 comma-separated tokens per call. $0.1 USDC for a single token contract / SPL mint, $0.25 for a 2-5 address batch, on Base (x402 v2, no account, no API key). An unpaid call answers HTTP 402 with the payment challenge; sign it and retry with the payment in the call `_meta`. Read-only: it never signs, transfers, or approves anything on the caller's behalf.

Input parameters:

- `chain` (string): Optional. Omit it and the chain is inferred from the address shape (0x… → Base by default, base58 → Solana). Set it explicitly when the same address shape is ambiguous.
- `token` (string, required): EVM address (0x + 40 hex chars) or Solana SPL mint (base58). Batch up to 5 addresses, comma-separated. Required.

Output parameters:

- `chain` (string): Chain used, or `auto` when inferred
- `kind` (string): Which tool produced this result
- `results` (array): One entry per requested address, in request order

### `contract_source_check` (~253 tokens)

Contract source check (EVM, read-only)

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. Returns markdown ending in a **Verdict** line. Up to 5 comma-separated addresses per call. $0.1 USDC for a single contract address, $0.25 for a 2-5 address batch, on Base (x402 v2, no account, no API key). An unpaid call answers HTTP 402 with the payment challenge; sign it and retry with the payment in the call `_meta`. Read-only: it never signs, transfers, or approves anything on the caller's behalf.

Input parameters:

- `address` (string, required): EVM address (0x + 40 hex chars). Batch up to 5 addresses, comma-separated. Required.
- `chain` (string): Optional. Defaults to Base when omitted.

Output parameters:

- `chain` (string): Chain used, or `auto` when inferred
- `kind` (string): Which tool produced this result
- `results` (array): One entry per requested address, in request order

### `wallet_risk_screen` (~238 tokens)

Wallet risk screen (EVM, read-only)

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). Returns markdown with a **Verdict** and a flag list. Up to 5 comma-separated addresses per call. $0.1 USDC for a single wallet address, $0.25 for a 2-5 address batch, on Base (x402 v2, no account, no API key). An unpaid call answers HTTP 402 with the payment challenge; sign it and retry with the payment in the call `_meta`. Read-only: it never signs, transfers, or approves anything on the caller's behalf.

Input parameters:

- `address` (string, required): EVM address (0x + 40 hex chars). Batch up to 5 addresses, comma-separated. Required.
- `chain` (string): Optional. Defaults to Base when omitted.

Output parameters:

- `chain` (string): Chain used, or `auto` when inferred
- `kind` (string): Which tool produced this result
- `results` (array): One entry per requested address, in request order

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/dev-rendraputra-100pro-token-risk/x402#diagnostics

## Score history

- 2026-09-28: 67
- 2026-09-27: 67
- 2026-09-26: 66
- 2026-09-25: 66
- 2026-09-24: 65
- 2026-09-23: 65

## Common questions

### What is the dev.rendraputra/100pro-token-risk MCP server?

dev.rendraputra/100pro-token-risk is an MCP server listed in the public MCP registry as dev.rendraputra/100pro-token-risk. Read-only risk tools: token screen, contract source, wallet. $0.10 USDC on Base. This page covers its hosted endpoint (https://x402.rendraputra.dev/mcp).

### Is the dev.rendraputra/100pro-token-risk MCP server safe to use?

dev.rendraputra/100pro-token-risk scores 67 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the dev.rendraputra/100pro-token-risk MCP server expose?

dev.rendraputra/100pro-token-risk exposes 3 tools: token_risk_screen, contract_source_check, wallet_risk_screen. Their descriptions and schemas cost roughly 764 tokens of context every time the server is loaded.

### Does the dev.rendraputra/100pro-token-risk MCP server require authentication?

No. We connected to dev.rendraputra/100pro-token-risk without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the dev.rendraputra/100pro-token-risk MCP server still maintained?

dev.rendraputra/100pro-token-risk is still listed as active in the MCP registry. We last reached this channel on 28 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://x402.rendraputra.dev/mcp
- Repository: https://github.com/rndrpp/100pro-mcp
- Website: https://x402.rendraputra.dev/
- Changelog RSS feed: https://verifymcp.io/servers/dev-rendraputra-100pro-token-risk/x402.xml
- Changelog JSON feed: https://verifymcp.io/servers/dev-rendraputra-100pro-token-risk/x402.json
- HTML version of this page: https://verifymcp.io/servers/dev-rendraputra-100pro-token-risk/x402