Ext Ops Panel
Open dashboard
Comparison

PageVerified vs ogfetch

PageVerified is an MCP server published by pageverified.com. Marketplaces we read that list it: 1 (Official MCP Registry). ogfetch is an MCP server published by ogfetch.dev. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-10. 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
MarketplacePageVerifiedogfetch
Official MCP Registry Listed
Version: 1.0.0
No figure published
Not marked · First seen
Listed
Version: 1.0.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

PageVerified vs ogfetch
FactPageVerifiedogfetch
Marketplaces that list it11
Last releaseNot publishedNot published
Where it runs (differs)Remote server (pageverified.com/mcp)Remote server (ogfetch.dev/v1/mcp)
TransportStreamable HTTPStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
LicenceNot statedNot stated
RepositoryNot statedNot stated
Changes in the last 7 days (differs)20
First seen (differs)2026-11-092026-11-03
Endpoint at the last check (differs)not checked yetStatus out of date: last check 33 h ago returned HTTP 405

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

PageVerified

In its own words, on Official MCP Registry:

Paid tools for AI agents: web capture with SHA-256 receipts, tech-stack lookup and verification.

ogfetch

In its own words, on Official MCP Registry:

URL to JSON metadata: title, Open Graph, favicon, tech stack. Agents self-signup and pay in USDC.

How to run each

PageVerified As a remote MCP server

Claude Code
claude mcp add --transport http tools https://pageverified.com/mcp --header "Authorization: Bearer <YOUR_TOKEN>"

Requires: Authorization header

ogfetch As a remote MCP server

Claude Code
claude mcp add --transport http ogfetch https://ogfetch.dev/v1/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.

Only ogfetch 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

Neither one's marketplaces publish the settings it asks for.

What it can do: PageVerified · What it can do: ogfetch · 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