Email Finder Server vs pline.ai
Email Finder Server is an MCP server published by admosolutionsgo-star. Marketplaces we read that list it: 1 (Official MCP Registry). pline.ai is an MCP server published by grepsr. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-27. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  Email Finder Server |  pline.ai |
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.0 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Listed Version: 0.3.9 Downloads/month (npm): 935 Downloads/week (npm): 429 Forks (GitHub): 0 Stars (GitHub): 1 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | Email Finder Server | pline.ai |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 0 (worse) | 1 (better) |
| Forks (GitHub) | 0 | 0 |
| Last release (differs) | Not published | 2026-10-14 |
| Where it runs (differs) | Remote server (mcp.apify.com) | On your machine (pline-api) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 2, secrets among them: 1 |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/admosolutionsgo-star/email-finder-server | github.com/grepsr/pline-api |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Not responding since 2026-10-24 | no remote endpoint we check |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
Email Finder Server
Extract emails and phones from any website via Apify.
pline.ai
Scrape, crawl, batch-scrape, map, and search the web through the hosted pline.ai API.
How to run each
Email Finder Server
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
pline.ai As a local MCP server: npm package
claude mcp add --env "PLINE_API_KEY=<YOUR_PLINE_API_KEY>" --transport stdio pline-api -- npx -y pline-apiRequires: PLINE_API_KEY (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Email Finder Server has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
The marketplaces of Email Finder Server publish no settings it asks for, so we do not compare settings.
What it can do: Email Finder Server · What it can do: pline.ai · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.