loudtzu-actors-mcp
Related Servers
Alternatives to loudtzu-actors-mcp
No user-submitted related servers found.
Related Servers
AlicenseNot gradedqualityBmaintenanceEnables 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- AlicenseAqualityBmaintenanceGives AI agents 13 data tools covering package and repo health, browser and mobile app-store listings, DOI and FDA recall lookups, iCal feeds, Shopify products, and Hacker News and Stack Exchange search. Each call runs a backer's Actor under your own Apify token, so usage is billed to your account.13MIT
- AlicenseAqualityBmaintenanceEnables AI agents to retrieve competitor Google ads, app reviews, job postings, PDF tables, bank statement and invoice data, clean email lists, capture website screenshots, and find broken links through Apify-backed tools.14MIT
- AlicenseAqualityBmaintenanceEnables AI agents and MCP clients to retrieve company profiles, hiring signals, YC companies, Wikidata enrichment, email validation, OpenStreetMap places, market quotes, and remote jobs via eight tools backed by the user's own Apify account.8MIT
- AlicenseNot gradedqualityBmaintenanceExposes typed tools that forward requests to Apify actors for public-data lookups and scraping across sanctions, SEC filings, layoffs, licensing, SEO, jobs, permits, maps, social media, marketplace, and government data. It lets MCP clients run these data-collection workflows using their own Apify token.1MIT
- AlicenseNot gradedqualityNot gradedmaintenanceExposes over 19,000 Apify Actors as MCP tools for web scraping, data extraction, and OSINT automation. It enables AI agents to dynamically discover and execute scrapers to collect structured data and crawl web content.MIT
TDQS
Scored across 9 tools
Each tool maps to a single, clearly named external data source: two retail-scraping tools are separated by platform (Shopify vs WooCommerce), and the Canadian datasets (recalls, building permits, corporations, charities, funding) target entirely different record types. No two tools could plausibly be selected for the same query, and each description states required inputs (e.g. keywords required for Loblaws) that further pin down use.
All nine names are snake_case and follow a uniform source-descriptor pattern (source_or_dataset + object, e.g. canada_federal_corporations, loblaws_grocery_prices, shopify_store_products). The convention is noun-oriented rather than verb_noun, but it is applied with zero deviation, which is what matters for predictability.
Nine tools sit comfortably in the well-scoped range, and each corresponds to one distinct Apify Actor with a unique data source. There is no filler or near-duplicate tool padding the set.
Each tool offers a search/export with rich filters, which is the full lifecycle for a read-only dataset endpoint, and the Canadian public-data domain is covered across several distinct registries. Minor gaps remain: no way to fetch details by identifier, broaden to other Apify Actors, or retrieve past run outputs, and coverage of Canadian open data is a curated subset rather than exhaustive.