com.blackwalltier/blackwall
NPM · BLACKWALL-MCP · SCANNED AUG 3
Pre-action risk gate: AI agents call before any irreversible action (money, SQL, delete).
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 →
Supply Chain Security87
- No malware found by supply-chain analysis.Pass
- Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree. 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 63 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 Management27
- Stability observed for 8 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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · blackwall-mcp
claude mcp add com-blackwalltier-blackwall -- npx -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": {
"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.
- 3 Aug 26 +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.
- 2 Aug 26 +15
- Known CVEs: partial → unverified ▼ security
- 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. security
- Dependency health: partial → unverified ▼ functional
- Security disclosure: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Stability: unverified → 0.23 ▲ functional
- 1 Aug 26 +33
- Provenance: unverified → fail ▼ security
- Install scripts: unverified → pass ▲ security
- Known CVEs: unverified → partial ▲ security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- Maintenance: unverified → pass ▲ functional
- Schema quality: unverified → excellent ▲ functional
- License: unverified → pass ▲ functional
- Dependency health: unverified → partial ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Licence: MIT functional
- 31 Jul 26 −25
- 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 +19
- Tool coverage: unverified → 100 ▲ functional
- 28 Jul 26 −19
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 27 Jul 26 43
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 3 Aug 2026 · Analysed npm/[email protected]
Provenance none
Ecosystem: npm · Outcome: none
Dependencies 95 packages
95 packages in the resolved dependency tree · 95 deprecated · 29 stale.
The dependency tree was only partially resolved, so these counts may be incomplete.
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.
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.