# com.dropwatchhq/distress-abc (remote · abc.dropwatchhq.com)

ABC/receivership wind-down asset maps: state notices joined to UCC collateral & secured parties.

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

## Components

- remote · `abc.dropwatchhq.com`: 51/100 (this document), [markdown](https://verifymcp.io/servers/com-dropwatchhq-distress-abc/abc.md), [page](https://verifymcp.io/servers/com-dropwatchhq-distress-abc/abc)

## Channel facts

- Endpoint: `https://abc.dropwatchhq.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.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**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS check failed: the endpoint is reachable over plaintext HTTP.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - 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**: 36/100
  - AI-judged instruction clarity (poor).
  - Context-footprint check failed: tool/resource definitions use about 905 tokens (~181/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params.
  - 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.
- **Capabilities**: 20/100
  - Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http com-dropwatchhq-distress-abc https://abc.dropwatchhq.com/mcp
```

### Codex

```toml
[mcp_servers.com-dropwatchhq-distress-abc]
url = "https://abc.dropwatchhq.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-dropwatchhq-distress-abc": {
      "type": "remote",
      "url": "https://abc.dropwatchhq.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-dropwatchhq-distress-abc --url https://abc.dropwatchhq.com/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-dropwatchhq-distress-abc:
    url: "https://abc.dropwatchhq.com/mcp"
```

### Other

```json
{
  "mcpServers": {
    "com-dropwatchhq-distress-abc": {
      "type": "http",
      "url": "https://abc.dropwatchhq.com/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-03 (score 51, +1)

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

### 2026-08-01 (score 50, +1)

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

### 2026-07-31 (score 49, 0)

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

### 2026-07-30 (score 49, 0)

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

### 2026-07-29 (score 49, +1)

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

### 2026-07-28 (score 48, +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 47, 0)

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

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

First indexed and scored.

## MCP tools (5)

### `abc_distress_feed` (~144 tokens)

FREE: live feed of state ASSIGNMENT-FOR-BENEFIT-OF-CREDITORS (ABC) and RECEIVERSHIP public legal notices — the wind-down firehose with NO PACER. Each notice: type (receivership/abc/asset-auction/lien-foreclosure), the assignor/distressed entity where parseable, case number, claim/sale date, and link. Beachhead state: WA (a notice-publishing state); FL/NY/DE link-out, CA/TX are dark. Wind-downs move fast — this is the clock.

Input parameters:

- `limit` (number): Max notices to return (default 40).

### `abc_find_notices` (~83 tokens)

FREE: keyword-search the wind-down legal-notice archive (e.g. 'receivership', 'assignment for benefit of creditors', 'assignee', a company name). Returns matching notice headers + links you can feed into abc_asset_map.

Input parameters:

- `keyword` (string, required): Search term (required).
- `limit` (number): Max results (default 15).

### `warn_plant_deaths` (~151 tokens)

FREE: recent WARN-Act PLANT-DEATH events (mass layoffs / plant closures) — the SECOND distress-event lane feeding the same liquidation map. Each is a failing employer the day its plant is dying, with whether it has a live Colorado UCC collateral map (so a liquidator can triage which dying plant has filed collateral worth chasing). Live keyless index = CA EDD detailed WARN report; the CO UCC join is the collateral overlay (honest null where the firm's collateral is in a state not yet covered keyless). Feed an employer into warn_liquidation_map for the full collateral inventory.

Input parameters:

- `limit` (number): Max plant-death events (default 25).

### `warn_liquidation_map` (~284 tokens)

Build the LIQUIDATOR-facing ASSET / COLLATERAL MAP for a WARN-Act plant-death entity (the failing employer). Joins that entity to FREE-STATE UCC-encumbered collateral + secured parties (Colorado SOS, live keyless) + the county-recorder real-property lookout, and returns the encumbered-collateral inventory + liquidator/auctioneer/assignee actions. Buyers: distressed-asset liquidators, auctioneers, and the assignee running the wind-down — they NEED the collateral map to know what can sell free vs. what's locked by a perfected lien. Pass an `entity` (employer name) for the full map, or omit it for the recent plant-death TRIAGE feed (each with a CO-UCC collateral count). HONEST: WARN index is CA, UCC join is CO — a CA plant-death maps to CO collateral only for multi-state operators (honest null otherwise). Hand-verifiable at this volume; verify before bidding. [x402: full map settles $0.50 USDC on Base mainnet, keyless; free preview included.]

Input parameters:

- `entity` (string): Failing employer / plant-death entity name (omit for the triage feed).
- `limit` (number): Triage-feed size when no entity (default 12).

### `abc_asset_map` (~243 tokens)

Build the full WIND-DOWN ASSET / COLLATERAL MAP for one ABC/receivership case. Pass the notice `link` (from abc_distress_feed/abc_find_notices) and/or the assignor `entity` name. Joins the failing entity to FREE-STATE UCC-encumbered collateral + secured parties (Colorado SOS, live keyless) and the county-recorder real-property lookout, then returns the collateral inventory + buyer actions per role (assignee/liquidator, distressed-asset/IP buyer, creditor). The map the assignee needs to actually run the wind-down — and the map a buyer needs to bid first. Multi-hop parse is hand-verifiable; verify before acting. [x402: full map settles $0.50 USDC on Base mainnet, keyless; free preview included.]

Input parameters:

- `entity` (string): Assignor / distressed entity name (use if no link, or to override the parse).
- `link` (string): Notice page URL (preferred — we parse the assignor + case).
- `state` (string): US state 2-letter code (record header / recorder lookout).

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-dropwatchhq-distress-abc/abc#diagnostics

## Score history

- 2026-08-03: 51
- 2026-08-02: 50
- 2026-08-01: 50
- 2026-07-31: 49
- 2026-07-30: 49
- 2026-07-29: 49
- 2026-07-28: 48
- 2026-07-27: 47
- 2026-07-26: 47

## Links

- Remote endpoint: https://abc.dropwatchhq.com/mcp
- Website: https://abc.dropwatchhq.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-dropwatchhq-distress-abc/abc/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-dropwatchhq-distress-abc/abc/changelog.json
- HTML version of this page: https://verifymcp.io/servers/com-dropwatchhq-distress-abc/abc