Apify
Server Details
Apify MCP — run web-scraping Actors and fetch their dataset results.
Glama couldn't complete the latest health check. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.
If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.
- Status
- Unhealthy
- Uptime
- 0.1% over 22 days
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- pipeworx-io/mcp-apify
- GitHub Stars
- 1
- Server Listing
- mcp-apify
TDQS
Scored across 39 tools
Multiple tools have poorly defined boundaries: ask_pipeworx, ask_pipeworx_beta (currently identical), and ask_pipeworx_grounded all route to the same 6,216 tools, and the prediction-market cluster (polymarket_arbitrage, polymarket_edges, polymarket_edge_tracker, polymarket_fill_risk, polymarket_kalshi_spread, bet_research, kalshi_weather_edge) has heavy conceptual overlap. An agent could easily select the wrong entry point.
Names are uniformly snake_case, but the pattern is mixed: some follow verb_noun (list_subscriptions, resolve_entity, scan_dependency), some are bare product/domain names (ask_pipeworx, entity_profile, polymarket_arbitrage), and Apify tools use an apify_ prefix. Readable, but not a consistent semantic convention.
39 tools is well past the heavy range, and the surface sprawls across scraping, structured-data lookup, prediction-market analytics, memory, and subscriptions. Many tools appear bolted on rather than part of a single coherent purpose, making the set feel bloated.
As an 'Apify' server, scraping coverage is minimal (only three tools, mostly wrappers), with no actor management, task scheduling, or storage APIs. The data-lookup and prediction-market side is broad, but the stated primary domain is underserved, leaving significant gaps for the server's apparent purpose.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
39 tool updates
- First observed
ai_visibility_check - First observed
apify_dataset_items - First observed
apify_run_actor - First observed
apify_scrape_url - First observed
ask_pipeworx - First observed
ask_pipeworx_beta - First observed
ask_pipeworx_grounded - First observed
bet_research - First observed
company_facts - First observed
compare_entities - First observed
deep_research - First observed
discover_tools - First observed
entity_profile - First observed
forget - First observed
generate_llms_txt - First observed
kalshi_weather_edge - First observed
list_subscriptions - First observed
pipeworx_feedback - First observed
pipeworx_trending - First observed
polymarket_arbitrage - First observed
polymarket_edge_tracker - First observed
polymarket_edges - First observed
polymarket_fill_risk - First observed
polymarket_kalshi_spread - First observed
recall - First observed
recent_alerts - First observed
recent_changes - First observed
release_calendar_markets - First observed
remember - First observed
resolution_audit - First observed
resolution_diff - First observed
resolve_entity - First observed
scan_competitor_ai_presence - First observed
scan_dependency - First observed
search_within - First observed
subscribe - First observed
suggest_questions - First observed
unsubscribe - First observed
validate_claim
Related MCP Connectors
Seven pay-per-event Apify Actors (PDF/CSV/links/sitemap/email/phone/VAT) as MCP tools.
SAP SuccessFactors public career-site jobs via an Apify Actor, hosted MCP.
17 data tools in one MCP server, run on Apify: Google Shopping, Flights, Hotels, News, Images, Videos, Ads Transparency, Jobs and Trends; YouTube transcripts; AI visibility checks; Google Maps leads; App Store and Google Play reviews. Pay per result. Sign in with Apify (OAuth) or an API token.
Apify MCP: retrainmap/federal-register-documents - Federal Register API, one row per document
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceEnables web scraping, browser automation, and dataset management through Apify's actor platform.MIT
- AlicenseAqualityBmaintenanceEnables MCP clients to run Apify-compatible web scrapers locally via stdio or HTTP, including site crawling, job board retrieval, web search, Google Maps and LinkedIn job lookups, with run management, dataset storage, and a REST API.26MIT
- AlicenseAqualityBmaintenanceAn MCP server that runs Apify scraping actors with quality-gated validation, scoring, and retries, returning embedding-ready chunks for AI agents.71MIT
- AlicenseBqualityDmaintenanceEnables AI assistants to interact with the Apify platform to manage actors, monitor runs, and retrieve scraped data from datasets. It supports natural language commands for executing web scrapers, managing tasks, and accessing key-value stores.28MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.