Home / MCP registry index / io.github.mmorris35/devplan-mcp-server

DevPlan MCP Server

io.github.mmorris35/devplan-mcp-server in the official MCP registry. Endpoint https://devplan-mcp-server.mike-c63.workers.dev/mcp. Source: github.com/mmorris35/devplan-mcp-server.

The registry describes it as: Transform project ideas into paint-by-numbers development plans with phases, tasks, and subtasks.

We read its 25 tools on 2026-10-29. Nothing in them matched our tool-poisoning rules.

A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

Claude Code

claude mcp add --transport http devplan-mcp-server https://devplan-mcp-server.mike-c63.workers.dev/mcp

Cursor: ~/.cursor/mcp.json

{
  "mcpServers": {
    "devplan-mcp-server": {
      "url": "https://devplan-mcp-server.mike-c63.workers.dev/mcp"
    }
  }
}

VS Code

code --add-mcp '{"name":"devplan-mcp-server","type":"http","url":"https://devplan-mcp-server.mike-c63.workers.dev/mcp"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which.

Let Claude Code check servers as it adds them

With the free lazaretto-guard plugin installed, when Claude Code adds a server for you or writes one into an MCP config, the plugin reads the server's tools first and asks you if one of our rules matches. Install it, restart Claude Code, then ask it to run the command above.

Install lazaretto-guard

claude plugin marketplace add jamesdfinance-dev/lazaretto-plugins
claude plugin install lazaretto-guard@lazaretto-plugins

Tools it advertises

devplan_start devplan_interview_questions devplan_create_brief devplan_parse_brief devplan_generate_plan devplan_generate_claude_md devplan_list_templates devplan_validate_plan devplan_get_subtask devplan_update_progress devplan_generate_executor devplan_generate_verifier devplan_progress_summary devplan_add_lesson devplan_list_lessons devplan_delete_lesson devplan_archive_lesson devplan_extract_lessons_from_report devplan_parse_issue devplan_issue_to_task devplan_usage_stats devplan_validate_haiku_executable devplan_export_workflow devplan_export_workflow_mermaid devplan_implement

Run this server? Show the check in your README

The badge reflects the latest weekly read:

Markdown

[![MCP tool check](https://lazaretto.dev/mcp-registry/io-github-mmorris35-devplan-mcp-server/badge.svg)](https://lazaretto.dev/mcp-registry/io-github-mmorris35-devplan-mcp-server)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.