# Conducted MCP (npm · conducted-mcp)

Stateless advisor + validator for Conducted Development: kickoff, artifact validation, rule checks.

- Trust score: 69/100 (medium)
- Change this week: +45
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `conducted-mcp.jonathanmostov.workers.dev`: 62/100, [markdown](https://verifymcp.io/servers/mostov82-conducted-mcp/conducted-mcp.md), [page](https://verifymcp.io/servers/mostov82-conducted-mcp/conducted-mcp)
- npm · `conducted-mcp`: 69/100 (this document), [markdown](https://verifymcp.io/servers/mostov82-conducted-mcp/conducted-mcp-2.md), [page](https://verifymcp.io/servers/mostov82-conducted-mcp/conducted-mcp-2)

## Channel facts

- Registry: `npm`
- Package: `conducted-mcp`
- Version: `0.1.1`
- 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-08-03.

- **Supply Chain Security**: 87/100
  - No malware found by supply-chain analysis.
  - Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree.
  - No install/post-install scripts declared.
  - Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 32 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 82/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 1341 tokens (~70/item across 19 items; 7 tools + 12 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 85/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 55% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add mostov82-conducted-mcp -- npx -y conducted-mcp
```

### Codex

```bash
codex mcp add mostov82-conducted-mcp -- npx -y conducted-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "mostov82-conducted-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "conducted-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add mostov82-conducted-mcp --command npx --arg -y --arg conducted-mcp
```

### Hermes

```yaml
mcp_servers:
  mostov82-conducted-mcp:
    command: "npx"
    args: ["-y", "conducted-mcp"]
```

### Other

```json
{
  "mcpServers": {
    "mostov82-conducted-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "conducted-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-08-03 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-02 (score 68, +63)

- [security regression] Provenance: unverified → fail
- [security improvement] Known CVEs: unverified → partial
- [security improvement] Install scripts: unverified → pass
- [security improvement] Malware scan: unverified → pass
- [functional improvement] Stability: unverified → 0.23
- [functional improvement] Schema quality: unverified → good
- [functional improvement] License: unverified → pass
- [functional improvement] Dependency health: unverified → partial
- [functional improvement] Maintenance: unverified → pass
- [functional improvement] MCP protocol: unverified → pass
- [functional improvement] Schema quality: unverified → 100
- [functional improvement] Tool coverage: unverified → 100
- [functional] Licence: MIT

### 2026-08-01 (score 5, −20)

- [functional regression] Schema quality: 100 → unverified
- [functional regression] Tool coverage: 100 → unverified

### 2026-07-31 (score 25, −8)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 33, −18)

- [security regression] Malware scan: pass → unverified

### 2026-07-28 (score 51, +27)

- [functional regression] Security disclosure: unverified → fail
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] Schema quality: unverified → 100
- [functional] First check of Schema quality: pass
- [functional] First check of Schema quality: unverified
- [functional] First check of Tool coverage: 55
- [functional] First check of Schema quality: fail

### 2026-07-27 (score 24)

First indexed and scored.

## MCP tools (7)

### `validate_artifact` (~134 tokens)

Validate a methodology artifact

Strictly check whether a Conducted Development artifact's text satisfies the methodology's required structure. Supply the artifact's type and its full text (the server never reads files). Returns { valid, missing, warnings }: `missing` lists required sections that are absent, empty, or contain only unmodified template placeholder text (blocking); `warnings` lists sections that are present but look thin (advisory, non-blocking). `valid` is true iff `missing` is empty.

Input parameters:

- `artifact_type` (string, required): Which artifact to validate.
- `content` (string, required): The full markdown text of the artifact to validate.

### `kickoff_questions` (~145 tokens)

Get the kickoff interview question set

Return the branched kickoff interview (DECISIONS.md D3/D4). Supply `project_type`: 'greenfield' asks the full set; 'brownfield' uses the agent-supplied `detected` facts (language, framework, tests, CI, existing docs) to pre-fill candidates and drop fully-inferable questions — except LOCKED_DOCS, which is always asked because it is human judgment. Returns { project_type, questions, inferred, notes }; the server reads no files.

Input parameters:

- `detected` (object): Facts the agent detected by inspecting the repo (brownfield only).
- `project_type` (string, required): 'greenfield' or 'brownfield'.

### `kickoff_plan` (~263 tokens)

Assemble the kickoff file plan

Assemble, from the bundled templates, the four `_template.md` copies (front-matter tokens replaced), `decision-log.md`, and a filled `AGENT_CONVENTIONS.md` (kickoff guide Steps 2–5). Supply `project_type`, the interview `answers`, optional `detected` (brownfield pre-fill fallback), and optional `existing` (the agent's inventory of files already present). Returns { files: [{ path, content, action }], missing, open_questions, warnings }. The plan is ready iff `missing` is empty (D5 strict); a file with any unresolved {{…}} token is reported in `missing`. Idempotent: already-present files are 'review'/'skip', never overwritten. The server returns content + paths only — it writes nothing (Model C, D2/D6).

Input parameters:

- `answers` (object, required): Confirmed interview answers keyed by token id (e.g. PROJECT_NAME, LOCKED_DOCS).
- `detected` (object): Facts the agent detected by inspecting the repo (brownfield only).
- `existing` (object): Agent inventory of files already present in the target (for idempotent re-runs).
- `project_type` (string, required): 'greenfield' or 'brownfield'.

### `next_procedure` (~145 tokens)

Get the procedure for a methodology phase

Return the ordered procedure for where the agent is in the methodology loop. Supply `phase` (one of: kickoff, goal_brief, intent_doc, session_open, session_active, session_close, standup) and optional `facts` (e.g. a ticket id) to tailor the output. Returns { steps, reads_first, escalation_points, notes? } sourced from the bundled guides and conventions — the procedure half of advisor + validator. The server reads no files.

Input parameters:

- `facts` (object): Optional facts to weave into the procedure (e.g. ticket id, work dir).
- `phase` (string, required): Which phase of the methodology loop the agent is in.

### `standup_due` (~143 tokens)

Judge whether a standup is due

Given agent-supplied facts, decide whether a standup is due. Triggers in priority order: a deliverable gate reached → 'gate'; else a dependency intersection → 'intersection'; else more than five working days since the last standup → 'weekly'; else 'none'. Working days are an input (the working week varies by team), never computed from a calendar. Returns { due, reason, detail }.

Input parameters:

- `dependency_intersection` (boolean)
- `gate_reached` (boolean)
- `last_standup_date` (string)
- `today` (string)
- `working_days_since_last_standup` (number)

### `evaluate_gate` (~133 tokens)

Evaluate whether a goal brief's gates are resolved

Encode the goal-brief rule that no session may begin while any gate is open. Supply either a structured `gates` list ([{ id, resolved }]) or a goal-brief `content` string, in which case the GATE LIST checkboxes (- [ ] / - [x]) are parsed. Returns { all_resolved, unresolved, may_begin } where may_begin === all_resolved. The server reads no files — the content is agent-supplied.

Input parameters:

- `content` (string): A goal-brief markdown string whose GATE LIST is parsed.
- `gates` (array): Structured gate list.

### `decision_log_guidance` (~160 tokens)

Judge whether a situation belongs in the Decision Log

Encode the Decision-Log 'when to use it' rules. Set whichever apply: `escalation_fired`, `gate_resolved_cross_cutting`, `affects_multiple_tickets`, `override_architectural`, `confined_to_one_session`. Returns { should_log, reason, entry_template? }; when should_log is true the Context/Trigger/Decision/Rationale/Affects skeleton is returned. A decision confined to one session does not need an entry — the session notes suffice.

Input parameters:

- `affects_multiple_tickets` (boolean)
- `confined_to_one_session` (boolean)
- `escalation_fired` (boolean)
- `gate_resolved_cross_cutting` (boolean)
- `override_architectural` (boolean)

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/mostov82-conducted-mcp/conducted-mcp-2#diagnostics

## Score history

- 2026-08-03: 69
- 2026-08-02: 68
- 2026-08-01: 5
- 2026-07-31: 25
- 2026-07-30: 33
- 2026-07-28: 51
- 2026-07-27: 24

## Links

- npm package: https://www.npmjs.com/package/conducted-mcp
- Socket report: https://socket.dev/npm/package/conducted-mcp
- Repository: https://github.com/Mostov82/conducted-mcp
- Changelog RSS feed: https://verifymcp.io/servers/mostov82-conducted-mcp/conducted-mcp-2/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/mostov82-conducted-mcp/conducted-mcp-2/changelog.json
- HTML version of this page: https://verifymcp.io/servers/mostov82-conducted-mcp/conducted-mcp-2