Conducted MCP
NPM · CONDUCTED-MCP · 2 COMPONENTS · SCANNED SEP 21
Stateless advisor + validator for Conducted Development: kickoff, artifact validation, rule checks.
Available components
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 Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 81 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability86
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 1341 tokens (~70/item across 19 items; 7 tools + 12 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
- Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage85
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 55% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 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
How do I install the Conducted MCP server?
Conducted MCP runs locally as an npm package, launched with npx -y conducted-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · conducted-mcp
claude mcp add mostov82-conducted-mcp -- npx -y conducted-mcp
{
"mcpServers": {
"mostov82-conducted-mcp": {
"command": "npx",
"args": [
"-y",
"conducted-mcp"
]
}
}
} {
"servers": {
"mostov82-conducted-mcp": {
"command": "npx",
"args": [
"-y",
"conducted-mcp"
]
}
}
} codex mcp add mostov82-conducted-mcp -- npx -y conducted-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"mostov82-conducted-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"conducted-mcp"
],
"enabled": true
}
}
} openclaw mcp add mostov82-conducted-mcp --command npx --arg -y --arg conducted-mcp
mcp_servers:
mostov82-conducted-mcp:
command: "npx"
args: ["-y", "conducted-mcp"] {
"McpServers": {
"mostov82-conducted-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"conducted-mcp"
]
}
}
} assistant mcp add mostov82-conducted-mcp -t stdio -c npx -a -y conducted-mcp
{
"mcpServers": {
"mostov82-conducted-mcp": {
"command": "npx",
"args": [
"-y",
"conducted-mcp"
]
}
}
} 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.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 −3
- Stability: pass → 0.80 functional
- 15 Sept 26 +1
- Stability: 0.97 → pass security
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 0
- Security disclosure: unverified → fail ▼ functional
- 9 Sept 26 −2
- Security disclosure: fail → unverified ▼ functional
- Stability: pass → 0.80 functional
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 Sept 2026 · Analysed npm/conducted-mcp@0.1.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 96 packages
| Packages resolved | 96 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
decision_log_guidance Judge whether a situation belongs in the Decision Log ~160
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.
| Name | Type | Req | Description |
|---|---|---|---|
| affects_multiple_tickets | boolean | – | – |
| confined_to_one_session | boolean | – | – |
| escalation_fired | boolean | – | – |
| gate_resolved_cross_cutting | boolean | – | – |
| override_architectural | boolean | – | – |
No output schema declared.
No examples provided.
evaluate_gate Evaluate whether a goal brief's gates are resolved ~133
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.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | – | A goal-brief markdown string whose GATE LIST is parsed. |
| gates | array | – | Structured gate list. |
No output schema declared.
No examples provided.
kickoff_plan Assemble the kickoff file plan ~263
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).
| Name | Type | Req | Description |
|---|---|---|---|
| answers | object | yes | 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 | yes | 'greenfield' or 'brownfield'. |
No output schema declared.
No examples provided.
kickoff_questions Get the kickoff interview question set ~145
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.
| Name | Type | Req | Description |
|---|---|---|---|
| detected | object | – | Facts the agent detected by inspecting the repo (brownfield only). |
| project_type | string | yes | 'greenfield' or 'brownfield'. |
No output schema declared.
No examples provided.
next_procedure Get the procedure for a methodology phase ~145
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.
| Name | Type | Req | Description |
|---|---|---|---|
| facts | object | – | Optional facts to weave into the procedure (e.g. ticket id, work dir). |
| phase | string | yes | Which phase of the methodology loop the agent is in. |
No output schema declared.
No examples provided.
standup_due Judge whether a standup is due ~143
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 }.
| Name | Type | Req | Description |
|---|---|---|---|
| dependency_intersection | boolean | – | – |
| gate_reached | boolean | – | – |
| last_standup_date | string | – | – |
| today | string | – | – |
| working_days_since_last_standup | number | – | – |
No output schema declared.
No examples provided.
validate_artifact Validate a methodology artifact ~134
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.
| Name | Type | Req | Description |
|---|---|---|---|
| artifact_type | string | yes | Which artifact to validate. |
| content | string | yes | The full markdown text of the artifact to validate. |
No output schema declared.
No examples provided.
What is the Conducted MCP server?
Conducted MCP is listed in the public MCP registry as io.github.Mostov82/conducted-mcp. Stateless advisor + validator for Conducted Development: kickoff, artifact validation, rule checks. This page covers its npm package (conducted-mcp).
Is the Conducted MCP server safe to use?
Conducted MCP scores 84 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 September 2026. It declares no install or post-install scripts. 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 Conducted MCP server expose?
Conducted MCP exposes 7 tools: validate_artifact, kickoff_questions, kickoff_plan, next_procedure, standup_due, and 2 more. Their descriptions and schemas cost roughly 1,123 tokens of context every time the server is loaded.
Is the Conducted MCP server still maintained?
Conducted MCP is still listed as active in the MCP registry. We last reached this channel on 21 September 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 Conducted MCP server under?
Conducted 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.