Developer · Local MCP server
Deadzone
Local-first MCP server: semantic search over library docs. No cloud, no API key, no telemetry.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.laradji/deadzone- Version
- 0.7.4
- Status
- Active
- Category
- developer
- Transport
- stdio (local process)
- Package
- OCI image (Docker)
- Published
- 2026-05-07
- Updated
- 2026-05-07
- Publisher
- laradji (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/laradji) · how
- Website
- github.com/laradji/deadzone
- Repository
- github.com/laradji/deadzone
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| OCI image (Docker) | ghcr.io/laradji/deadzone:v0.7.4 | - | stdio |
How to connect Deadzone
Deadzone runs locally from a container image in an OCI registry such as Docker Hub or GitHub Container Registry: ghcr.io/laradji/deadzone:v0.7.4. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Docker or another OCI container runtime; started with docker run - the usual command is docker run -i --rm ghcr.io/laradji/deadzone:v0.7.4.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"deadzone": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/laradji/deadzone:v0.7.4"
]
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| DbtDbt MCP - manifest/run_results/sources/catalog parsing + DQ result tables (BigQuery/Postgres) | Local · stdio |
| DbxQuery databases from AI agents using connections configured in DBX. | Local · stdio |
| DCL Trust Oracle - AI/LLM Output Audit (x402 MCP)AI/LLM agent output audit MCP: policy eval, tamper-evident chain, AI safety, x402 USDC on Base. | Remote · HTTPLive check: ✓ handshake |
| ddflowWork-queue kernel for AI coding agents: dependencies, worktree isolation, quality gates, recovery. | Local · stdio |
| Dear ClaudeSpawn Claude Code instances from 6 platforms when 'Dear Claude' is mentioned. | Local · stdio |
| Debugai MCPMCP server for DebugAI. Browser sign-in, auto client setup, no key pasting. | Local · stdio |
| DebugBundleDebugBundle MCP: runtime error reporting, incident response, health checks, and product analytics. | Local · stdio |
| DebugiumAI-driven live debugger with MCP bridge for Python, JS, TS, Rust, Java, C/C++. | Local · stdio |