# Chicago Demolition Leads | Salvage Signal (remote · salvagesignal.com)

Chicago demolition and reclaimed-brick leads, pricing, and a human-confirmed Daily Drop handoff.

- Trust score: 76/100 (medium)
- Change this week: +6
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `salvagesignal.com`: 76/100 (this document), [markdown](https://verifymcp.io/servers/com-salvagesignal-salvage-signal/api-mcp.md), [page](https://verifymcp.io/servers/com-salvagesignal-salvage-signal/api-mcp)

## Channel facts

- Endpoint: `https://salvagesignal.com/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.3.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 77/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 387 tokens (~96/item across 4 items; 4 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http com-salvagesignal-salvage-signal https://salvagesignal.com/api/mcp
```

### Codex

```toml
[mcp_servers.com-salvagesignal-salvage-signal]
url = "https://salvagesignal.com/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-salvagesignal-salvage-signal": {
      "type": "remote",
      "url": "https://salvagesignal.com/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-salvagesignal-salvage-signal --url https://salvagesignal.com/api/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-salvagesignal-salvage-signal:
    url: "https://salvagesignal.com/api/mcp"
```

### Other

```json
{
  "mcpServers": {
    "com-salvagesignal-salvage-signal": {
      "type": "http",
      "url": "https://salvagesignal.com/api/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-02 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 75, +3)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 72, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-28 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-27 (score 70, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 69)

First indexed and scored.

## MCP tools (4)

### `search_salvage_signals` (~111 tokens)

Search Chicago salvage signals

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.

Input parameters:

- `limit` (integer): Maximum number of ranked signals to return.
- `material` (string): Material or building-characteristic filter.
- `urgency` (string): Salvage Signal urgency band.

Output parameters:

- `dataMode` (string)
- `market` (string)
- `safety` (string)
- `signalCount` (integer)
- `signals` (array)
- `source` (object)

### `get_chicago_reuse_brief` (~58 tokens)

Get the Chicago Teardown-to-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.

Output parameters:

- `dataMode` (string)
- `market` (string)
- `name` (string)
- `safety` (string)
- `source` (object)
- `summary` (object)
- `watchList` (array)

### `get_salvage_signal_offer` (~64 tokens)

Get Salvage Signal product and pricing facts

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.

Output parameters:

- `dailyDrop` (object)
- `description` (string)
- `name` (string)
- `safety` (string)
- `source` (object)
- `url` (string)

### `get_subscription_handoff` (~103 tokens)

Get a human-confirmed subscription handoff

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.

Input parameters:

- `campaign` (string): Short campaign identifier used only for signup attribution.
- `source` (string): Short agent or channel identifier used only for signup attribution.

Output parameters:

- `agentPolicy` (object)
- `humanDecision` (object)
- `links` (object)
- `pricing` (object)
- `product` (object)
- `readOnly` (boolean)
- `schemaVersion` (string)
- `status` (string)
- `type` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-salvagesignal-salvage-signal/api-mcp#diagnostics

## Score history

- 2026-08-03: 76
- 2026-08-02: 76
- 2026-08-01: 75
- 2026-07-31: 75
- 2026-07-30: 72
- 2026-07-29: 71
- 2026-07-28: 71
- 2026-07-27: 70
- 2026-07-26: 69

## Links

- Remote endpoint: https://salvagesignal.com/api/mcp
- Website: https://salvagesignal.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-salvagesignal-salvage-signal/api-mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-salvagesignal-salvage-signal/api-mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/com-salvagesignal-salvage-signal/api-mcp