Ext Ops Panel
Open dashboard
Comparison

openwebninja-universal-scraper vs ParseAddr — Address Parsing & Normalization

openwebninja-universal-scraper is a plugin bundle for AI coding tools published by OpenWeb-Ninja. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). ParseAddr — Address Parsing & Normalization is an MCP server published by parseaddr.com. Marketplaces we read that list it: 1 (Official MCP Registry). 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
Marketplaceopenwebninja-universal-scraperParseAddr — Address Parsing & Normalization
Claude Code: claude-plugins-community Listed
Version: 1.0.0
Forks (GitHub): 0
Stars (GitHub): 4
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.1.0
Forks (GitHub): 0
Stars (GitHub): 0
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

openwebninja-universal-scraper vs ParseAddr — Address Parsing & Normalization
Factopenwebninja-universal-scraperParseAddr — Address Parsing & Normalization
Marketplaces that list it11
Stars (GitHub) (differs)4 (better)0 (worse)
Forks (GitHub)00
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleRemote server (api.parseaddr.com/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Licence (differs)MITNot stated
Repository (differs)github.com/openweb-ninja/openwebninja-skillsgithub.com/wezpyke/parseaddr-mcp
Changes in the last 7 days00
First seen (differs)2026-10-112026-10-12
Endpoint at the last check (differs)no remote endpoint we checkStatus out of date: last check 31 h ago returned HTTP 406

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

openwebninja-universal-scraper

In its own words, on Claude Code: claude-plugins-community:

Extract structured data from 35+ public web APIs using natural language. Covers local businesses, jobs, products, reviews, news, social profiles, real estate, and finance. Outputs to JSON, CSV, Webhook, S3, FTP, Airtable, Google Sheets, or Slack.

ParseAddr — Address Parsing & Normalization

In its own words, on Official MCP Registry:

Hosted libpostal: messy free-text postal addresses → structured fields. No 2-4GB self-host.

How to run each

openwebninja-universal-scraper As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install openwebninja-universal-scraper@claude-community

ParseAddr — Address Parsing & Normalization As a remote MCP server

Claude Code
claude mcp add --transport http address-parse https://api.parseaddr.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.

Only ParseAddr — Address Parsing & Normalization 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: openwebninja-universal-scraper · What it can do: ParseAddr — Address Parsing & Normalization · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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