Fetch MCP Server vs Olostep MCP Server
Fetch MCP Server is an MCP server published by YawLabs. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). Olostep MCP Server is an MCP server published by olostep. Marketplaces we read that list it: 2 (Official MCP Registry, Claude Code: claude-plugins-community). As of our marketplace pass on 2026-10-29. 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 | ||
|---|---|---|
| Official MCP Registry | Listed Version: 0.8.5 Downloads/month (npm): 1 595 Downloads/week (npm): 154 Forks (GitHub): 1 Stars (GitHub): 2 Not marked · First seen |
Listed Version: 1.0.19 Downloads/month (npm): 763 Downloads/week (npm): 220 Forks (GitHub): 10 Stars (GitHub): 25 Not marked · First seen |
| npm registry (MCP servers) | Listed Version: 0.8.5 Downloads/month (npm): 1 595 Downloads/week (npm): 154 Forks (GitHub): 1 Stars (GitHub): 2 Not marked · First seen |
Not listed |
| Claude Code: claude-plugins-community | Not listed | Listed Version: 1.0.0 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 | Fetch MCP Server | Olostep MCP Server |
|---|---|---|
| Marketplaces that list it | 2 | 2 |
| Stars (GitHub) (differs) | 2 (worse) | 25 (better) |
| Forks (GitHub) (differs) | 1 (worse) | 10 (better) |
| Last release (differs) | 2026-10-11 (worse) | 2026-10-28 (better) |
| Where it runs (differs) | On your machine (@yawlabs/fetch-mcp) | Remote server or your machine |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 1, secrets among them: 1 |
| Parts of the bundle (differs) | Not a bundle | 14 |
| Licence | MIT | MIT |
| Repository (differs) | github.com/yawlabs/fetch-mcp | github.com/olostep/olostep-mcp-server |
| Changes in the last 7 days (differs) | 0 | 6 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | not checked yet |
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
Fetch MCP Server
HTTP fetch MCP server: SSRF protection, HTML-to-markdown, reader mode, metadata extraction
Olostep MCP Server
Live web search, scraping and crawling API for AI. Get structured, LLM-ready data from any site.
How to run each
Fetch MCP Server As a local MCP server: npm package
claude mcp add --transport stdio fetch-mcp -- npx -y @yawlabs/fetch-mcp
Olostep MCP Server As a remote MCP server
claude mcp add --transport http olostep-mcp-server https://mcp.olostep.com/mcp --header "Authorization: Bearer <YOUR_TOKEN>"
Requires: Authorization header
Commands built only from what the marketplaces declare; the full set for every client is on each card.
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 Fetch MCP Server publish no settings it asks for, so we do not compare settings.
What it can do: Fetch MCP Server · What it can do: Olostep MCP Server · 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). Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.