GC AI vs ParseAddr — Address Parsing & Normalization
GC AI is a plugin bundle for AI coding tools published by GC-AI-Inc. Marketplaces we read that list it: 2 (Claude Code: claude-plugins-official, Claude: knowledge-work-plugins). 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-10-22. 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 |  GC AI |  ParseAddr — Address Parsing & Normalization |
|---|---|---|
| Claude Code: claude-plugins-official | Listed Version: 0.1.0 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Not listed |
| Claude: knowledge-work-plugins | Listed Version: 0.1.0 Forks (GitHub): 0 Stars (GitHub): 0 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
| Fact | GC AI | ParseAddr — Address Parsing & Normalization |
|---|---|---|
| Marketplaces that list it (differs) | 2 (better) | 1 (worse) |
| Stars (GitHub) | 0 | 0 |
| Forks (GitHub) | 0 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (app.gc.ai/api/mcp) | Remote server (api.parseaddr.com/mcp) |
| Transport | Streamable HTTP | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | 5 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/gc-ai-inc/gc-ai-claude-plugin | github.com/wezpyke/parseaddr-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-11 | 2026-10-12 |
| Endpoint at the last check (differs) | Responded 39 h ago | Responded 46 h 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
GC AI
Work in your GC AI legal knowledge base from Claude: upload documents, run review playbooks, and ask questions grounded in your own files, all as you.
ParseAddr — Address Parsing & Normalization
Hosted libpostal: messy free-text postal addresses → structured fields. No 2-4GB self-host.
How to run each
GC AI As a Claude Code plugin
/plugin install gc-ai@claude-plugins-officialParseAddr — Address Parsing & Normalization As a remote MCP server
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.
Both endpoints responded at the last daily 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: GC AI · 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-official/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the public marketplace file https://github.com/anthropics/knowledge-work-plugins/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.