com.onegoodarea/oga-mcp vs Building Permits & Code Violations Scraper — Owner Skip Trace
com.onegoodarea/oga-mcp is an MCP server published by onegoodarea.com. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). Building Permits & Code Violations Scraper — Owner Skip Trace is an MCP server published by ceadigital. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-15. 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 |  com.onegoodarea/oga-mcp | |
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.15 Downloads/month (npm): 1 162 Downloads/week (npm): 353 Not marked · First seen |
Listed Version: 1.0.0 No figure published Not marked · First seen |
| npm registry (MCP servers) | Listed Version: 1.0.15 Downloads/month (npm): 1 162 Downloads/week (npm): 353 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Not listed |
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 | com.onegoodarea/oga-mcp | Building Permits & Code Violations Scraper — Owner Skip Trace |
|---|---|---|
| Marketplaces that list it (differs) | 2 (better) | 1 (worse) |
| Stars (GitHub) (differs) | 0 | No figure on GitHub |
| Forks (GitHub) (differs) | 0 | No figure on GitHub |
| Last release (differs) | 2026-11-03 | Not published |
| Where it runs (differs) | Remote server or your machine | Remote server (ceadigital.io/mcp) |
| Transport | Streamable HTTP | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 2, secrets among them: 1 | Not published |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/onegoodarea/oga-mcp | Not stated |
| Changes in the last 7 days (differs) | 0 | 2 |
| First seen (differs) | 2026-10-11 | 2026-11-10 |
| Endpoint at the last check (differs) | Responded 11 h ago, requires authentication | Responded 11 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
com.onegoodarea/oga-mcp
Sourced facts, explained scores and change alerts for every GB neighbourhood, from one API.
Building Permits & Code Violations Scraper — Owner Skip Trace
Live Socrata building permits & code violations with auto-chained LLC owner wireless phone lookup.
How to run each
com.onegoodarea/oga-mcp As a remote MCP server
claude mcp add --transport http oga-mcp https://api.onegoodarea.com/mcp --header "Authorization: Bearer <YOUR_TOKEN>"Requires: OOGA_API_KEY (secret), Authorization header
Building Permits & Code Violations Scraper — Owner Skip Trace As a remote MCP server
claude mcp add --transport http building-permits-code-violations-scraper https://ceadigital.io/mcpCommands 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
The marketplaces of Building Permits & Code Violations Scraper — Owner Skip Trace publish no settings it asks for, so we do not compare settings.
What it can do: com.onegoodarea/oga-mcp · What it can do: Building Permits & Code Violations Scraper — Owner Skip Trace · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the public npm registry (registry.npmjs.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.