Ext Ops Panel
Open dashboard
Comparison

host.nippy/nippy vs io.github.Custodia-Admin/pagebolt

host.nippy/nippy is an MCP server published by nippy.host. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.Custodia-Admin/pagebolt is an MCP server published by Custodia-Admin. Marketplaces we read that list it: 1 (Official MCP Registry). 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

Where each is published
Marketplacehost.nippy/nippyio.github.Custodia-Admin/pagebolt
Official MCP Registry Listed
Version: 1.1.0
No figure published
Not marked · First seen
Listed
Version: 1.17.1
Downloads/month (npm): 777
Downloads/week (npm): 60
Forks (GitHub): 0
Stars (GitHub): 4
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

host.nippy/nippy vs io.github.Custodia-Admin/pagebolt
Facthost.nippy/nippyio.github.Custodia-Admin/pagebolt
Marketplaces that list it11
Stars (GitHub) (differs)No figure on GitHub4
Forks (GitHub) (differs)No figure on GitHub0
Last releaseNot publishedNot published
Where it runs (differs)Remote server (api.nippy.host/mcp)On your machine (pagebolt-mcp)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published1, secrets among them: 1
LicenceNot statedNot stated
Repository (differs)Not statedgithub.com/custodia-admin/pagebolt-mcp
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Responded 4 days ago, requires a keyno 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

host.nippy/nippy

In its own words, on Official MCP Registry:

Let Claude and ChatGPT publish real websites — iterate in previews, keep the good one.

io.github.Custodia-Admin/pagebolt

In its own words, on Official MCP Registry:

Screenshots, PDFs, OG images, page inspection, and narrated video recording for Claude and Cursor.

How to run each

host.nippy/nippy As a remote MCP server

Claude Code
claude mcp add --transport http nippy https://api.nippy.host/mcp

io.github.Custodia-Admin/pagebolt As a local MCP server: npm package

Claude Code
claude mcp add --env "PAGEBOLT_API_KEY=<YOUR_PAGEBOLT_API_KEY>" --transport stdio pagebolt -- npx -y pagebolt-mcp

Requires: PAGEBOLT_API_KEY (secret)

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

Only host.nippy/nippy 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 host.nippy/nippy publish no settings it asks for, so we do not compare settings.

What it can do: host.nippy/nippy · What it can do: io.github.Custodia-Admin/pagebolt · 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