Bulwark
OCI · GHCR.IO/BPOLANIA/BULWARK:V0.2.0
AI agent governance: content scanning, audit logs, policy evaluation, session management.
Available components
Last scanned (6 hours ago)
Scores higher than 45% of OCI servers
Category Security
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 Security0
- 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.Unverified
- Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
Provenance & Transparency9
- Repository check failed: the declared repository URL redirects; it must resolve directly. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- License check failed: no license is declared. See how to fix → Fail
- Actively maintained (last published 253 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability75
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 357 tokens (~51/item across 7 items; 7 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management80
- Stability observed for 24 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 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
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.
Checks we ran (12)
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (4)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Malware scan in Supply Chain Security (scores 0 for this)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 in Supply Chain Security (scores 0 for this)Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
- Install scripts in Supply Chain Security (scores 0 for this)Install-script risk not yet assessed.
- Dependency health in Supply Chain Security (scores 0 for this)Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 6 Nov 26 −3
- Stability: pass → 0.80 functional
- 25 Oct 26 0
- Stability: 0.97 → pass security
- 24 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Oct 26 0
- Provenance: unverified → fail ▼ security
- 18 Oct 26 +1
- Provenance: fail → unverified ▼ security
- 16 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 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 6 Nov 2026 · Analysed oci/ghcr.io/bpolania/bulwark:v0.2.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | oci |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
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 →
bulwark__audit_search ~110
Search audit events with filters
| Name | Type | Req | Description |
|---|---|---|---|
| event_type | string | – | Filter by event type (e.g. request_processed, policy_decision) |
| limit | integer | – | Max results (default 50) |
| operator | string | – | Filter by operator name |
| outcome | string | – | Filter by outcome (e.g. success, denied, failed) |
| session_id | string | – | Filter by session ID |
| tool | string | – | Filter by tool name (supports * wildcard) |
No output schema declared.
No examples provided.
bulwark__audit_stats ~32
Show aggregate audit statistics
| Name | Type | Req | Description |
|---|---|---|---|
| since_hours | integer | – | Show stats for the last N hours |
No output schema declared.
No examples provided.
bulwark__audit_tail ~35
Show the most recent audit events
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | – | Number of events to return (default 20) |
No output schema declared.
No examples provided.
bulwark__audit_verify ~20
Verify integrity of the audit hash chain
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
bulwark__policy_evaluate ~90
Evaluate policy rules for a given tool and action
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | Action to evaluate |
| agent_type | string | – | Agent type |
| environment | string | – | Environment scope |
| operator | string | – | Operator name |
| project | string | – | Project scope |
| team | string | – | Team scope |
| tool | string | yes | Tool name to evaluate |
No output schema declared.
No examples provided.
bulwark__scan_content ~36
Scan text for secrets, PII, and prompt injection patterns
| Name | Type | Req | Description |
|---|---|---|---|
| text | string | yes | Text content to scan |
No output schema declared.
No examples provided.
bulwark__session_list ~34
List active sessions in the vault
| Name | Type | Req | Description |
|---|---|---|---|
| include_revoked | boolean | – | Include revoked sessions (default false) |
No output schema declared.
No examples provided.
How do I install the Bulwark MCP server?
Bulwark runs locally as a container image, launched with docker run --rm -i -e BULWARK_CONFIG -e BULWARK_SESSION_TOKEN ghcr.io/bpolania/bulwark:v0.2.0 mcp start. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.
oci · ghcr.io/bpolania/bulwark:v0.2.0
claude mcp add bpolania-bulwark -- docker run --rm -i -e BULWARK_CONFIG -e BULWARK_SESSION_TOKEN ghcr.io/bpolania/bulwark:v0.2.0 mcp start
This image reads BULWARK_CONFIG and BULWARK_SESSION_TOKEN. Set them in your client's env block for this server; docker run -e passes each one through to the container.
What is the Bulwark MCP server?
Bulwark is an MCP server listed in the public MCP registry as io.github.bpolania/bulwark. AI agent governance: content scanning, audit logs, policy evaluation, session management. This page covers its container image (ghcr.io/bpolania/bulwark:v0.2.0).
Is the Bulwark MCP server safe to use?
Bulwark scores 41 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 Bulwark MCP server expose?
Bulwark exposes 7 tools: bulwark__scan_content, bulwark__audit_search, bulwark__audit_tail, bulwark__audit_stats, bulwark__audit_verify, and 2 more. Their descriptions and schemas cost roughly 357 tokens of context every time the server is loaded.
Is the Bulwark MCP server still maintained?
Bulwark is still listed as active in the MCP registry. We last reached this channel on 6 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Bulwark MCP server?
VerifyMCP ran 12 checks on Bulwark, 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 Bulwark: 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.