com.blackwalltier/blackwall
NPM · BLACKWALL-MCP · SCANNED OCT 1
API-key pre-action risk gate: any irreversible agent action (money, SQL, delete, email).
Available components
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. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 33 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability63
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
- Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the com.blackwalltier/blackwall MCP server?
com.blackwalltier/blackwall runs locally as an npm package, launched with npx -y blackwall-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · blackwall-mcp
claude mcp add com-blackwalltier-blackwall -- npx -y blackwall-mcp
{
"mcpServers": {
"com-blackwalltier-blackwall": {
"command": "npx",
"args": [
"-y",
"blackwall-mcp"
]
}
}
} {
"servers": {
"com-blackwalltier-blackwall": {
"command": "npx",
"args": [
"-y",
"blackwall-mcp"
]
}
}
} codex mcp add com-blackwalltier-blackwall -- npx -y blackwall-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-blackwalltier-blackwall": {
"type": "local",
"command": [
"npx",
"-y",
"blackwall-mcp"
],
"enabled": true
}
}
} openclaw mcp add com-blackwalltier-blackwall --command npx --arg -y --arg blackwall-mcp
mcp_servers:
com-blackwalltier-blackwall:
command: "npx"
args: ["-y", "blackwall-mcp"] {
"McpServers": {
"com-blackwalltier-blackwall": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"blackwall-mcp"
]
}
}
} assistant mcp add com-blackwalltier-blackwall -t stdio -c npx -a -y blackwall-mcp
{
"mcpServers": {
"com-blackwalltier-blackwall": {
"command": "npx",
"args": [
"-y",
"blackwall-mcp"
]
}
}
} 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.
- 30 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Sept 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 Sept 26 −3
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 +1
- Stability: 0.97 → pass security
- 22 Sept 26 −1
- Stability: pass → 0.93 functional
- Package version: 1.4.1 → 1.4.2 functional
- 21 Sept 26 +1
- Stability: 0.97 → pass security
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
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 1 Oct 2026 · Analysed npm/blackwall-mcp@1.4.2
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 93 packages
| Packages resolved | 93 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
forecast BLACK_WALL pre-action risk check ~244
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.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | 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 | yes | The concrete parameters of the action: recipient, amount_usd, SQL statement, file path, message body, URL, etc. Include everything relevant to judging risk. |
No output schema declared.
No examples provided.
observe BLACK_WALL post-action observation ~331
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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… |
No output schema declared.
No examples provided.
What is the com.blackwalltier/blackwall MCP server?
com.blackwalltier/blackwall is an MCP server listed in the public MCP registry as com.blackwalltier/blackwall. API-key pre-action risk gate: any irreversible agent action (money, SQL, delete, email). This page covers its npm package (blackwall-mcp).
Is the com.blackwalltier/blackwall MCP server safe to use?
com.blackwalltier/blackwall scores 81 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 1 October 2026. It declares no install or post-install scripts. 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.blackwalltier/blackwall MCP server expose?
com.blackwalltier/blackwall exposes 2 tools: forecast, observe. Their descriptions and schemas cost roughly 575 tokens of context every time the server is loaded.
Is the com.blackwalltier/blackwall MCP server still maintained?
com.blackwalltier/blackwall is still listed as active in the MCP registry. We last reached this channel on 1 October 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 com.blackwalltier/blackwall MCP server under?
com.blackwalltier/blackwall declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.