distress-abc MCP server
com.dropwatchhq/distress-abcdropwatchhq.comstreamable-httpv1.0.0Scanned
ABC/receivership wind-down asset maps: state notices joined to UCC collateral & secured parties.
5 tools: 4 change things and 1 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
4 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the distress-abc MCP server can do
The distress-abc MCP server is published by dropwatchhq.com, a domain the MCP Registry verified. It has 5 tools. It can create or change data (4 tools: abc_distress_feed, warn_plant_deaths, warn_liquidation_map and abc_asset_map), but cannot delete data. 1 tool only reads.
None of its tools reads private data, brings in text other people write, or sends data out.
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 17, 2026, version 1.0.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
5 tools
Changes things 4Claude Code: ask
abc_asset_mapBuild the full WIND-DOWN ASSET / COLLATERAL MAP for one ABC/receivership case.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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.]
abc_distress_feedFREE: live feed of state ASSIGNMENT-FOR-BENEFIT-OF-CREDITORS (ABC) and RECEIVERSHIP public legal notices — the wind-down firehose with NO PACER.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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.
warn_liquidation_mapBuild the LIQUIDATOR-facing ASSET / COLLATERAL MAP for a WARN-Act plant-death entity (the failing employer).No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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.]
warn_plant_deathsFREE: recent WARN-Act PLANT-DEATH events (mass layoffs / plant closures) — the SECOND distress-event lane feeding the same liquidation map.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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.
Only reads 1Show 1 read-only tool
abc_find_noticesFREE: keyword-search the wind-down legal-notice archive (e.g.No findings
Why it is in this group
- The name "abc_find_notices" says "find": a word for reading.
Description, as the server wrote it 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.
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:25 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 4
- Protocol version
- 2024-11-05
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 4 tools that change things (4 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://abc.dropwatchhq.com/mcp: tools/list returned 5 tools to an anonymous client, including abc_distress_feed (write), warn_plant_deaths (write), warn_liquidation_map (write), abc_asset_map (write)
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http distress-abc https://abc.dropwatchhq.com/mcpclaude mcp add --transport http distress-abc https://abc.dropwatchhq.com/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__distress-abc__abc_find_notices"
],
"ask": [
"mcp__distress-abc__abc_distress_feed",
"mcp__distress-abc__warn_plant_deaths",
"mcp__distress-abc__warn_liquidation_map",
"mcp__distress-abc__abc_asset_map"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as distress-abc. Review it before you use it.
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/com.dropwatchhq/distress-abc/verify?hash=8f6e68f6d13b4c73af56c652d874f672ffe5c9679718a8ce81e391d10549410d" | jq -e '.changed == false'Pinned hash 8f6e68f6d13b, from Nov 17, 2026, 10:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.dropwatchhq/distress-abc/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.dropwatchhq/distress-abc)Source: MCP Registry. Synced Oct 21, 2026, 17:54 UTC.
distress-abc MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the distress-abc MCP server safe?
- No scan can promise that. What its definitions show: 5 tools, 4 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the distress-abc MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the distress-abc MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the distress-abc MCP server have?
- 5 tools: 4 write, 1 read. abc_distress_feed, warn_plant_deaths, warn_liquidation_map, abc_asset_map and abc_find_notices.
Does the distress-abc MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the distress-abc MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the distress-abc MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 17, 2026.