io.github.Mostov82/conducted-mcp

Est-ce que io.github.Mostov82/conducted-mcp est sûr ?

Au dernier audit MCP Hub, le serveur MCP « io.github.Mostov82/conducted-mcp » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.

Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.

Les 7 outils

• decision_log_guidance≈ 230 tokens

  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.

  Paramètres, retour & exemple (5)

  Paramètres

  • escalation_fired · boolean · optionnel
  • override_architectural · boolean · optionnel
  • confined_to_one_session · boolean · optionnel
  • affects_multiple_tickets · boolean · optionnel
  • gate_resolved_cross_cutting · boolean · optionnel

  Exemple d'appel

  {"name": "decision_log_guidance", "arguments": {"escalation_fired": true, "override_architectural": true, "confined_to_one_session": true, "affects_multiple_tickets": true, "gate_resolved_cross_cutting": true}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• evaluate_gate≈ 240 tokens

  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.

  Paramètres, retour & exemple (2)

  Paramètres

  • gates · array · optionnel
    Structured gate list.
  • content · string · optionnel
    A goal-brief markdown string whose GATE LIST is parsed.

  Exemple d'appel

  {"name": "evaluate_gate", "arguments": {"gates": [], "content": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• kickoff_plan≈ 499 tokens

  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).

  Paramètres, retour & exemple (4)

  Paramètres

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

  Exemple d'appel

  {"name": "kickoff_plan", "arguments": {"answers": {}, "project_type": "greenfield"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• kickoff_questions≈ 312 tokens

  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.

  Paramètres, retour & exemple (2)

  Paramètres

  • detected · object · optionnel
    Facts the agent detected by inspecting the repo (brownfield only).
  • project_type · string · requis · greenfield | brownfield
    'greenfield' or 'brownfield'.

  Exemple d'appel

  {"name": "kickoff_questions", "arguments": {"project_type": "greenfield"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• next_procedure≈ 289 tokens

  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.

  Paramètres, retour & exemple (2)

  Paramètres

  • facts · object · optionnel
    Optional facts to weave into the procedure (e.g. ticket id, work dir).
  • phase · string · requis · kickoff | goal_brief | intent_doc | session_open | session_active | session_close | standup
    Which phase of the methodology loop the agent is in.

  Exemple d'appel

  {"name": "next_procedure", "arguments": {"phase": "kickoff"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• standup_due≈ 203 tokens

  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 }.

  Paramètres, retour & exemple (5)

  Paramètres

  • today · string · optionnel
  • gate_reached · boolean · optionnel
  • last_standup_date · string · optionnel
  • dependency_intersection · boolean · optionnel
  • working_days_since_last_standup · number · optionnel

  Exemple d'appel

  {"name": "standup_due", "arguments": {"today": "texte", "gate_reached": true, "last_standup_date": "texte", "dependency_intersection": true, "working_days_since_last_standup": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• validate_artifact≈ 247 tokens

  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.

  Paramètres, retour & exemple (2)

  Paramètres

  • content · string · requis
    The full markdown text of the artifact to validate.
  • artifact_type · string · requis · goal_brief | intent_doc | session_log | standup
    Which artifact to validate.

  Exemple d'appel

  {"name": "validate_artifact", "arguments": {"content": "texte", "artifact_type": "goal_brief"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

C'est votre serveur ?

Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».

Créer un compte / revendiquer →

Source

https://conducted-mcp.jonathanmostov.workers.dev/mcp