Chicago Demolition Leads | Salvage Signal
REMOTE · SALVAGESIGNAL.COM · SCANNED SEP 20
Chicago demolition and reclaimed-brick leads, pricing, and a human-confirmed Daily Drop handoff.
Available components
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. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability79
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 387 tokens (~96/item across 4 items; 4 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the Chicago Demolition Leads | Salvage Signal MCP server?
Chicago Demolition Leads | Salvage Signal is a hosted endpoint at https://salvagesignal.com/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · salvagesignal.com
claude mcp add --transport http com-salvagesignal-salvage-signal 'https://salvagesignal.com/api/mcp'
{
"mcpServers": {
"com-salvagesignal-salvage-signal": {
"url": "https://salvagesignal.com/api/mcp"
}
}
} {
"servers": {
"com-salvagesignal-salvage-signal": {
"type": "http",
"url": "https://salvagesignal.com/api/mcp"
}
}
} [mcp_servers.com-salvagesignal-salvage-signal] url = "https://salvagesignal.com/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-salvagesignal-salvage-signal": {
"type": "remote",
"url": "https://salvagesignal.com/api/mcp",
"enabled": true
}
}
} openclaw mcp add com-salvagesignal-salvage-signal --url 'https://salvagesignal.com/api/mcp' --transport streamable-http
mcp_servers:
com-salvagesignal-salvage-signal:
url: "https://salvagesignal.com/api/mcp" {
"McpServers": {
"com-salvagesignal-salvage-signal": {
"Transport": "http",
"Url": "https://salvagesignal.com/api/mcp"
}
}
} assistant mcp add com-salvagesignal-salvage-signal -t streamable-http -u 'https://salvagesignal.com/api/mcp'
{
"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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 +1
- Stability: 0.97 → pass security
- 23 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 0
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Probed https://salvagesignal.com/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=salvagesignal.com | CN=YE1,O=Let's Encrypt,C=US | 17 Sept 2026 | 16 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 6f486e61595f525be2225d2d3c147c1223d |
| SANs: salvagesignal.com, www.salvagesignal.com | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of salvagesignal.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| salvagesignal.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000 |
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://salvagesignal.com/api/mcp | Verified | 200 | |
| http (plaintext) | http://salvagesignal.com/api/mcp | HTTPS enforced | 301 | https://salvagesignal.com/api/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_chicago_reuse_brief Get the Chicago Teardown-to-Reuse Brief ~58
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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| dataMode | string | yes | – |
| market | string | yes | – |
| name | string | yes | – |
| safety | string | yes | – |
| source | object | yes | – |
| summary | object | yes | – |
| watchList | array | yes | – |
No examples provided.
get_salvage_signal_offer Get Salvage Signal product and pricing facts ~64
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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| dailyDrop | object | yes | – |
| description | string | yes | – |
| name | string | yes | – |
| safety | string | yes | – |
| source | object | yes | – |
| url | string | yes | – |
No examples provided.
get_subscription_handoff Get a human-confirmed subscription handoff ~103
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.
| Name | Type | Req | Description |
|---|---|---|---|
| campaign | string | – | Short campaign identifier used only for signup attribution. |
| source | string | – | Short agent or channel identifier used only for signup attribution. |
| Name | Type | Req | Description |
|---|---|---|---|
| agentPolicy | object | yes | – |
| humanDecision | object | yes | – |
| links | object | yes | – |
| pricing | object | yes | – |
| product | object | yes | – |
| readOnly | boolean | yes | – |
| schemaVersion | string | yes | – |
| status | string | yes | – |
| type | string | yes | – |
No examples provided.
search_salvage_signals Search Chicago salvage signals ~111
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum number of ranked signals to return. |
| material | string | – | Material or building-characteristic filter. |
| urgency | string | – | Salvage Signal urgency band. |
| Name | Type | Req | Description |
|---|---|---|---|
| dataMode | string | yes | – |
| market | string | yes | – |
| safety | string | yes | – |
| signalCount | integer | yes | – |
| signals | array | yes | – |
| source | object | yes | – |
No examples provided.
What is the Chicago Demolition Leads | Salvage Signal MCP server?
Chicago Demolition Leads | Salvage Signal is an MCP server listed in the public MCP registry as com.salvagesignal/salvage-signal. Chicago demolition and reclaimed-brick leads, pricing, and a human-confirmed Daily Drop handoff. This page covers its hosted endpoint (https://salvagesignal.com/api/mcp).
Is the Chicago Demolition Leads | Salvage Signal MCP server safe to use?
Chicago Demolition Leads | Salvage Signal scores 88 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Chicago Demolition Leads | Salvage Signal MCP server expose?
Chicago Demolition Leads | Salvage Signal exposes 4 tools: search_salvage_signals, get_chicago_reuse_brief, get_salvage_signal_offer, get_subscription_handoff. Their descriptions and schemas cost roughly 336 tokens of context every time the server is loaded.
Does the Chicago Demolition Leads | Salvage Signal MCP server require authentication?
No. We connected to Chicago Demolition Leads | Salvage Signal without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Chicago Demolition Leads | Salvage Signal MCP server still maintained?
Chicago Demolition Leads | Salvage Signal is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.