Home / MCP registry index / io.github.webberdesign/webbersites-x402-data-api

io.github.webberdesign/webbersites-x402-data-api

io.github.webberdesign/webbersites-x402-data-api in the official MCP registry. Endpoint https://api.webbersites.com/mcp. Source: github.com/webberdesign/api.webbersites.com.

The registry describes it as: 45 pay-per-call AI agent tools: scraping, SEO, crypto data, lint, agent memory. x402 USDC on Base.

We read its 78 tools on 2026-10-22. Nothing in them matched our tool-poisoning rules.

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

get_price_coin get_report_coin get_orderbook get_scrape get_summarize get_website_screenshot get_timezone post_llm get_calc post_calc_stats get_calc_dates post_calc_finance get_convert get_geo get_ping get_uptime get_uptime_report get_platform post_schema_audit get_email_verify get_og_check post_og_card get_qr post_data_convert get_barcode get_seo_alt_check get_a11y_contrast get_a11y_check get_seo_robots_check get_seo_metadata get_seo_head_check get_seo_sitemap_check get_seo_nav get_seo_links get_seo_full_audit get_music_album get_music_cover get_extract get_icon_search post_icon_generate post_logo_generate post_vectorize post_website_page get_wp_assess get_dns post_schema_generate post_lint_elixir post_lint_javascript post_lint_php post_lint_liquid post_liquid_section get_seo_site_audit post_brand_kit post_website_build post_store_collection get_store_collection get_store delete_store_collection post_scratchpad_name get_scratchpad_name and 18 more

Run this server? Show the check in your README

The badge reflects the latest weekly read: MCP tool check badge

Markdown
[![MCP tool check](https://lazaretto.dev/mcp-registry/io-github-webberdesign-webbersites-x402-data-api/badge.svg)](https://lazaretto.dev/mcp-registry/io-github-webberdesign-webbersites-x402-data-api)

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.