Home / MCP registry index / io.github.bnth09productions-maker/scrapling-x402-store
Scrapling x402 Data Store
io.github.bnth09productions-maker/scrapling-x402-store in the official MCP registry.
Endpoint https://scraplingdata.xyz/mcp.
The registry describes it as: Crypto/DeFi, stock and e-commerce datasets plus pay-per-call web scraping, paid with x402 USDC.
We read its 25 tools on 2026-10-22. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
list_datasets preview_dataset scrape_url buy_dataset free_feeds free_crypto_top10 free_defi_top_yields lookup_coin lookup_protocol lookup_yields lookup_pool lookup_polymarket lookup_token_risk free_datasets get_dataset market_pulse price_moves defi_intel ad_cost_benchmarks ping whale_moves whale_netflow whale_token token_verdict scrape_text
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-github-bnth09productions-maker-scrapling-x402-store)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.