Conducted MCP
NPM · CONDUCTED-MCP · 2 COMPONENTS · SCANNED AUG 3
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 →
Supply Chain Security87
- No malware found by supply-chain analysis.Pass
- Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree. 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 32 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability82
- 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 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 Management27
- Stability observed for 8 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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · conducted-mcp
claude mcp add mostov82-conducted-mcp -- npx -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": {
"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.
- 3 Aug 26 +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.
- 2 Aug 26 +63
- Provenance: unverified → fail ▼ security
- Known CVEs: unverified → partial ▲ security
- Install scripts: unverified → pass ▲ security
- Malware scan: unverified → pass ▲ security
- Stability: unverified → 0.23 ▲ functional
- Schema quality: unverified → good ▲ functional
- License: unverified → pass ▲ functional
- Dependency health: unverified → partial ▲ functional
- Maintenance: unverified → pass ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Schema quality: unverified → 100 ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Licence: MIT functional
- 1 Aug 26 −20
- Schema quality: 100 → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 31 Jul 26 −8
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 −18
- Malware scan: pass → unverified ▼ security
- 28 Jul 26 +27
- Security disclosure: unverified → fail ▼ functional
- Tool coverage: unverified → 100 ▲ functional
- 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 functional
- 27 Jul 26 24
First indexed and scored.
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 3 Aug 2026 · Analysed npm/[email protected]
Provenance none
Ecosystem: npm · Outcome: none
Dependencies 95 packages
95 packages in the resolved dependency tree · 95 deprecated · 29 stale.
The dependency tree was only partially resolved, so these counts may be incomplete.
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.
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.