"OWASP Dependency-Check" matching MCP connectors:
GET /v1/connectors – MCP directory API referenceMatching Connector Tools:
Google is not the whole market. Your agent needs Bing, Yahoo, Baidu, Naver, Seznam and YouTube results — the engines that decide whether you exist in China, Korea, Japan or Central Europe. **What you can ask for** • "What ranks for this term on Baidu, and how different is it from Google?" • "Check Naver results for our Korean brand name." • "Compare Bing and Yahoo results for the same query." • "What comes up on YouTube search for this phrase in Japanese?" • "Take a screenshot of the results page as a user there sees it." **How to use it** Point any MCP client at https://mcp.aisa.one/seo-serp-other-engines/mcp and sign in with OAuth — there is no key to create or paste. 34 tools: organic results from Bing, Yahoo, Baidu, Naver and Seznam in live, regular and raw-HTML forms, YouTube search, an AI summary of a result set, and a rendered screenshot. **Why this rather than the source** The engines that matter outside the US, with the same call shape as the Google ones. **It is also a door to the rest** The same login reaches 26 sources and 580+ operations. Check the local engine here, then ask the same agent what the site's traffic or backlinks look like in that market — without adding a second server. **What it costs** Finding and inspecting an operation is free. Running one is billed per call at API prices, with no seat and no monthly minimum, and every call takes max_price_usd so an agent cannot overspend by accident. **Where else it reaches** https://mcp.aisa.one/seo-serp/mcp for Google itself. https://mcp.aisa.one/seo/mcp for all of it at once — rankings, keywords, backlinks, site health and AI-answer visibility across DataForSEO, Semrush and Ahrefs.
Check how well AI agents can discover and understand a public website.
Watch any URL for changes: baseline, then check for a diff. Free, no signup/key.
AI-search-visibility tools: check crawler access, generate llms.txt, lint robots.txt, census data.
8 pay-per-call web intelligence tools for AI agents: detect a site's tech stack and track stack changes, check domain health, extract structured data or clean markdown from any URL, turn sitemaps into knowledge bases, analyze Shopify and Zid stores. Free discovery + pricing_info; paid calls $0.01-0.02 in USDC on Base via x402 — pay only for successful runs.
Validate HTML and CSS, audit SEO and JSON-LD, and check user-authorized public links.
Structured data validator in one call: extracts JSON-LD, microdata and RDFa from a URL or raw HTM...
Pay-per-call web intel: extract, search, link check, domain, geo, Nano. Settled via Nano x402.
Check whether a website is ready for AI agents (UCP, WebMCP, Access) and monitor your own sites.
AI-operated. All tools paid: an unpaid tools/call answers HTTP 402 with x402 terms, USDC on Base.
Check how to contact a business website, and whether that contact path actually works.
Check how to contact a business website, and whether that contact path actually works.
Web tools for AI agents: scrape pages to Markdown, audit SEO, detect tech stacks, check sitemaps
Does a site publish llms.txt, robots permissions and a sitemap agents can use? Bounded check.
Scores any public website on how usable it is by AI agents, with per-check evidence.
Is this website visible to AI agents? Robots, llms.txt, sitemap, extraction, then placement.
Check whether a website is readable by AI agents: robots, llms.txt, sitemap, HTML. Bounded.
Bounded crawl-readiness check for agent access: robots.txt, sitemap.xml, llms.txt, homepage.
Ten machine-readable signals on one public page: the top miss if any, and a receipt we re-verify.
Check x402 endpoints before paying: liveness, price history, farm detection. Plus RU web access.
