Ext Ops Panel
Open dashboard
Comparison

Micro Tool Factory — Commerce, Jobs and Web Data vs pline.ai

Micro Tool Factory — Commerce, Jobs and Web Data is an MCP server published by amitudai. 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: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-11-08. 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

Where each is published
MarketplaceMicro Tool Factory — Commerce, Jobs and Web Datapline.ai
Official MCP Registry Listed
Version: 1.0.3
No figure published
Not marked · First seen
Listed
Version: 0.3.12
Downloads/month (npm): 1 329
Downloads/week (npm): 356
Forks (GitHub): 0
Stars (GitHub): 19
Not marked · First seen
npm registry (MCP servers) Not listed Listed
Version: 0.3.12
Downloads/month (npm): 1 329
Downloads/week (npm): 356
Forks (GitHub): 0
Stars (GitHub): 19
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

Micro Tool Factory — Commerce, Jobs and Web Data vs pline.ai
FactMicro Tool Factory — Commerce, Jobs and Web Datapline.ai
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)No figure on GitHub19
Forks (GitHub) (differs)No figure on GitHub0
Last release (differs)2026-10-29 (worse)2026-11-04 (better)
Where it runs (differs)Remote server (mcp.apify.com)On your machine (pline-api)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published2, secrets among them: 1
Licence (differs)Not statedMIT
Repository (differs)Not statedgithub.com/grepsr/pline-api
Changes in the last 7 days (differs)04
First seen (differs)2026-10-202026-10-11
Endpoint at the last check (differs)Status out of date: last check 2 days ago returned HTTP 401no 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

Micro Tool Factory — Commerce, Jobs and Web Data

In its own words, on Official MCP Registry:

Shopify, jobs, feeds, GitHub, Hacker News, YouTube and Apple App Store via Apify MCP.

pline.ai

In its own words, on Official MCP Registry:

Scrape, crawl, batch-scrape, map, and search the web through the hosted pline.ai API.

How to run each

Micro Tool Factory — Commerce, Jobs and Web Data

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 Code
claude mcp add --env "PLINE_API_KEY=<YOUR_PLINE_API_KEY>" --transport stdio pline-api -- npx -y pline-api

Requires: PLINE_API_KEY (secret)

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only Micro Tool Factory — Commerce, Jobs and Web Data 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 Micro Tool Factory — Commerce, Jobs and Web Data publish no settings it asks for, so we do not compare settings.

What it can do: Micro Tool Factory — Commerce, Jobs and Web Data · What it can do: pline.ai · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the public npm registry (registry.npmjs.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built