Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Dev MCP

PYPI · BRAYNIX-DEV-MCP

AI Engineering Operating System for developer workflows.

Available components

+6 this week 86 Trust /100

Last scanned (17 hours ago)

Scores higher than 87% of PyPI servers

Category Project Management

Trust breakdown (7 categories)

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 Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Runs setuptools.build_meta at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
  • 1 of 15 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to pranjal2410719/dev-mcp). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 13 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability77
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 4700 tokens (~50/item across 93 items; 91 tools + 2 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management47
  • Stability observed for 14 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage91
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 67% of tool parameters carry a description.Partial
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 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. See how to fix → Fail
  • An AI judge read all 93 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (16)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

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 →

Changelog

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.

  • 21 Nov 26 +21
    • Malware scan: unverified → pass ▲ security
    • Stability: unverified → 0.47 ▲ functional
  • 20 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
  • 14 Nov 26 +1
    • Security disclosure: unverified → pass ▲ functional
  • 13 Nov 26 −1
    • Security disclosure: pass → unverified ▼ functional
  • 11 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 10 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
  • 8 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 7 Nov 26 65

    First indexed and scored.

Diagnostics

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 21 Nov 2026 · Analysed pypi/braynix-dev-mcp@2.2.0

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem pypi
Reason Verified
Discovered via Registry attestation endpoint
Source repo pranjal2410719/dev-mcp
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/pranjal2410719/dev-mcp/.github/workflows/publish.yml@refs/tags/v2.2.0
Rekor log index 3743703846
Predicate type PyPI publish attestation https://docs.pypi.org/attestations/publish/v1
Subject digest sha256:2ae8fde50638310bfb6e480047c811e8f1791d470182f810dd8a9c27d70718cc

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend Known build tool setuptools.build_meta

Background: Why install scripts are a supply-chain risk →

Dependencies 15 packages
Packages resolved 15
Stale 1
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 91 exposed · ~4,610 tokens

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 →

Tool Tokens
git_add ~51

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

NameTypeReqDescription
filesstring–File(s) to stage (space-separated, or '.' for all).
repo_pathstring–Path to the git repository.
NameTypeReqDescription
resultstringyes–

No examples provided.

git_branch ~28

List local branches (git branch).

NameTypeReqDescription
repo_pathstring–Path to the git repository.
NameTypeReqDescription
resultstringyes–

No examples provided.

git_commit ~40

Commit staged changes with a message (git commit).

NameTypeReqDescription
messagestring–Commit message.
repo_pathstring–Path to the git repository.
NameTypeReqDescription
resultstringyes–

No examples provided.

git_create_branch ~49

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

NameTypeReqDescription
branch_namestring–Name for the new branch.
repo_pathstring–Path to the git repository.
NameTypeReqDescription
resultstringyes–

No examples provided.

git_diff ~50

Show staged and unstaged changes (git diff).

NameTypeReqDescription
repo_pathstring–Path to the git repository.
stagedboolean–If True, show only staged changes (git diff --cached).
NameTypeReqDescription
resultstringyes–

No examples provided.

git_log ~43

Show recent commit history (git log).

NameTypeReqDescription
max_countinteger–Maximum number of commits to show.
repo_pathstring–Path to the git repository.
NameTypeReqDescription
resultstringyes–

No examples provided.

git_status ~30

Show the working tree status (git status).

NameTypeReqDescription
repo_pathstring–Path to the git repository.
NameTypeReqDescription
resultstringyes–

No examples provided.

glob_files ~95

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

NameTypeReqDescription
base_pathstring–Directory to search from (default: current directory).
include_hiddenboolean–If True, includes .git, node_modules, .venv files.
patternstringyesGlob pattern (e.g. '**/*.py', 'src/**/*.ts', '*.json').
NameTypeReqDescription
resultstringyes–

No examples provided.

impact_analysis ~38

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

NameTypeReqDescription
file_pathstringyes–
pathstring––
NameTypeReqDescription
resultstringyes–

No examples provided.

init_context ~40

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

NameTypeReqDescription
pathstring–Project root directory.
NameTypeReqDescription
resultstringyes–

No examples provided.

install_git_hooks ~66

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

NameTypeReqDescription
hook_typestring–Hook to install ('pre-commit' or 'post-commit').
repo_pathstring–Path to the git repository (defaults to project root).
NameTypeReqDescription
resultstringyes–

No examples provided.

list_directory ~59

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

NameTypeReqDescription
include_hiddenboolean–If True, includes hidden and build directories (.git, node_modules, etc.).
pathstringyesRelative or absolute path to the directory.
NameTypeReqDescription
resultstringyes–

No examples provided.

list_handoffs ~29

List all AI session handoffs with dates.

NameTypeReqDescription
pathstring–Project root directory.
NameTypeReqDescription
resultstringyes–

No examples provided.

list_milestones ~27

Show all milestones and their status.

NameTypeReqDescription
pathstring–Project root directory.
NameTypeReqDescription
resultstringyes–

No examples provided.

list_phases ~32

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

NameTypeReqDescription
pathstring–Project root directory.
NameTypeReqDescription
resultstringyes–

No examples provided.

list_tasks ~78

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

NameTypeReqDescription
pathstring–Project root directory.
phasestring–Filter by phase name.
prioritystring–Filter by priority (critical, high, medium, low).
statusstring–Filter by status (pending, in_progress, blocked, completed).
NameTypeReqDescription
resultstringyes–

No examples provided.

next_best_action ~41

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

NameTypeReqDescription
pathstring––
NameTypeReqDescription
resultstringyes–

No examples provided.

next_phase ~57

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

NameTypeReqDescription
descriptionstring–What the next phase involves.
pathstring–Project root directory.
phase_namestringyesName of the next phase.
NameTypeReqDescription
resultstringyes–

No examples provided.

next_task ~37

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

NameTypeReqDescription
pathstring–Project root directory.
NameTypeReqDescription
resultstringyes–

No examples provided.

prepare_commit ~40

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

NameTypeReqDescription
pathstring––
session_summarystringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

project_dashboard ~40

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

NameTypeReqDescription
pathstring––
NameTypeReqDescription
resultstringyes–

No examples provided.

project_info ~26

Get information about the current project environment.

NameTypeReqDescription
pathstring–Project root directory.
NameTypeReqDescription
resultstringyes–

No examples provided.

project_readiness_report ~35

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

NameTypeReqDescription
pathstring––
NameTypeReqDescription
resultstringyes–

No examples provided.

read_file ~90

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

NameTypeReqDescription
end_line––1-indexed end line inclusive (optional).
line_numbersboolean–If True, prefixes lines with line numbers (e.g. '12 | code').
pathstringyesRelative or absolute path to the file.
start_line––1-indexed start line (optional).
NameTypeReqDescription
resultstringyes–

No examples provided.

remove_context_item ~70

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

NameTypeReqDescription
dot_pathstringyesPath to the list (e.g. 'active_tasks', 'key_files').
indexintegeryesZero-based index of the item to remove.
pathstring–Project root directory.
NameTypeReqDescription
resultstringyes–

No examples provided.

reset_context ~31

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

NameTypeReqDescription
pathstring–Project root directory.
NameTypeReqDescription
resultstringyes–

No examples provided.

reset_project_brain ~44

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

NameTypeReqDescription
pathstring–Project root directory.
NameTypeReqDescription
resultstringyes–

No examples provided.

run_command ~82

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

NameTypeReqDescription
commandstringyesThe shell command to run.
timeout_secondsinteger–Maximum seconds to wait (default 60, max 300).
workdir––Working directory for the command (default: server CWD).
NameTypeReqDescription
resultstringyes–

No examples provided.

search_code ~138

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

NameTypeReqDescription
case_sensitiveboolean–If True, enforces strict case sensitivity.
context_linesinteger–Number of surrounding context lines to show (0 = match line only).
glob_filter––Optional file pattern filter (e.g. '*.py', '*.ts', '*.{ts,js}').
max_resultsinteger–Maximum number of result lines to return.
pathstring–Directory to search in (default: current directory).
patternstringyesThe text or regex pattern to search for.
NameTypeReqDescription
resultstringyes–

No examples provided.

set_phase ~70

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

NameTypeReqDescription
descriptionstring–What this phase involves.
pathstring–Project root directory.
phase_namestringyesName of the phase (e.g. 'Phase 4 — Activity Creation').
NameTypeReqDescription
resultstringyes–

No examples provided.

start_session ~43

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

NameTypeReqDescription
pathstring––
NameTypeReqDescription
resultstringyes–

No examples provided.

summarize_prd ~34

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

NameTypeReqDescription
pathstring–Project root directory.
NameTypeReqDescription
resultstringyes–

No examples provided.

sync_workspace ~44

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

NameTypeReqDescription
pathstring––
NameTypeReqDescription
resultstringyes–

No examples provided.

update_context ~76

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

NameTypeReqDescription
dot_pathstringyesDot-notation path to the field (e.g. 'project.description').
pathstring–Project root directory.
valuestringyesThe value to set.
NameTypeReqDescription
resultstringyes–

No examples provided.

update_prd ~77

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

NameTypeReqDescription
contentstringyesThe full markdown content of the document.
documentstringyesWhich document to write — PRD, VISION, SCOPE, or REQUIREMENTS.
pathstring–Project root directory.
NameTypeReqDescription
resultstringyes–

No examples provided.

update_task ~99

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

NameTypeReqDescription
pathstring–Project root directory.
prioritystring–One of: critical, high, medium, low.
statusstring–One of: pending, in_progress, blocked, completed, cancelled.
task_idstringyesThe task ID (e.g. TASK-0001).
titlestring–New title (if changing).
NameTypeReqDescription
resultstringyes–

No examples provided.

validate_architecture ~35

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

NameTypeReqDescription
pathstring––
NameTypeReqDescription
resultstringyes–

No examples provided.

verify_outcome ~42

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

NameTypeReqDescription
pathstring––
task_idstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

verify_requirements ~40

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

NameTypeReqDescription
feature_namestring––
pathstring––
NameTypeReqDescription
resultstringyes–

No examples provided.

verify_work ~45

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

NameTypeReqDescription
pathstring––
task_idstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

write_file ~84

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

NameTypeReqDescription
appendboolean–If True, appends to the file instead of overwriting.
atomicboolean–If True, writes to a temp file and replaces atomically.
contentstringyesThe text content to write.
pathstringyesRelative or absolute path to the file.
NameTypeReqDescription
resultstringyes–

No examples provided.

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.

pypi · braynix-dev-mcp

# add to Claude Code
claude mcp add pranjal2410719-dev-mcp -- uvx braynix-dev-mcp
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.