# Dev MCP (pypi · braynix-dev-mcp)

AI Engineering Operating System for developer workflows.

- Trust score: 86/100 (high trust)
- Change this week: +6
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- pypi · `braynix-dev-mcp`: 86/100 (this document), [markdown](https://verifymcp.io/servers/pranjal2410719-dev-mcp/braynix-dev-mcp.md), [page](https://verifymcp.io/servers/pranjal2410719-dev-mcp/braynix-dev-mcp)

## Channel facts

- Registry: `pypi`
- Package: `braynix-dev-mcp`
- Version: `2.2.0`
- Transport: `stdio`

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

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - Runs setuptools.build_meta at install time, a recognised build step with no custom scripting around it.
  - 1 of 15 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 100/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to pranjal2410719/dev-mcp).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 13 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 77/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 4700 tokens (~50/item across 93 items; 91 tools + 2 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 47/100
  - Stability observed for 14 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 91/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 67% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 0 of 5 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "delete_path" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default.
  - An AI judge read all 93 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Dev MCP server?

Dev MCP runs locally as a PyPI package, launched with uvx braynix-dev-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add pranjal2410719-dev-mcp -- uvx braynix-dev-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "pranjal2410719-dev-mcp": {
      "command": "uvx",
      "args": [
        "braynix-dev-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "pranjal2410719-dev-mcp": {
      "command": "uvx",
      "args": [
        "braynix-dev-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add pranjal2410719-dev-mcp -- uvx braynix-dev-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "pranjal2410719-dev-mcp": {
      "type": "local",
      "command": [
        "uvx",
        "braynix-dev-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add pranjal2410719-dev-mcp --command uvx --arg braynix-dev-mcp
```

### Hermes

```yaml
mcp_servers:
  pranjal2410719-dev-mcp:
    command: "uvx"
    args: ["braynix-dev-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "pranjal2410719-dev-mcp": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "braynix-dev-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add pranjal2410719-dev-mcp -t stdio -c uvx -a braynix-dev-mcp
```

### Other

```json
{
  "mcpServers": {
    "pranjal2410719-dev-mcp": {
      "command": "uvx",
      "args": [
        "braynix-dev-mcp"
      ]
    }
  }
}
```

## 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-21 (score 86, +21)

- [security improvement] Malware scan: unverified → pass
- [functional improvement] Stability: unverified → 0.47

### 2026-11-20 (score 65, −15)

- [security regression] Malware scan: pass → unverified

### 2026-11-14 (score 80, +1)

- [functional improvement] Security disclosure: unverified → pass

### 2026-11-13 (score 79, −1)

- [functional regression] Security disclosure: pass → unverified

### 2026-11-11 (score 80, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-11-10 (score 65, −15)

- [security regression] Malware scan: pass → unverified

### 2026-11-08 (score 80, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-11-07 (score 65)

First indexed and scored.

## MCP tools (91)

### `read_file` (~90 tokens)

Read the contents of a file with optional line-range slicing and line numbering.

Input parameters:

- `end_line`: 1-indexed end line inclusive (optional).
- `line_numbers` (boolean): If True, prefixes lines with line numbers (e.g. '12 | code').
- `path` (string, required): Relative or absolute path to the file.
- `start_line`: 1-indexed start line (optional).

Output parameters:

- `result` (string)

### `write_file` (~84 tokens)

Write content to a file with atomic commit or append mode.

Input parameters:

- `append` (boolean): If True, appends to the file instead of overwriting.
- `atomic` (boolean): If True, writes to a temp file and replaces atomically.
- `content` (string, required): The text content to write.
- `path` (string, required): Relative or absolute path to the file.

Output parameters:

- `result` (string)

### `edit_file` (~91 tokens)

Replace target string with replacement text in a file with occurrence control and diff preview.

Input parameters:

- `count` (integer): Number of occurrences to replace (0 = replace all, 1 = first only).
- `new_string` (string, required): The replacement string.
- `old_string` (string, required): The exact string to find (case-sensitive, whitespace-sensitive).
- `path` (string, required): Relative or absolute path to the file.

Output parameters:

- `result` (string)

### `batch_replace` (~91 tokens)

Search and replace a string across multiple files matching a glob pattern.

Input parameters:

- `max_files` (integer): Safety cap on modified files.
- `new_string` (string, required): Replacement text.
- `old_string` (string, required): Exact text to search for.
- `pattern` (string, required): Glob pattern matching files (e.g. 'src/**/*.py', '*.ts').
- `root_path` (string): Base directory for search.

Output parameters:

- `result` (string)

### `file_info` (~31 tokens)

Get metadata, line count, permissions, and size for a file or directory.

Input parameters:

- `path` (string, required)

Output parameters:

- `result` (string)

### `delete_path` (~32 tokens)

Delete a file or an empty directory.

Input parameters:

- `path` (string, required): Relative or absolute path to the file/directory.

Output parameters:

- `result` (string)

### `delete_recursive` (~37 tokens)

Recursively delete a file or directory tree. Use with caution.

Input parameters:

- `path` (string, required): Relative or absolute path to the file/directory.

Output parameters:

- `result` (string)

### `list_directory` (~59 tokens)

List files and directories inside a given directory with size and clean filtering.

Input parameters:

- `include_hidden` (boolean): If True, includes hidden and build directories (.git, node_modules, etc.).
- `path` (string, required): Relative or absolute path to the directory.

Output parameters:

- `result` (string)

### `glob_files` (~95 tokens)

Find files matching a glob pattern (e.g. '**/*.ts', 'src/**/*.py') with automatic noise filtering.

Input parameters:

- `base_path` (string): Directory to search from (default: current directory).
- `include_hidden` (boolean): If True, includes .git, node_modules, .venv files.
- `pattern` (string, required): Glob pattern (e.g. '**/*.py', 'src/**/*.ts', '*.json').

Output parameters:

- `result` (string)

### `create_directory` (~33 tokens)

Create one or more directories (like mkdir -p).

Input parameters:

- `path` (string, required): Relative or absolute path to the directory.

Output parameters:

- `result` (string)

### `search_code` (~138 tokens)

Search for a text or regex pattern across codebase with ripgrep, noise exclusion, and context lines.

Input parameters:

- `case_sensitive` (boolean): If True, enforces strict case sensitivity.
- `context_lines` (integer): Number of surrounding context lines to show (0 = match line only).
- `glob_filter`: Optional file pattern filter (e.g. '*.py', '*.ts', '*.{ts,js}').
- `max_results` (integer): Maximum number of result lines to return.
- `path` (string): Directory to search in (default: current directory).
- `pattern` (string, required): The text or regex pattern to search for.

Output parameters:

- `result` (string)

### `run_command` (~82 tokens)

Run a shell command and return its output. Always set a reasonable timeout. Avoid destructive commands (rm -rf, etc.).

Input parameters:

- `command` (string, required): The shell command to run.
- `timeout_seconds` (integer): Maximum seconds to wait (default 60, max 300).
- `workdir`: Working directory for the command (default: server CWD).

Output parameters:

- `result` (string)

### `git_status` (~30 tokens)

Show the working tree status (git status).

Input parameters:

- `repo_path` (string): Path to the git repository.

Output parameters:

- `result` (string)

### `git_diff` (~50 tokens)

Show staged and unstaged changes (git diff).

Input parameters:

- `repo_path` (string): Path to the git repository.
- `staged` (boolean): If True, show only staged changes (git diff --cached).

Output parameters:

- `result` (string)

### `git_log` (~43 tokens)

Show recent commit history (git log).

Input parameters:

- `max_count` (integer): Maximum number of commits to show.
- `repo_path` (string): Path to the git repository.

Output parameters:

- `result` (string)

### `git_branch` (~28 tokens)

List local branches (git branch).

Input parameters:

- `repo_path` (string): Path to the git repository.

Output parameters:

- `result` (string)

### `git_add` (~51 tokens)

Stage file(s) for commit (git add).

Input parameters:

- `files` (string): File(s) to stage (space-separated, or '.' for all).
- `repo_path` (string): Path to the git repository.

Output parameters:

- `result` (string)

### `git_commit` (~40 tokens)

Commit staged changes with a message (git commit).

Input parameters:

- `message` (string): Commit message.
- `repo_path` (string): Path to the git repository.

Output parameters:

- `result` (string)

### `git_create_branch` (~49 tokens)

Create and switch to a new git branch (git checkout -b).

Input parameters:

- `branch_name` (string): Name for the new branch.
- `repo_path` (string): Path to the git repository.

Output parameters:

- `result` (string)

### `install_git_hooks` (~66 tokens)

Install automated pre-commit hook to sync Project Brain and context with native terminal git commits.

Input parameters:

- `hook_type` (string): Hook to install ('pre-commit' or 'post-commit').
- `repo_path` (string): Path to the git repository (defaults to project root).

Output parameters:

- `result` (string)

### `init_context` (~40 tokens)

Initialize or auto-detect project context. Scans project files to detect tech stack, languages, and frameworks.

Input parameters:

- `path` (string): Project root directory.

Output parameters:

- `result` (string)

### `get_context` (~83 tokens)

Get the full project context as formatted text. Optionally filter by dot path (e.g. 'tech_stack.languages').

Input parameters:

- `dot_path` (string): Optional dot-notation path to get a specific field       (e.g. 'project.name', 'tech_stack.languages').       Leave empty to get the entire context.
- `path` (string): Project root directory.

Output parameters:

- `result` (string)

### `update_context` (~76 tokens)

Update a specific field in the project context using dot notation (e.g. 'project.description', 'conventions.code_style').

Input parameters:

- `dot_path` (string, required): Dot-notation path to the field (e.g. 'project.description').
- `path` (string): Project root directory.
- `value` (string, required): The value to set.

Output parameters:

- `result` (string)

### `add_to_context_list` (~77 tokens)

Add an item to a list field in the context (e.g. tech_stack.languages, key_files, active_tasks, goals).

Input parameters:

- `dot_path` (string, required): Path to the list field.
- `item` (string, required): Item to add (string, or JSON for complex items).
- `path` (string): Project root directory.

Output parameters:

- `result` (string)

### `add_key_file` (~76 tokens)

Register a key file with its purpose in the project context.

Input parameters:

- `details` (string): Optional extended notes about the file.
- `file_path` (string, required): Path to the file (relative to project root).
- `purpose` (string, required): What this file does (one sentence).
- `root_path` (string): Project root directory.

Output parameters:

- `result` (string)

### `add_task` (~99 tokens)

Add an active task to the project context.

Input parameters:

- `branch` (string): Optional git branch name.
- `description` (string, required): What needs to be done.
- `notes` (string): Optional notes.
- `path` (string): Project root directory.
- `status` (string): One of: pending, in_progress, blocked, completed.
- `task_id` (string, required): Unique identifier (e.g. 'TASK-1', 'feat-auth').

Output parameters:

- `result` (string)

### `add_decision` (~66 tokens)

Log an architecture decision record (ADR) in the project context.

Input parameters:

- `alternatives` (string): Other options that were considered.
- `decision` (string, required): What was decided.
- `path` (string): Project root directory.
- `reason` (string, required): Why this decision was made.

Output parameters:

- `result` (string)

### `export_context_markdown` (~39 tokens)

Export the project context as a Markdown document for sharing with other LLMs and AI tools.

Input parameters:

- `path` (string): Project root directory.

Output parameters:

- `result` (string)

### `remove_context_item` (~70 tokens)

Remove an item from a list in the project context by index.

Input parameters:

- `dot_path` (string, required): Path to the list (e.g. 'active_tasks', 'key_files').
- `index` (integer, required): Zero-based index of the item to remove.
- `path` (string): Project root directory.

Output parameters:

- `result` (string)

### `reset_context` (~31 tokens)

Reset the project context to default values (clears all data).

Input parameters:

- `path` (string): Project root directory.

Output parameters:

- `result` (string)

### `project_info` (~26 tokens)

Get information about the current project environment.

Input parameters:

- `path` (string): Project root directory.

Output parameters:

- `result` (string)

### `desktop_status` (~19 tokens)

Check desktop accessibility status, permissions, and supported surfaces.

Output parameters:

- `result` (string)

### `desktop_list_apps` (~16 tokens)

List all running GUI desktop applications.

Output parameters:

- `result` (string)

### `desktop_list_windows` (~29 tokens)

List all open windows with titles, dimensions, and window IDs.

Input parameters:

- `app` (string)

Output parameters:

- `result` (string)

### `desktop_snapshot` (~42 tokens)

Capture the accessibility tree of an application with actionable @refs.

Input parameters:

- `app` (string, required)
- `compact` (boolean)
- `interactive_only` (boolean)

Output parameters:

- `result` (string)

### `desktop_find` (~45 tokens)

Search for UI elements matching a role, name, or text in an app.

Input parameters:

- `app` (string, required)
- `name` (string)
- `role` (string)

Output parameters:

- `result` (string)

### `desktop_click` (~37 tokens)

Click an element using its qualified snapshot reference (@snapshot_id:eN).

Input parameters:

- `headed` (boolean)
- `ref_id` (string, required)

Output parameters:

- `result` (string)

### `desktop_type` (~42 tokens)

Insert text into a text field target using its qualified ref.

Input parameters:

- `headed` (boolean)
- `ref_id` (string, required)
- `text` (string, required)

Output parameters:

- `result` (string)

### `desktop_press` (~47 tokens)

Send a keyboard shortcut or key combo (e.g. 'ctrl+c', 'return', 'escape', 'tab').

Input parameters:

- `headed` (boolean)
- `key_combo` (string, required)

Output parameters:

- `result` (string)

### `desktop_scroll` (~53 tokens)

Scroll an element or page by direction (up, down, left, right).

Input parameters:

- `amount` (integer)
- `direction` (string)
- `headed` (boolean)
- `ref_id` (string)

Output parameters:

- `result` (string)

### `desktop_launch` (~35 tokens)

Launch a desktop application and optionally wait for its window to appear.

Input parameters:

- `activate` (boolean)
- `app` (string, required)

Output parameters:

- `result` (string)

### `desktop_close_app` (~32 tokens)

Close an application gracefully or force terminate it.

Input parameters:

- `app` (string, required)
- `force` (boolean)

Output parameters:

- `result` (string)

### `desktop_focus_window` (~36 tokens)

Bring an application or window to the foreground and focus it.

Input parameters:

- `app` (string)
- `window_id` (string)

Output parameters:

- `result` (string)

### `desktop_clipboard` (~41 tokens)

Read, write, or clear system clipboard ('get', 'set', or 'clear').

Input parameters:

- `action` (string)
- `text` (string)

Output parameters:

- `result` (string)

### `desktop_verify_element` (~56 tokens)

Verify if a GUI element exists and assert its state (e.g. enabled, selected).

Input parameters:

- `app` (string, required)
- `expected_state` (string)
- `name` (string)
- `role` (string)

Output parameters:

- `result` (string)

### `desktop_screenshot` (~37 tokens)

Take a screenshot of an application window and save to target path.

Input parameters:

- `app` (string, required)
- `output_path` (string, required)

Output parameters:

- `result` (string)

### `desktop_action` (~55 tokens)

Universal dispatcher executing ANY agent-desktop CLI command (hover, drag, wait, is, get, toggle, batch, etc.).

Input parameters:

- `args` (array)
- `command` (string, required)
- `timeout` (integer)

Output parameters:

- `result` (string)

### `get_prd` (~69 tokens)

Retrieve a PRD document (PRD, VISION, SCOPE, REQUIREMENTS). Returns the content of the specified document.

Input parameters:

- `document` (string): Which document to read — PRD, VISION, SCOPE, or REQUIREMENTS.
- `path` (string): Project root directory.

Output parameters:

- `result` (string)

### `update_prd` (~77 tokens)

Create or update a PRD document (PRD, VISION, SCOPE, REQUIREMENTS).

Input parameters:

- `content` (string, required): The full markdown content of the document.
- `document` (string, required): Which document to write — PRD, VISION, SCOPE, or REQUIREMENTS.
- `path` (string): Project root directory.

Output parameters:

- `result` (string)

### `summarize_prd` (~34 tokens)

Summarize key requirements from PRD documents into a concise bullet list.

Input parameters:

- `path` (string): Project root directory.

Output parameters:

- `result` (string)

### `compare_work_to_prd` (~35 tokens)

Compare current project context and tasks against PRD requirements to check alignment.

Input parameters:

- `path` (string): Project root directory.

Output parameters:

- `result` (string)

### `get_current_phase` (~28 tokens)

Get the current active phase and its status.

Input parameters:

- `path` (string): Project root directory.

Output parameters:

- `result` (string)

### `set_phase` (~70 tokens)

Set the current active development phase. Only tasks in this phase are considered 'in scope'.

Input parameters:

- `description` (string): What this phase involves.
- `path` (string): Project root directory.
- `phase_name` (string, required): Name of the phase (e.g. 'Phase 4 — Activity Creation').

Output parameters:

- `result` (string)

### `complete_phase` (~47 tokens)

Mark the current phase as completed and optionally advance to the next phase.

Input parameters:

- `notes` (string): Summary of what was accomplished in this phase.
- `path` (string): Project root directory.

Output parameters:

- `result` (string)

### `next_phase` (~57 tokens)

Mark current phase as complete and advance to the next phase in sequence.

Input parameters:

- `description` (string): What the next phase involves.
- `path` (string): Project root directory.
- `phase_name` (string, required): Name of the next phase.

Output parameters:

- `result` (string)

### `list_phases` (~32 tokens)

List all phases and their status (completed, active, pending).

Input parameters:

- `path` (string): Project root directory.

Output parameters:

- `result` (string)

### `add_milestone` (~79 tokens)

Define a milestone with a target date and associated features.

Input parameters:

- `features` (string): Comma-separated list of key features for this milestone.
- `name` (string, required): Milestone name (e.g. 'v1.0 Beta').
- `path` (string): Project root directory.
- `target_date` (string): Target completion date.

Output parameters:

- `result` (string)

### `list_milestones` (~27 tokens)

Show all milestones and their status.

Input parameters:

- `path` (string): Project root directory.

Output parameters:

- `result` (string)

### `create_task` (~108 tokens)

Create a new task with phase, priority, dependencies, and description.

Input parameters:

- `depends_on` (string): Comma-separated task IDs that must be completed first.
- `description` (string): Longer description / acceptance criteria.
- `path` (string): Project root directory.
- `phase` (string): Which phase this task belongs to (leave empty for current phase).
- `priority` (string): One of: critical, high, medium, low.
- `title` (string, required): Short task title.

Output parameters:

- `result` (string)

### `update_task` (~99 tokens)

Update a task's status, priority, or description by ID.

Input parameters:

- `path` (string): Project root directory.
- `priority` (string): One of: critical, high, medium, low.
- `status` (string): One of: pending, in_progress, blocked, completed, cancelled.
- `task_id` (string, required): The task ID (e.g. TASK-0001).
- `title` (string): New title (if changing).

Output parameters:

- `result` (string)

### `complete_task` (~49 tokens)

Mark a task as completed with optional notes.

Input parameters:

- `notes` (string): Completion notes.
- `path` (string): Project root directory.
- `task_id` (string, required): The task ID to complete.

Output parameters:

- `result` (string)

### `next_task` (~37 tokens)

Get the highest-priority task that is ready to work on (dependencies met, current phase).

Input parameters:

- `path` (string): Project root directory.

Output parameters:

- `result` (string)

### `blocked_tasks` (~31 tokens)

List all tasks that are blocked, either by dependencies or explicitly.

Input parameters:

- `path` (string): Project root directory.

Output parameters:

- `result` (string)

### `list_tasks` (~78 tokens)

List all active tasks, optionally filtered by phase or status.

Input parameters:

- `path` (string): Project root directory.
- `phase` (string): Filter by phase name.
- `priority` (string): Filter by priority (critical, high, medium, low).
- `status` (string): Filter by status (pending, in_progress, blocked, completed).

Output parameters:

- `result` (string)

### `generate_handoff` (~77 tokens)

Generate a session summary capturing what was done, what's next, and current project state for handoff to another AI.

Input parameters:

- `known_issues` (string): Any bugs or issues the next session should know about.
- `path` (string): Project root directory.
- `session_summary` (string): Brief summary of what was accomplished this session.

Output parameters:

- `result` (string)

### `get_last_handoff` (~37 tokens)

Retrieve the most recent AI handoff document so a new AI session has full context.

Input parameters:

- `path` (string): Project root directory.

Output parameters:

- `result` (string)

### `list_handoffs` (~29 tokens)

List all AI session handoffs with dates.

Input parameters:

- `path` (string): Project root directory.

Output parameters:

- `result` (string)

### `generate_project_brain` (~41 tokens)

Generate a complete aggregated Project Brain dashboard showing current status, phase, active/blocked tasks, recent changes, and recommendations.

Input parameters:

- `path` (string)

Output parameters:

- `result` (string)

### `next_best_action` (~41 tokens)

Intelligently calculate and recommend the next best task to work on based on phase, priority, dependencies, and file hints.

Input parameters:

- `path` (string)

Output parameters:

- `result` (string)

### `start_session` (~43 tokens)

Start a development session. Loads state, PRD, active tasks, and latest handoff to generate a detailed Session Brief for the AI.

Input parameters:

- `path` (string)

Output parameters:

- `result` (string)

### `end_session` (~54 tokens)

End the current session, update progress, and generate a handoff file (does not auto-commit changes).

Input parameters:

- `known_issues` (string)
- `path` (string)
- `session_summary` (string, required)

Output parameters:

- `result` (string)

### `prepare_commit` (~40 tokens)

Analyze modified workspace files and generate a suggested conventional git commit message and summary for approval.

Input parameters:

- `path` (string)
- `session_summary` (string, required)

Output parameters:

- `result` (string)

### `commit_changes` (~37 tokens)

Stage all workspace changes and commit them to Git with the approved commit message.

Input parameters:

- `message` (string, required)
- `path` (string)

Output parameters:

- `result` (string)

### `validate_architecture` (~35 tokens)

Scan the codebase and validate imports/technologies against the project's architectural guidelines and forbidden tools.

Input parameters:

- `path` (string)

Output parameters:

- `result` (string)

### `build_dependency_graph` (~31 tokens)

Scan files and construct a complete mapping of dependencies and references in the project.

Input parameters:

- `path` (string)

Output parameters:

- `result` (string)

### `impact_analysis` (~38 tokens)

Calculate direct and transitive downstream files affected if a given file is modified.

Input parameters:

- `file_path` (string, required)
- `path` (string)

Output parameters:

- `result` (string)

### `sync_workspace` (~44 tokens)

Scan the physical workspace (Git diff, new files, current branch, commits) and compare to the Todo plan to auto-detect finished work.

Input parameters:

- `path` (string)

Output parameters:

- `result` (string)

### `verify_work` (~45 tokens)

Perform deep sanity, test, git diff, and architecture checks against a task to output a reality verification dossier.

Input parameters:

- `path` (string)
- `task_id` (string, required)

Output parameters:

- `result` (string)

### `project_dashboard` (~40 tokens)

Generate a unified Project Manager Dashboard combining phase state, todo progress, git status, architecture violations, and a project health score.

Input parameters:

- `path` (string)

Output parameters:

- `result` (string)

### `extract_requirements` (~32 tokens)

Parse PRD markdown files to extract structured requirements and save them into requirements.json.

Input parameters:

- `path` (string)

Output parameters:

- `result` (string)

### `verify_requirements` (~40 tokens)

Scan codebase to map requirement keywords and verify their implementation status and feature coverage.

Input parameters:

- `feature_name` (string)
- `path` (string)

Output parameters:

- `result` (string)

### `verify_outcome` (~42 tokens)

Perform outcome audits verifying user flows, business goals, and objective completion based on target tasks.

Input parameters:

- `path` (string)
- `task_id` (string, required)

Output parameters:

- `result` (string)

### `assess_project_readiness` (~37 tokens)

Scan the workspace and evaluate its onboarding readiness score (0-100%) against required Project Brain documents.

Input parameters:

- `path` (string)

Output parameters:

- `result` (string)

### `project_readiness_report` (~35 tokens)

Generate a formatted Markdown project readiness report showing missing files, scoring audit, and recommended actions.

Input parameters:

- `path` (string)

Output parameters:

- `result` (string)

### `bootstrap_project` (~41 tokens)

Auto-generate template files and directories (PRD, milestones, active tasks, config yaml) to instantly onboard an unknown repository.

Input parameters:

- `path` (string)

Output parameters:

- `result` (string)

### `adopt_existing_project` (~44 tokens)

Scan an existing legacy codebase (directories, package lists, readmes) and generate context, PRDs, milestones, and audit tasks.

Input parameters:

- `path` (string)

Output parameters:

- `result` (string)

### `doctor` (~32 tokens)

Check the diagnostic health and configuration integrity of the Project Brain and MCP server.

Input parameters:

- `path` (string): Project root directory.

Output parameters:

- `result` (string)

### `reset_project_brain` (~44 tokens)

Wipe all Project Brain configuration, tasks, and context metadata inside the selected project. Leaves git and source code untouched.

Input parameters:

- `path` (string): Project root directory.

Output parameters:

- `result` (string)

### `archive_project_brain` (~44 tokens)

Archive current Project Brain settings and context files to .project_brain_archive/ before a reset or pivot, preserving history.

Input parameters:

- `path` (string): Project root directory.

Output parameters:

- `result` (string)

### `create_project_workspace` (~81 tokens)

Create a new isolated project workspace directory, initialize git, bootstrap the project context/brain, and set up first milestone.

Input parameters:

- `name` (string, required): Name of the project directory to create.
- `path` (string): Parent directory path (default is '.').
- `template` (string): Workspace template name ('blank', 'nextjs', or 'python').

Output parameters:

- `result` (string)

### `get_dev_mcp_profile` (~24 tokens)

Get the active dev-mcp tool profile and registered module count.

Output parameters:

- `result` (string)

## Diagnostics

Captured diagnostic sections: Provenance, Install scripts, Dependencies. The full working is on the page: https://verifymcp.io/servers/pranjal2410719-dev-mcp/braynix-dev-mcp#diagnostics

## Score history

- 2026-11-21: 86
- 2026-11-20: 65
- 2026-11-19: 80
- 2026-11-18: 80
- 2026-11-17: 80
- 2026-11-16: 80
- 2026-11-15: 80
- 2026-11-14: 80
- 2026-11-13: 79
- 2026-11-12: 80
- 2026-11-11: 80
- 2026-11-10: 65
- 2026-11-09: 80
- 2026-11-08: 80
- 2026-11-07: 65

## Common questions

### What is the Dev MCP server?

Dev MCP is listed in the public MCP registry as io.github.pranjal2410719/dev-mcp. AI Engineering Operating System for developer workflows. This page covers its PyPI package (braynix-dev-mcp).

### Is the Dev MCP server safe to use?

Dev MCP scores 86 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. Its build provenance is signed and verified. 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 Dev MCP server expose?

Dev MCP exposes 91 tools: read_file, write_file, edit_file, batch_replace, file_info, and 86 more. Their descriptions and schemas cost roughly 4,610 tokens of context every time the server is loaded.

### Is the Dev MCP server still maintained?

Dev MCP is still listed as active in the MCP registry. We last reached this channel on 21 November 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 Dev MCP server under?

Dev MCP declares the MIT 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 Dev MCP server?

VerifyMCP ran 16 checks on Dev MCP, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to a PyPI package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- PyPI project: https://pypi.org/project/braynix-dev-mcp/
- Socket report: https://socket.dev/pypi/package/braynix-dev-mcp
- Repository: https://github.com/pranjal2410719/dev-mcp
- Changelog RSS feed: https://verifymcp.io/servers/pranjal2410719-dev-mcp/braynix-dev-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/pranjal2410719-dev-mcp/braynix-dev-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/pranjal2410719-dev-mcp/braynix-dev-mcp.json
- HTML version of this page: https://verifymcp.io/servers/pranjal2410719-dev-mcp/braynix-dev-mcp
