mcp server
Chicago Demolition Leads | Salvage Signal
Chicago demolition and reclaimed-brick leads, pricing, and a human-confirmed Daily Drop handoff.
Description as published by the maintainer. Source
- version 1.3.0
- active
active — Registry entry last updated 2026-07-21.
What this server can do
4 functions, named and described by the server itself. Parameter names are shown because they say more about what a function does than its name usually does.
get_chicago_reuse_brief- Use for a current Chicago teardown-to-reuse overview, aggregate trends, and a ranked watch list with source and safety context. For a material- or urgency-filtered candidate list, use search_salvage_signals instead.
get_salvage_signal_offer- Use for factual questions about Salvage Signal's audience, free board, Daily Drop price, live aggregate founding availability, source, safety, or signup terms. This does not prepare a purchase link; use get_subscription_handoff only after a human expresses subscription interest.
get_subscription_handoff(source, campaign)- Use only after a human expresses interest in subscribing or asks for the checkout path. It returns exact Chicago Daily Drop terms and an attributed signup URL. For price-only questions, use get_salvage_signal_offer. This tool is read-only: it accepts no email or payment data and cannot complete a purchase.
search_salvage_signals(limit, urgency, material)- Use when a human or agent needs specific current Chicago demolition-permit prospects, especially by material, urgency, or result count. For an aggregate trend summary and fixed watch list, use get_chicago_reuse_brief instead. Results are public prospecting clues, never site-access permission or inventory guarantees.
Last successful function declaration observed on . Source: https://salvagesignal.com/api/mcp. We list what the server declared; we do not call any of these functions.
Endpoint status observed on . Source: https://salvagesignal.com/api/mcp.
Signals
These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.
| Signal | Value | What it measures | Window | Observed | Source |
|---|---|---|---|---|---|
| Latest published version | 1.3.0 | Latest version string the maintainer published to the registry. | as of fetch | Model Context Protocol | |
| Registry record last updated | 2026-07-21 | When the registry record was last updated by its maintainer. | point in time | Model Context Protocol | |
| First listed in the MCP Registry | 2026-07-21 | Date this server was first published to the official MCP Registry. Not a usage or quality measure. | point in time | Model Context Protocol | |
| mcp tools declared | 4 tools | Number of functions the server itself declared when asked to list them. This is what the server offers an agent, not a measure of how well any of them work. | as of probe | salvagesignal.com | |
| mcp endpoint status | ok | The server listed 4 functions when asked. | as of probe | salvagesignal.com |
Where to get it
This record as data
Every field on this page, with its source and observation date, is in the catalog JSON. Fetch the whole kind at once instead of parsing this HTML.
GET /api/v1/entries/mcp_server.json