WebDataTools Developer, app & research data MCP server
Related Servers
Alternatives to WebDataTools Developer, app & research data MCP server
No user-submitted related servers found.
Related Servers
AlicenseNot gradedqualityCmaintenanceEnables AI agents to access fourteen web-data tools for scraping, SEO and site auditing, extraction, validation, enrichment, and screenshots through Apify actors. It runs those tools on the user's own Apify account via an API token.MIT- AlicenseNot gradedqualityCmaintenanceEnables AI agents to search and retrieve government contracts, job postings, LinkedIn profiles, YC startups, contact details, tech stacks, PDF text, and Google Trends through 13 integrated tools. It returns compact JSON, handles long-running queries with progress and run results paging, and runs the underlying scrapers on the user's Apify account.MIT
- AlicenseAqualityAmaintenanceEnables AI agents to pull structured web data (news, reviews, jobs, products) as clean JSON via ready-made Apify Actors on a pay-per-result basis. Built-in safeguards like cost caps, item limits, and truncated text protect agent context from flooding.12466 npmMIT

kanto-labs-mcpofficial
AlicenseAqualityAmaintenanceEnables AI assistants to run pay-per-result web data and media tools such as website tech stack detection, document-to-Markdown conversion, SEO audits, OCR, and domain lookups via Apify.14MIT- AlicenseNot gradedqualityDmaintenanceProvides AI agents with real-time web capabilities including live search results, markdown web scraping, business lead generation, and detailed company information. It enables agents to bypass knowledge cutoffs by accessing current web data through a monetized Apify Actor.MIT
- AlicenseAqualityAmaintenanceThis MCP server equips AI agents with ten web-data tools for web search, page reading, site crawling, contact and tech-stack detection, company profiling, e-mail/DNS security checks, e-mail validation, package health, and raw Google search. Each call runs Actors on the user's own Apify account, returning trimmed, readable dataset rows.10MIT
TDQS
Scored across 13 tools
Each tool targets a distinct data source or platform (npm/PyPI, GitHub, VS Code, Chrome, Google Play, App Store, CrossRef, openFDA, iCal, Shopify, Hacker News, GitHub trending, Stack Exchange). The only slight overlap is between github_repo_health and github_trending_scraper, but they serve different purposes (health metrics vs trending repos), so confusion is minimal.
Names follow a general noun/action pattern but mix conventions: some use underscores (package_health_checker), some use camelCase-like concatenation (github_repo_health), and some are verb phrases (app_store_lookup). The inconsistency is noticeable but each name remains readable and descriptive.
13 tools is a reasonable count for a multi-source data aggregation server. Each tool covers a distinct data source, so the set is well-scoped, though it could be considered slightly heavy if more sources are added without grouping.
The server covers a broad range of developer, app, and research data sources with read-only scraping/lookup operations. However, it lacks tools for write operations (e.g., posting to Hacker News, managing repositories) and some potential sources (e.g., Reddit, Product Hunt), but for a data retrieval server, the surface is fairly complete.