# io.github.CloudCorpRecords/noticewire (oci · ghcr.io/cloudcorprecords/noticewire)

ABC and receivership legal-notice feed, notice archive search and WARN plant-closure events.

- Trust score: 43/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- npm · `@reneturcios/noticewire`: 72/100, [markdown](https://verifymcp.io/servers/cloudcorprecords-noticewire/reneturcios-noticewire.md), [page](https://verifymcp.io/servers/cloudcorprecords-noticewire/reneturcios-noticewire)
- oci · `ghcr.io/cloudcorprecords/noticewire`: 43/100 (this document), [markdown](https://verifymcp.io/servers/cloudcorprecords-noticewire/ghcr-io-cloudcorprecords-noticewire.md), [page](https://verifymcp.io/servers/cloudcorprecords-noticewire/ghcr-io-cloudcorprecords-noticewire)

## Channel facts

- Registry: `oci`
- Package: `ghcr.io/cloudcorprecords/noticewire`
- Version: `0.1.0`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, 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-11-21.

- **Supply Chain Security**: 0/100
  - No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.
  - Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
  - Install-script risk not yet assessed.
  - Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 4 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 76/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 378 tokens (~126/item across 3 items; 3 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 17/100
  - Stability observed for 5 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.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

**Unverified: 1 category.** A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

## Install

### How do I install the io.github.CloudCorpRecords/noticewire MCP server?

io.github.CloudCorpRecords/noticewire runs locally as a container image, launched with docker run --rm -i ghcr.io/cloudcorprecords/noticewire:0.1.0 mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add cloudcorprecords-noticewire -- docker run --rm -i ghcr.io/cloudcorprecords/noticewire:0.1.0 mcp
```

### Cursor

```json
{
  "mcpServers": {
    "cloudcorprecords-noticewire": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/cloudcorprecords/noticewire:0.1.0",
        "mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "cloudcorprecords-noticewire": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/cloudcorprecords/noticewire:0.1.0",
        "mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add cloudcorprecords-noticewire -- docker run --rm -i ghcr.io/cloudcorprecords/noticewire:0.1.0 mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "cloudcorprecords-noticewire": {
      "type": "local",
      "command": [
        "docker",
        "run",
        "--rm",
        "-i",
        "ghcr.io/cloudcorprecords/noticewire:0.1.0",
        "mcp"
      ],
      "enabled": true
    }
  }
}
```

### Hermes

```yaml
mcp_servers:
  cloudcorprecords-noticewire:
    command: "docker"
    args: ["run", "--rm", "-i", "ghcr.io/cloudcorprecords/noticewire:0.1.0", "mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "cloudcorprecords-noticewire": {
      "Transport": "stdio",
      "Command": "docker",
      "Arguments": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/cloudcorprecords/noticewire:0.1.0",
        "mcp"
      ]
    }
  }
}
```

### Other

```json
{
  "mcpServers": {
    "cloudcorprecords-noticewire": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/cloudcorprecords/noticewire:0.1.0",
        "mcp"
      ]
    }
  }
}
```

## 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-11-20 (score 43, +1)

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

### 2026-11-18 (score 42, +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-11-16 (score 41)

First indexed and scored.

## MCP tools (3)

### `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).

## Diagnostics

Captured diagnostic sections: Provenance. The full working is on the page: https://verifymcp.io/servers/cloudcorprecords-noticewire/ghcr-io-cloudcorprecords-noticewire#diagnostics

## Score history

- 2026-11-21: 43
- 2026-11-20: 43
- 2026-11-19: 42
- 2026-11-18: 42
- 2026-11-17: 41
- 2026-11-16: 41

## Common questions

### What is the io.github.CloudCorpRecords/noticewire MCP server?

io.github.CloudCorpRecords/noticewire is an MCP server listed in the public MCP registry as io.github.CloudCorpRecords/noticewire. ABC and receivership legal-notice feed, notice archive search and WARN plant-closure events. This page covers its container image (ghcr.io/cloudcorprecords/noticewire).

### Is the io.github.CloudCorpRecords/noticewire MCP server safe to use?

io.github.CloudCorpRecords/noticewire scores 43 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 io.github.CloudCorpRecords/noticewire MCP server expose?

io.github.CloudCorpRecords/noticewire exposes 3 tools: abc_distress_feed, abc_find_notices, warn_plant_deaths. Their descriptions and schemas cost roughly 378 tokens of context every time the server is loaded.

### Is the io.github.CloudCorpRecords/noticewire MCP server still maintained?

io.github.CloudCorpRecords/noticewire is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the io.github.CloudCorpRecords/noticewire MCP server under?

io.github.CloudCorpRecords/noticewire declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

### What did VerifyMCP test on the io.github.CloudCorpRecords/noticewire MCP server?

VerifyMCP ran 12 checks on io.github.CloudCorpRecords/noticewire, covering Source repository, Provenance, License, Maintenance and 8 more. 4 items could not be completed, a gap on our side rather than a finding about io.github.CloudCorpRecords/noticewire: Malware scan, Known CVEs, Install scripts and Dependency health. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to a container image, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- GitHub Container Registry: https://ghcr.io/cloudcorprecords/noticewire
- Repository: https://github.com/CloudCorpRecords/noticewire
- Changelog RSS feed: https://verifymcp.io/servers/cloudcorprecords-noticewire/ghcr-io-cloudcorprecords-noticewire.xml
- Changelog JSON feed: https://verifymcp.io/servers/cloudcorprecords-noticewire/ghcr-io-cloudcorprecords-noticewire/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/cloudcorprecords-noticewire/ghcr-io-cloudcorprecords-noticewire.json
- HTML version of this page: https://verifymcp.io/servers/cloudcorprecords-noticewire/ghcr-io-cloudcorprecords-noticewire
