dev.rendraputra/100pro-token-risk
REMOTE · X402.RENDRAPUTRA.DEV
Read-only risk tools: token screen, contract source, wallet. $0.10 USDC on Base.
Available components
Last scanned (18 hours ago)
Scores higher than 71% of remote servers
Reachable. Last reached 16 Oct 2026.
Category Crypto and Web3
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. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 402, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability65
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management77
- Stability observed for 23 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 16 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 63. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 53. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 6 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 43. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 16 Oct 2026 · Probed https://x402.rendraputra.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=rendraputra.dev | CN=WE1,O=Google Trust Services,C=US | 10 Oct 2026 | 8 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | f4c7b865c2e759e813e7851ef209feef |
| SANs: rendraputra.dev, *.rendraputra.dev | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of x402.rendraputra.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| rendraputra.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://x402.rendraputra.dev/mcp | Verified | 200 | |
| http (plaintext) | http://x402.rendraputra.dev/mcp | Inconclusive | 402 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
contract_source_check Contract source check (EVM, read-only) ~253
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.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | EVM address (0x + 40 hex chars). Batch up to 5 addresses, comma-separated. Required. |
| chain | string | – | Optional. Defaults to Base when omitted. |
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | yes | Chain used, or `auto` when inferred |
| kind | string | yes | Which tool produced this result |
| results | array | yes | One entry per requested address, in request order |
No examples provided.
token_risk_screen Token risk screen (EVM + Solana, read-only) ~273
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | EVM address (0x + 40 hex chars) or Solana SPL mint (base58). Batch up to 5 addresses, comma-separated. Required. |
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | yes | Chain used, or `auto` when inferred |
| kind | string | yes | Which tool produced this result |
| results | array | yes | One entry per requested address, in request order |
No examples provided.
wallet_risk_screen Wallet risk screen (EVM, read-only) ~238
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.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | EVM address (0x + 40 hex chars). Batch up to 5 addresses, comma-separated. Required. |
| chain | string | – | Optional. Defaults to Base when omitted. |
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | yes | Chain used, or `auto` when inferred |
| kind | string | yes | Which tool produced this result |
| results | array | yes | One entry per requested address, in request order |
No examples provided.
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.
remote · x402.rendraputra.dev
claude mcp add --transport http dev-rendraputra-100pro-token-risk 'https://x402.rendraputra.dev/mcp'
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 76 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 16 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.