com.dropwatchhq/distress-abc
REMOTE · ABC.DROPWATCHHQ.COM · SCANNED SEP 21
ABC/receivership wind-down asset maps: state notices joined to UCC collateral & secured parties.
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 Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- HTTPS check failed: the endpoint is reachable over plaintext HTTP. See how to fix → View diagnostics → Fail
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- 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 Usability67
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- 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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 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
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
How do I install the com.dropwatchhq/distress-abc MCP server?
com.dropwatchhq/distress-abc is a hosted endpoint at https://abc.dropwatchhq.com/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 · abc.dropwatchhq.com
claude mcp add --transport http com-dropwatchhq-distress-abc 'https://abc.dropwatchhq.com/mcp'
{
"mcpServers": {
"com-dropwatchhq-distress-abc": {
"url": "https://abc.dropwatchhq.com/mcp"
}
}
} {
"servers": {
"com-dropwatchhq-distress-abc": {
"type": "http",
"url": "https://abc.dropwatchhq.com/mcp"
}
}
} [mcp_servers.com-dropwatchhq-distress-abc] url = "https://abc.dropwatchhq.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-dropwatchhq-distress-abc": {
"type": "remote",
"url": "https://abc.dropwatchhq.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-dropwatchhq-distress-abc --url 'https://abc.dropwatchhq.com/mcp' --transport streamable-http
mcp_servers:
com-dropwatchhq-distress-abc:
url: "https://abc.dropwatchhq.com/mcp" {
"McpServers": {
"com-dropwatchhq-distress-abc": {
"Transport": "http",
"Url": "https://abc.dropwatchhq.com/mcp"
}
}
} assistant mcp add com-dropwatchhq-distress-abc -t streamable-http -u 'https://abc.dropwatchhq.com/mcp'
{
"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.
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 +1
- 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
- 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 21 Sept 2026 · Probed https://abc.dropwatchhq.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=dropwatchhq.com | CN=WE1,O=Google Trust Services,C=US | 20 Aug 2026 | 18 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 5e5bbf18531cc5cd0eeb2e436233f89d |
| SANs: dropwatchhq.com, abc.dropwatchhq.com, *.abc.dropwatchhq.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of abc.dropwatchhq.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| dropwatchhq.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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://abc.dropwatchhq.com/mcp | Verified | 200 | |
| http (plaintext) | http://abc.dropwatchhq.com/mcp | Served over HTTP | 200 |
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 →
abc_asset_map ~243
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.]
| Name | Type | Req | Description |
|---|---|---|---|
| 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). |
No output schema declared.
No examples provided.
abc_distress_feed ~144
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max notices to return (default 40). |
No output schema declared.
No examples provided.
abc_find_notices ~83
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.
| Name | Type | Req | Description |
|---|---|---|---|
| keyword | string | yes | Search term (required). |
| limit | number | – | Max results (default 15). |
No output schema declared.
No examples provided.
warn_liquidation_map ~284
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.]
| Name | Type | Req | Description |
|---|---|---|---|
| entity | string | – | Failing employer / plant-death entity name (omit for the triage feed). |
| limit | number | – | Triage-feed size when no entity (default 12). |
No output schema declared.
No examples provided.
warn_plant_deaths ~151
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max plant-death events (default 25). |
No output schema declared.
No examples provided.
What is the com.dropwatchhq/distress-abc MCP server?
com.dropwatchhq/distress-abc is an MCP server listed in the public MCP registry as com.dropwatchhq/distress-abc. ABC/receivership wind-down asset maps: state notices joined to UCC collateral & secured parties. This page covers its hosted endpoint (https://abc.dropwatchhq.com/mcp).
Is the com.dropwatchhq/distress-abc MCP server safe to use?
com.dropwatchhq/distress-abc scores 69 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 com.dropwatchhq/distress-abc MCP server expose?
com.dropwatchhq/distress-abc exposes 5 tools: abc_distress_feed, abc_find_notices, warn_plant_deaths, warn_liquidation_map, abc_asset_map. Their descriptions and schemas cost roughly 905 tokens of context every time the server is loaded.
Does the com.dropwatchhq/distress-abc MCP server require authentication?
No. We connected to com.dropwatchhq/distress-abc without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the com.dropwatchhq/distress-abc MCP server still maintained?
com.dropwatchhq/distress-abc is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.