About 100pro-token-risk
100pro-token-risk is a read-only MCP server for pre-trade screening of EVM token contracts and Solana SPL mints. It combines contract, liquidity, and holder signals into a one-line verdict.
Key features
- 01Screens for honeypot, tax, and owner flags
- 02Checks LP locks and authority status
- 03Analyzes holder concentration and liquidity
- 04Detects wash-trade signals
- 05Returns a one-line risk verdict
Use cases
- 01Screen EVM token contracts before a trade
- 02Check Solana SPL mint authorities and risks
- 03Compare risk signals across multiple tokens
MCP support
The remote MCP server exposes the read-only `token_risk_screen` tool for up to five addresses per call. Calls use x402 v2 USDC payments on Base; the repository also includes a stdio bridge that forwards requests to the remote endpoint.
Configuration
Remote servers need no local install. Pick your client, then copy the config or install in one click.
https://x402.rendraputra.dev/mcpclaude mcp add --transport http dev-rendraputra-100pro-token-risk https://x402.rendraputra.dev/mcp{"mcpServers":{"dev-rendraputra-100pro-token-risk":{"type":"http","url":"https://x402.rendraputra.dev/mcp"}}}Open in Cursor{"servers":{"dev-rendraputra-100pro-token-risk":{"type":"http","url":"https://x402.rendraputra.dev/mcp"}}}Open in VS Code{"mcpServers":{"dev-rendraputra-100pro-token-risk":{"type":"http","url":"https://x402.rendraputra.dev/mcp"}}}{"mcpServers":{"dev-rendraputra-100pro-token-risk":{"serverUrl":"https://x402.rendraputra.dev/mcp"}}}Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.
Tools
Details
From the project README100pro Token Risk Screen — MCP server
Pre-trade risk screening for EVM token contracts and Solana SPL mints, exposed as a remote MCP tool. Honeypot/tax/owner flags, LP-lock state, mint & freeze authority, transfer fee/hook, holder concentration, liquidity depth, wash-trade signals — ending in a one-line Verdict.
- Endpoint:
https://x402.rendraputra.dev/mcp(MCP streamable HTTP, JSON-RPC 2.0) - Tool:
token_risk_screen(token,chain) — read-only, up to 5 comma-separated addresses per call - Chains:
base,ethereum,bsc,polygon,arbitrum,solana - Price: $0.10 USDC per single token, $0.25 for a 2-5 token batch, on Base, paid with
x402 v2 — no account,
no API key, no subscription. An unpaid call answers HTTP 402 with the payment challenge; pay it and
retry. Free metadata:
/llms.txt,/openapi.json,/.well-known/x402.
Use it as a remote MCP server (no install)
{
"mcpServers": {
"100pro-token-risk": {
"type": "http",
"url": "https://x402.rendraputra.dev/mcp"
}
}
}
Use it through this stdio bridge
Some clients only speak stdio. This tiny proxy forwards initialize, tools/list and tools/call
to the remote endpoint (stdlib only, no dependencies):
{
"mcpServers": {
"100pro-token-risk": {
"command": "python3",
"args": ["/absolute/path/to/100pro_mcp.py"]
}
}
}
or straight from the repo, if you use uv:
{
"mcpServers": {
"100pro-token-risk": {
"command": "uvx",
"args": ["--from", "git+https://github.com/rndrpp/100pro-mcp", "100pro-mcp"]
}
}
}
What a call returns
A markdown report per token, e.g.:
## 0x8335…2913 (base)
**Verdict: PASS — no blocking risk signal found.**
...
If the call is unpaid the server answers with the x402 payment challenge (HTTP 402). Pay $0.10 USDC
(single token) or $0.25 (2-5 token batch) on
Base to the payTo in the challenge and retry; the response carries a PAYMENT-RESPONSE receipt
naming the settled transaction.
Why paying beats a free scanner
Free scanners are the product being sold elsewhere: rate-limited, delay-baiting, or an upsell funnel. This one is a single priced call with a fail-closed guarantee — the report is generated and returned only after the USDC transfer is confirmed on Base, and every settle attempt is logged with the on-chain verdict.
Links
- Discovery: https://x402.rendraputra.dev/llms.txt
- OpenAPI: https://x402.rendraputra.dev/openapi.json
- x402 protocol: https://www.x402.org
MIT licensed.
Repo layout
100pro_mcp.py— repo-root entry point (python3 100pro_mcp.py, and the file container checkers execute after cloning); it bootstrapspro100/bridge.py.pro100/bridge.py— the actual stdio bridge: answersinitialize/tools/listlocally (so introspection needs no network) and forwardstools/callto the hosted endpoint.pyproject.toml— packagespro100, console script100pro-mcp(souvx --from git+https://github.com/rndrpp/100pro-mcp 100pro-mcpworks).
Python 3.9+, standard library only — nothing to install for the plain-script path.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.