# com.blackwalltier/blackwall (npm · blackwall-mcp)

Pre-action risk gate: AI agents call before any irreversible action (money, SQL, delete).

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

## Components

- npm · `blackwall-mcp`: 67/100 (this document), [markdown](https://verifymcp.io/servers/com-blackwalltier-blackwall/blackwall-mcp.md), [page](https://verifymcp.io/servers/com-blackwalltier-blackwall/blackwall-mcp)

## Channel facts

- Registry: `npm`
- Package: `blackwall-mcp`
- Version: `1.4.1`
- 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-08-03.

- **Supply Chain Security**: 87/100
  - No malware found by supply-chain analysis.
  - Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree.
  - No install/post-install scripts declared.
  - Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree.
- **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 63 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 63/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 575 tokens (~287/item across 2 items; 2 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**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add com-blackwalltier-blackwall -- npx -y blackwall-mcp
```

### Codex

```bash
codex mcp add com-blackwalltier-blackwall -- npx -y blackwall-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-blackwalltier-blackwall": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "blackwall-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-blackwalltier-blackwall --command npx --arg -y --arg blackwall-mcp
```

### Hermes

```yaml
mcp_servers:
  com-blackwalltier-blackwall:
    command: "npx"
    args: ["-y", "blackwall-mcp"]
```

### Other

```json
{
  "mcpServers": {
    "com-blackwalltier-blackwall": {
      "command": "npx",
      "args": [
        "-y",
        "blackwall-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-08-03 (score 67, +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-02 (score 66, +15)

- [security regression] Known CVEs: partial → unverified
- [security improvement] Malware scan: unverified → pass
- [security] Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet.
- [functional regression] Dependency health: partial → unverified
- [functional regression] Security disclosure: fail → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional regression] Capabilities: pass → unverified
- [functional improvement] Stability: unverified → 0.23

### 2026-08-01 (score 51, +33)

- [security regression] Provenance: unverified → fail
- [security improvement] Install scripts: unverified → pass
- [security improvement] Known CVEs: unverified → partial
- [security] Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window).
- [functional improvement] Maintenance: unverified → pass
- [functional improvement] Schema quality: unverified → excellent
- [functional improvement] License: unverified → pass
- [functional improvement] Dependency health: unverified → partial
- [functional improvement] MCP protocol: unverified → pass
- [functional] Licence: MIT

### 2026-07-31 (score 18, −25)

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

### 2026-07-30 (score 43, +19)

- [functional improvement] Tool coverage: unverified → 100

### 2026-07-28 (score 24, −19)

- [functional regression] Tool coverage: 100 → unverified
- [functional] First check of Schema quality: unverified

### 2026-07-27 (score 43)

First indexed and scored.

## MCP tools (2)

### `forecast` (~244 tokens)

BLACK_WALL pre-action risk check

Call this BEFORE taking ANY irreversible or high-stakes action — sending an email, making a payment, running SQL, deleting files or data, posting public content, calling an external API that changes state. It returns a risk score (0–100), a recommendation (GO / CAUTION / STOP), and named red flags. If the recommendation is STOP, do not take the action — surface the flags to the user instead. If CAUTION, confirm with the user first.

Input parameters:

- `action` (string, required): The action about to be taken, e.g. 'send_email', 'make_payment', 'run_sql', 'delete_file', 'delete_database', 'post_content', 'api_call'.
- `context` (object): Optional situational context: { agent_role, user_intent, environment } — helps the model judge whether the action fits the intent.
- `depth` (string): Analysis depth. 'standard' (default) or 'deep' (more thorough, costs more).
- `inputs` (object, required): The concrete parameters of the action: recipient, amount_usd, SQL statement, file path, message body, URL, etc. Include everything relevant to judging risk.

### `observe` (~331 tokens)

BLACK_WALL post-action observation

Call this AFTER an action runs (or after deciding NOT to run it because BLACK_WALL returned STOP/HUMAN_REQUIRED) to report what actually happened. Closes the loop with the earlier forecast — BLACK_WALL compares your observation to the prediction to track accuracy and improve future forecasts. FREE — no tokens charged. Always call this if you have a forecast_id from a recent `forecast` call.

Input parameters:

- `actual_targets` (array): IDs / paths / hashes of what was actually affected (e.g. user_ids, file paths, transaction hashes, row counts as strings). Helps reconstruct the event later.
- `details` (string): Free-form details: what actually happened, error messages, observed side effects, anything that helps trace the event back later.
- `divergence_severity` (string): How bad the divergence was. Use 'none' for 'matched' or 'aborted' outcomes.
- `forecast_id` (string, required): The id returned by the matching `forecast` call (the top-level `id` field in that response). Required.
- `outcome_class` (string): How the actual outcome compared to the prediction. 'matched' = exactly as predicted. 'over_scope' = affected MORE than predicted (e.g. DELETE hit 1247 rows when 1 was expected). 'under_scope' = affec…

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/com-blackwalltier-blackwall/blackwall-mcp#diagnostics

## Score history

- 2026-08-03: 67
- 2026-08-02: 66
- 2026-08-01: 51
- 2026-07-31: 18
- 2026-07-30: 43
- 2026-07-28: 24
- 2026-07-27: 43

## Links

- npm package: https://www.npmjs.com/package/blackwall-mcp
- Socket report: https://socket.dev/npm/package/blackwall-mcp
- Repository: https://github.com/bluetieroperations-create/blackwall-mcp
- Website: https://blackwalltier.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-blackwalltier-blackwall/blackwall-mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-blackwalltier-blackwall/blackwall-mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/com-blackwalltier-blackwall/blackwall-mcp