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
add_decision ~66

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

NameTypeReqDescription
alternativesstring–Other options that were considered.
decisionstringyesWhat was decided.
pathstring–Project root directory.
reasonstringyesWhy this decision was made.
NameTypeReqDescription
resultstringyes–

No examples provided.

add_key_file ~76

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

NameTypeReqDescription
detailsstring–Optional extended notes about the file.
file_pathstringyesPath to the file (relative to project root).
purposestringyesWhat this file does (one sentence).
root_pathstring–Project root directory.
NameTypeReqDescription
resultstringyes–

No examples provided.

add_milestone ~79

Define a milestone with a target date and associated features.

NameTypeReqDescription
featuresstring–Comma-separated list of key features for this milestone.
namestringyesMilestone name (e.g. 'v1.0 Beta').
pathstring–Project root directory.
target_datestring–Target completion date.
NameTypeReqDescription
resultstringyes–

No examples provided.

add_task ~99

Add an active task to the project context.

NameTypeReqDescription
branchstring–Optional git branch name.
descriptionstringyesWhat needs to be done.
notesstring–Optional notes.
pathstring–Project root directory.
statusstring–One of: pending, in_progress, blocked, completed.
task_idstringyesUnique identifier (e.g. 'TASK-1', 'feat-auth').
NameTypeReqDescription
resultstringyes–

No examples provided.

add_to_context_list ~77

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

NameTypeReqDescription
dot_pathstringyesPath to the list field.
itemstringyesItem to add (string, or JSON for complex items).
pathstring–Project root directory.
NameTypeReqDescription
resultstringyes–

No examples provided.

adopt_existing_project ~44

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

NameTypeReqDescription
pathstring––
NameTypeReqDescription
resultstringyes–

No examples provided.

archive_project_brain ~44

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

NameTypeReqDescription
pathstring–Project root directory.
NameTypeReqDescription
resultstringyes–

No examples provided.

assess_project_readiness ~37

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

NameTypeReqDescription
pathstring––
NameTypeReqDescription
resultstringyes–

No examples provided.

batch_replace ~91

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

NameTypeReqDescription
max_filesinteger–Safety cap on modified files.
new_stringstringyesReplacement text.
old_stringstringyesExact text to search for.
patternstringyesGlob pattern matching files (e.g. 'src/**/*.py', '*.ts').
root_pathstring–Base directory for search.
NameTypeReqDescription
resultstringyes–

No examples provided.

blocked_tasks ~31

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

NameTypeReqDescription
pathstring–Project root directory.
NameTypeReqDescription
resultstringyes–

No examples provided.

bootstrap_project ~41

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

NameTypeReqDescription
pathstring––
NameTypeReqDescription
resultstringyes–

No examples provided.

build_dependency_graph ~31

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

NameTypeReqDescription
pathstring––
NameTypeReqDescription
resultstringyes–

No examples provided.

commit_changes ~37

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

NameTypeReqDescription
messagestringyes–
pathstring––
NameTypeReqDescription
resultstringyes–

No examples provided.

compare_work_to_prd ~35

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

NameTypeReqDescription
pathstring–Project root directory.
NameTypeReqDescription
resultstringyes–

No examples provided.

complete_phase ~47

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

NameTypeReqDescription
notesstring–Summary of what was accomplished in this phase.
pathstring–Project root directory.
NameTypeReqDescription
resultstringyes–

No examples provided.

complete_task ~49

Mark a task as completed with optional notes.

NameTypeReqDescription
notesstring–Completion notes.
pathstring–Project root directory.
task_idstringyesThe task ID to complete.
NameTypeReqDescription
resultstringyes–

No examples provided.

create_directory ~33

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

NameTypeReqDescription
pathstringyesRelative or absolute path to the directory.
NameTypeReqDescription
resultstringyes–

No examples provided.

create_project_workspace ~81

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

NameTypeReqDescription
namestringyesName of the project directory to create.
pathstring–Parent directory path (default is '.').
templatestring–Workspace template name ('blank', 'nextjs', or 'python').
NameTypeReqDescription
resultstringyes–

No examples provided.

create_task ~108

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

NameTypeReqDescription
depends_onstring–Comma-separated task IDs that must be completed first.
descriptionstring–Longer description / acceptance criteria.
pathstring–Project root directory.
phasestring–Which phase this task belongs to (leave empty for current phase).
prioritystring–One of: critical, high, medium, low.
titlestringyesShort task title.
NameTypeReqDescription
resultstringyes–

No examples provided.

delete_path ~32

Delete a file or an empty directory.

NameTypeReqDescription
pathstringyesRelative or absolute path to the file/directory.
NameTypeReqDescription
resultstringyes–

No examples provided.

delete_recursive ~37

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

NameTypeReqDescription
pathstringyesRelative or absolute path to the file/directory.
NameTypeReqDescription
resultstringyes–

No examples provided.

desktop_action ~55

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

NameTypeReqDescription
argsarray––
commandstringyes–
timeoutinteger––
NameTypeReqDescription
resultstringyes–

No examples provided.

desktop_click ~37

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

NameTypeReqDescription
headedboolean––
ref_idstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

desktop_clipboard ~41

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

NameTypeReqDescription
actionstring––
textstring––
NameTypeReqDescription
resultstringyes–

No examples provided.

desktop_close_app ~32

Close an application gracefully or force terminate it.

NameTypeReqDescription
appstringyes–
forceboolean––
NameTypeReqDescription
resultstringyes–

No examples provided.

desktop_find ~45

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

NameTypeReqDescription
appstringyes–
namestring––
rolestring––
NameTypeReqDescription
resultstringyes–

No examples provided.

desktop_focus_window ~36

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

NameTypeReqDescription
appstring––
window_idstring––
NameTypeReqDescription
resultstringyes–

No examples provided.

desktop_launch ~35

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

NameTypeReqDescription
activateboolean––
appstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

desktop_list_apps ~16

List all running GUI desktop applications.

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultstringyes–

No examples provided.

desktop_list_windows ~29

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

NameTypeReqDescription
appstring––
NameTypeReqDescription
resultstringyes–

No examples provided.

desktop_press ~47

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

NameTypeReqDescription
headedboolean––
key_combostringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

desktop_screenshot ~37

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

NameTypeReqDescription
appstringyes–
output_pathstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

desktop_scroll ~53

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

NameTypeReqDescription
amountinteger––
directionstring––
headedboolean––
ref_idstring––
NameTypeReqDescription
resultstringyes–

No examples provided.

desktop_snapshot ~42

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

NameTypeReqDescription
appstringyes–
compactboolean––
interactive_onlyboolean––
NameTypeReqDescription
resultstringyes–

No examples provided.

desktop_status ~19

Check desktop accessibility status, permissions, and supported surfaces.

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultstringyes–

No examples provided.

desktop_type ~42

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

NameTypeReqDescription
headedboolean––
ref_idstringyes–
textstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

desktop_verify_element ~56

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

NameTypeReqDescription
appstringyes–
expected_statestring––
namestring––
rolestring––
NameTypeReqDescription
resultstringyes–

No examples provided.

doctor ~32

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

NameTypeReqDescription
pathstring–Project root directory.
NameTypeReqDescription
resultstringyes–

No examples provided.

edit_file ~91

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

NameTypeReqDescription
countinteger–Number of occurrences to replace (0 = replace all, 1 = first only).
new_stringstringyesThe replacement string.
old_stringstringyesThe exact string to find (case-sensitive, whitespace-sensitive).
pathstringyesRelative or absolute path to the file.
NameTypeReqDescription
resultstringyes–

No examples provided.

end_session ~54

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

NameTypeReqDescription
known_issuesstring––
pathstring––
session_summarystringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

export_context_markdown ~39

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

NameTypeReqDescription
pathstring–Project root directory.
NameTypeReqDescription
resultstringyes–

No examples provided.

extract_requirements ~32

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

NameTypeReqDescription
pathstring––
NameTypeReqDescription
resultstringyes–

No examples provided.

file_info ~31

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

NameTypeReqDescription
pathstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

generate_handoff ~77

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

NameTypeReqDescription
known_issuesstring–Any bugs or issues the next session should know about.
pathstring–Project root directory.
session_summarystring–Brief summary of what was accomplished this session.
NameTypeReqDescription
resultstringyes–

No examples provided.

generate_project_brain ~41

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

NameTypeReqDescription
pathstring––
NameTypeReqDescription
resultstringyes–

No examples provided.

get_context ~83

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

NameTypeReqDescription
dot_pathstring–Optional dot-notation path to get a specific field (e.g. 'project.name', 'tech_stack.languages'). Leave empty to get the entire context.
pathstring–Project root directory.
NameTypeReqDescription
resultstringyes–

No examples provided.

get_current_phase ~28

Get the current active phase and its status.

NameTypeReqDescription
pathstring–Project root directory.
NameTypeReqDescription
resultstringyes–

No examples provided.

get_dev_mcp_profile ~24

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

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultstringyes–

No examples provided.

get_last_handoff ~37

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

NameTypeReqDescription
pathstring–Project root directory.
NameTypeReqDescription
resultstringyes–

No examples provided.

get_prd ~69

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

NameTypeReqDescription
documentstring–Which document to read — PRD, VISION, SCOPE, or REQUIREMENTS.
pathstring–Project root directory.
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.