Vendor domain: apify.com · vendor page id apify-com
A live handshake means the URL answered an MCP initialize as a server on the probe date. It is liveness and nothing more: nobody has run its tools. A tool being catalogued means a server names it, by answering tools/list, in its own source, or in the vendor's documentation. None of them has been called. A tool count of 0 means not measured, never zero tools.
A cloud platform for running "Actors" (hosted scrapers and automation programs, thousands of them in a public store) that extract web data such as LinkedIn posts, Google Maps listings, company sites and social feeds into datasets, with an API, scheduling and...
MCP server for AI agents: search local businesses on Google Maps, generate leads and validate emails. For Claude and Cursor. Pay-per-event.
MCP server with 10 B2B lead-gen tools for AI agents: emails, enrichment, lead discovery, hiring signals, tech stack, LinkedIn jobs. Claude Desktop, Curs...
1 of 3 free to start, a solo operator gets API access without talking to anyone. 2 of 3 gate unknown, not established from public sources and published as unknown.
The gate is the api_gate field on each product entry, established by hand on the last_checked date shown above. It records whether a solo operator can get API access without a contract. Money is not tracked.
No job tag on any product of this vendor.
An empty list means nobody has tagged these entries, not that the tools do nothing.
No product of this vendor records an MCP endpoint or docs URL that the probe could classify.
brew install apify-cliquoted from https://formulae.brew.sh/formula/apify-cli on 2026-09-27, via brew
harvested 2026-09-27, all on the tool page.
npm install -g apify-cliquoted from https://www.npmjs.com/package/apify-cli on 2026-09-27, via npm
1 more install command, harvested 2026-09-27, all on the tool page.
A CLI being listed means the harvest found an install command or a package on a stated date. Nobody has run it. Every command is quoted verbatim from the URL beneath it.
github.com/apify tied to the vendor by rule 3, account website https://apify.com/ has the vendor's domain, confidence strong
The five most recently pushed, on 2026-09-08:
| Repository | Kind | Description | Stars | Pushed | Latest release |
|---|---|---|---|---|---|
| agent-skills | other | Collection of Apify agent skills | 2,371 | 2026-09-08 | |
| apify-evals | other | 0 | 2026-09-08 | ||
| cgroups-sensor | other | Utility functions to measure resource limits from cgroups in scenarios where psutils is not sufficient. | 0 | 2026-09-08 | |
| actor-templates | docs or examples | This project is the :house: home of Apify Actor templates to help users quickly get started. Contributions welcome! | 60 | 2026-09-08 | |
| apify-mcp-server | MCP server | The Apify MCP server enables your AI agents to extract data from social media, search engines, maps, e-commerce sites,... | 6,380 | 2026-09-08 | v0.15.4 |
Kind is a heuristic guessed from the repository name, topics and description, not a fact the vendor stated. A repository count is activity, not a verdict. Read 2026-09-08.
No organisation could be tied with evidence to the entry for Google Maps Lead MCP by NextGenData, Sales Intelligence MCP by NextGenData on 2026-09-08, 2026-09-15; the organisation above was tied through a sibling product.
A job tag is a vendor claim: it means the vendor says the product does this, and it is not a test result. A listed tool has not been run: the catalogue says what an agent could try, not what works. 1 of 1,252 directory entries are bench tested, meaning somebody personally ran the tool on a stated date, and 0 of this vendor's 3 products are among them. There is no verdict here on whether this vendor is better than another.
Vendor pages group the directory's canonical product entries by vendor_domain. The vendor name is the product display name that matches the domain when several products share it; nothing on this page is typed by hand. Data baked 2026-09-27 by build_directory.py (phase 1).