x402-weblens-mcp
Related Servers
Alternatives to x402-weblens-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenancePay-per-use clean web reader for AI agents. URL in, markdown plus metadata out, in milliseconds. Settled per-call in USDC over x402 — no signup, no API keys.1102 npm3MIT
- AlicenseAqualityCmaintenancePay-per-call web page extraction, on-page SEO audits and text analysis for AI agents. Paid in USDC on Base via x402; no API keys, failed calls are not charged.4MIT
- AlicenseNot gradedqualityCmaintenanceEnables agents to convert any URL into clean, structured, agent-optimized content with a single paid call, paying $0.02 USDC per successful extraction via x402 on Base without API keys or accounts.MIT
- AlicenseAqualityCmaintenanceEnables AI agents to fetch any public web page as clean Markdown, retrieve page metadata (title, description, canonical URL, OpenGraph/Twitter cards, JSON-LD), and crawl a page plus up to four linked same-site pages. Calls are paid per use in USDC via x402/MPP with no API key or account, and invalid inputs or unfetchable pages are never charged.3MIT
- FlicenseNot gradedqualityBmaintenanceEnables AI agents to extract structured JSON data from web pages using presets or custom JSON schemas, with confidence scores and source snippets, paid per call via USDC on Base.-
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to call pay-per-use web tools over Streamable HTTP—converting URLs to Markdown, extracting metadata and links, checking URL status, DNS, email domains, WHOIS, robots.txt, and generating domain reports—with per-call USDC payments on Base via x402 and no API keys.MIT
TDQS
Scored across 10 tools
Most tools have clearly distinct purposes, and the two family prefixes (weblens_ vs rugprobe_) help separate web-content utilities from Base token risk tools. There is some overlap between rugprobe_check and rugprobe_report because the report is a superset, and weblens_extract vs weblens_structure could occasionally be confused, but the descriptions clarify when to use each.
All tools follow a consistent snake_case family_action pattern, with weblens_ and rugprobe_ prefixes consistently identifying the product area. No mixed casing or vague verb styles appear.
Ten tools is well within a reasonable range, and each tool maps to a distinct operation or analysis workflow. Neither family feels padded or thin.
The surface covers solid core workflows for both web extraction/conversion and Base token due diligence, including content extraction, metadata, links, schema structuring, token risk checks, position sizing, and gas estimation. Minor gaps exist such as no search/crawl/batch web operations or token history/portfolio tools, but these are not fatal for the stated utility scope.