# DeadBolt by NextEleven (mcpb · deadbolt-2.0.1.mcpb)

Local execution gate: fixed deadlines, operator-only controls, read-only setup and readable denials.

- Trust score: 48/100 (low)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- mcpb · `deadbolt-2.0.1.mcpb`: 48/100 (this document), [markdown](https://verifymcp.io/servers/seanebones-lang-deadbolt/deadbolt.md), [page](https://verifymcp.io/servers/seanebones-lang-deadbolt/deadbolt)

## Channel facts

- Registry: `mcpb`
- Package: `https://github.com/seanebones-lang/deadbolt/releases/download/mcpb-v2.0.1/deadbolt-2.0.1.mcpb`
- Transport: `stdio`
- SHA-256: `709bd27afe9c1ce8a833d124eceb2e6ca6458a40924534a34882b253fe4ae644`

## 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-05.

- **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: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).
  - Install-script risk not yet assessed.
  - Dependency health could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).
- **Provenance & Transparency**: 48/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (Apache-2.0).
  - Actively maintained (last published 1 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 68/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 214 tokens (~107/item across 2 items; 2 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 73/100
  - Stability observed for 22 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.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 2 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**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; 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 DeadBolt by NextEleven MCP server?

DeadBolt by NextEleven ships as an MCPB bundle, a single file you download and open in an MCP host that supports MCPB bundles, such as Claude Desktop. The host reads the launch command from the bundle's own manifest, so there is no command to copy. Before opening it, check the file's SHA-256 matches the one the MCP registry declares for it, 709bd27afe9c1ce8a833d124eceb2e6ca6458a40924534a34882b253fe4ae644; the commands to do that are on this page. If it does not match, do not open it.

- Download bundle: `https://github.com/seanebones-lang/deadbolt/releases/download/mcpb-v2.0.1/deadbolt-2.0.1.mcpb`
- SHA-256: `709bd27afe9c1ce8a833d124eceb2e6ca6458a40924534a34882b253fe4ae644`

### Verify on macOS / Linux

```bash
echo "709bd27afe9c1ce8a833d124eceb2e6ca6458a40924534a34882b253fe4ae644  deadbolt-2.0.1.mcpb" | shasum -a 256 -c
```

### Verify on Windows (PowerShell)

```powershell
(Get-FileHash -Algorithm SHA256 .\deadbolt-2.0.1.mcpb).Hash -eq "709bd27afe9c1ce8a833d124eceb2e6ca6458a40924534a34882b253fe4ae644"
```

## 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-03 (score 48, +1)

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

### 2026-11-01 (score 47, +1)

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

### 2026-10-31 (score 46, +2)

- [functional improvement] Maintenance: unverified → pass

### 2026-10-30 (score 44, 0)

- [security regression] Provenance: unverified → fail

### 2026-10-29 (score 44, −1)

- [security regression] Provenance: fail → unverified
- [functional regression] Maintenance: pass → unverified

### 2026-10-28 (score 45, +1)

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

### 2026-10-26 (score 44, +1)

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

### 2026-10-24 (score 43, +1)

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

## MCP tools (2)

### `deadbolt_get_integration_guide` (~101 tokens)

Get local, read-only DeadBolt setup steps for a supported integration route. Returns operator responsibilities, a placeholder configuration and the enforcement boundary. Does not create files, run a server or grant permission. Available only when operator configuration is blank.

Input parameters:

- `route` (string, required): Integration route: claude_desktop for this bundle, stdio_client for a terminal/editor MCP client, rust for embedding the crate, or http for the local sidecar.

Output parameters:

- `boundary` (string): Protection scope and setup-mode limitation.
- `documentation_url` (string): Official integration documentation URL; this tool performs no network request.
- `operator_config_example` (string): JSON template for the bundle; replace all placeholders deliberately. This tool does not save or apply it.
- `route` (string): Requested integration route.
- `steps` (array): Ordered steps for the trusted developer/operator.

### `deadbolt_check_bundle` (~60 tokens)

Read the bundled engine and provenance metadata, calculate its SHA-256 and report compatibility and packaging integrity for this host. Reads only this installed bundle; does not execute the engine, inspect operator state or test security. Available only when operator configuration is blank.

Output parameters:

- `active_protection` (boolean): Always false in setup mode; no downstream server is configured.
- `boundary` (string): Protection scope and setup-mode limitation.
- `bundle_version` (string): Installed launcher bundle version.
- `checksum_matches` (boolean): Whether the bundled executable matches its packaged SHA-256 metadata. This is corruption detection, not independent signature verification.
- `engine_version` (string): Pinned preview engine version.
- `target` (string): Native target for this host, or unsupported.

## Diagnostics

Captured diagnostic sections: Provenance. The full working is on the page: https://verifymcp.io/servers/seanebones-lang-deadbolt/deadbolt#diagnostics

## Score history

- 2026-11-05: 48
- 2026-11-04: 48
- 2026-11-03: 48
- 2026-11-02: 47
- 2026-11-01: 47
- 2026-10-31: 46
- 2026-10-30: 44
- 2026-10-29: 44
- 2026-10-28: 45
- 2026-10-27: 44
- 2026-10-26: 44
- 2026-10-25: 43
- 2026-10-24: 43
- 2026-10-23: 42
- 2026-10-22: 42
- 2026-10-21: 41
- 2026-10-20: 38
- 2026-10-19: 38
- 2026-10-18: 38
- 2026-10-17: 38
- 2026-10-16: 38
- 2026-10-15: 38
- 2026-10-14: 38
- 2026-10-13: 10
- 2026-10-12: 10

## Common questions

### What is the DeadBolt by NextEleven MCP server?

DeadBolt by NextEleven is an MCP server listed in the public MCP registry as io.github.seanebones-lang/deadbolt. Local execution gate: fixed deadlines, operator-only controls, read-only setup and readable denials. This page covers its MCPB bundle (https://github.com/seanebones-lang/deadbolt/releases/download/mcpb-v2.0.1/deadbolt-2.0.1.mcpb).

### Is the DeadBolt by NextEleven MCP server safe to use?

DeadBolt by NextEleven scores 48 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 DeadBolt by NextEleven MCP server expose?

DeadBolt by NextEleven exposes 2 tools: deadbolt_get_integration_guide, deadbolt_check_bundle. Their descriptions and schemas cost roughly 161 tokens of context every time the server is loaded.

### What licence is the DeadBolt by NextEleven MCP server under?

DeadBolt by NextEleven declares the Apache-2.0 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 DeadBolt by NextEleven MCP server?

VerifyMCP ran 12 checks on DeadBolt by NextEleven, 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 DeadBolt by NextEleven: 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 an MCPB bundle, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Repository: https://github.com/seanebones-lang/deadbolt
- Website: https://nexteleven.dev/deadbolt
- Changelog RSS feed: https://verifymcp.io/servers/seanebones-lang-deadbolt/deadbolt.xml
- Changelog JSON feed: https://verifymcp.io/servers/seanebones-lang-deadbolt/deadbolt/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/seanebones-lang-deadbolt/deadbolt.json
- HTML version of this page: https://verifymcp.io/servers/seanebones-lang-deadbolt/deadbolt