Ext Ops Panel
Open dashboard
Comparison

io.github.Cal-Dev-Tech/perpage-mcp-server vs io.github.robertoyanguas-ops/llms-generator-mcp

io.github.Cal-Dev-Tech/perpage-mcp-server is an MCP server published by Cal-Dev-Tech. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.robertoyanguas-ops/llms-generator-mcp is an MCP server published by robertoyanguas-ops. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-28. 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
Marketplaceio.github.Cal-Dev-Tech/perpage-mcp-serverio.github.robertoyanguas-ops/llms-generator-mcp
Official MCP Registry Listed
Version: 0.1.3
Downloads/month (npm): 715
Downloads/week (npm): 120
Not marked · First seen
Listed
Version: 1.1.0
No figure published
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

io.github.Cal-Dev-Tech/perpage-mcp-server vs io.github.robertoyanguas-ops/llms-generator-mcp
Factio.github.Cal-Dev-Tech/perpage-mcp-serverio.github.robertoyanguas-ops/llms-generator-mcp
Marketplaces that list it11
Last release (differs)Not published2026-10-13
Where it runs (differs)On your machine (@perpage/mcp-server)Remote server (llms-generator-72343955726.us-central1.run.app/mcp/llms-generator)
Transport (differs)stdioStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)2, secrets among them: 1Not published
LicenceNot statedNot stated
RepositoryNot statedNot stated
Changes in the last 7 days00
First seen (differs)2026-10-112026-10-13
Endpoint at the last check (differs)no remote endpoint we checkResponded 4 days ago

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

io.github.Cal-Dev-Tech/perpage-mcp-server

In its own words, on Official MCP Registry:

Give AI agents clean, LLM-ready web data — scrape any URL to markdown or extract structured JSON.

io.github.robertoyanguas-ops/llms-generator-mcp

In its own words, on Official MCP Registry:

Crawls any website and generates a standards-compliant /llms.txt file and JSON-LD schema bundle.

How to run each

io.github.Cal-Dev-Tech/perpage-mcp-server As a local MCP server: npm package

Claude Code
claude mcp add --env "PERPAGE_API_KEY=<YOUR_PERPAGE_API_KEY>" --transport stdio perpage-mcp-server -- npx -y @perpage/mcp-server

Requires: PERPAGE_API_KEY (secret)

io.github.robertoyanguas-ops/llms-generator-mcp As a remote MCP server

Claude Code
claude mcp add --transport http llms-generator-mcp https://llms-generator-72343955726.us-central1.run.app/mcp/llms-generator

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

Only io.github.robertoyanguas-ops/llms-generator-mcp 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 io.github.robertoyanguas-ops/llms-generator-mcp publish no settings it asks for, so we do not compare settings.

What it can do: io.github.Cal-Dev-Tech/perpage-mcp-server · What it can do: io.github.robertoyanguas-ops/llms-generator-mcp · 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.

Where the data comes from: how the catalog is built