Ext Ops Panel
Open dashboard
Comparison

SAM.gov vs Code Violations & Distressed Property Leads — Owner Phones

SAM.gov is an MCP server published by 1102tools.com. Marketplaces we read that list it: 2 (Official MCP Registry, PyPI (MCP servers)). Code Violations & Distressed Property Leads — Owner Phones 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-14. 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
MarketplaceSAM.govCode Violations & Distressed Property Leads — Owner Phones
Official MCP Registry Listed
Version: 1.0.18
Downloads/month (PyPI): 638
Downloads/week (PyPI): 102
Forks (GitHub): 10
Stars (GitHub): 32
Not marked · First seen
Listed
Version: 1.0.0
No figure published
Not marked · First seen
PyPI (MCP servers) Listed
Version: 1.0.18
Downloads/month (PyPI): 638
Downloads/week (PyPI): 102
Forks (GitHub): 10
Stars (GitHub): 32
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

SAM.gov vs Code Violations & Distressed Property Leads — Owner Phones
FactSAM.govCode Violations & Distressed Property Leads — Owner Phones
Marketplaces that list it (differs)2 (better)1 (worse)
Stars (GitHub) (differs)32No figure on GitHub
Forks (GitHub) (differs)10No figure on GitHub
Last release (differs)2026-10-28Not published
Where it runs (differs)Remote server or your machineRemote server (ceadigital.io/mcp)
Transport (differs)Streamable HTTP, stdioStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)1, secrets among them: 1Not published
Licence (differs)MITNot stated
Repository (differs)github.com/1102tools-dev/federal-contracting-mcpsNot stated
Changes in the last 7 days (differs)02
First seen (differs)2026-10-112026-11-10
Endpoint at the last checkResponded 11 h agoResponded 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

SAM.gov

In its own words, on Official MCP Registry:

SAM.gov readiness, entities, exclusions, opportunities, awards, hierarchy, and subawards. 20 tools.

Code Violations & Distressed Property Leads — Owner Phones

In its own words, on Official MCP Registry:

Scrape municipal code violations & distressed property liens with auto-chained LLC owner phones.

How to run each

SAM.gov As a remote MCP server

Claude Code
claude mcp add --transport http sam-gov-mcp https://sam.1102tools.com/mcp

Requires: SAM_API_KEY (secret)

Code Violations & Distressed Property Leads — Owner Phones As a remote MCP server

Claude Code
claude mcp add --transport http code-violations-distressed-property-scra https://ceadigital.io/mcp

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 the marketplaces of Code Violations & Distressed Property Leads — Owner Phones nor its endpoint list any tools, so we do not compare tools.

Settings each asks for

The marketplaces of Code Violations & Distressed Property Leads — Owner Phones publish no settings it asks for, so we do not compare settings.

What it can do: SAM.gov · What it can do: Code Violations & Distressed Property Leads — Owner Phones · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the Python Package Index (pypi.org). 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