Is the Mostov82 Conducted MCP server down?

mcp-registry/io.github.mostov82/conducted-mcp · v0.1.0

Also listed as glama/mostov82/conducted-mcp

healthy
Last checked 2026-10-18 15:06 UTC · handshake 105ms

As of 2026-10-18 15:06 UTC, the Mostov82 Conducted MCP server is up with a Glimind reliability score of 96/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

uptime (30d checks)
100%
checks observed
3,657
outages (90d)
0
tools
7

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

Install Mostov82 Conducted MCP server

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http mostov82-conducted-mcp-server https://conducted-mcp.jonathanmostov.workers.dev/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "mostov82-conducted-mcp-server": {
      "type": "http",
      "url": "https://conducted-mcp.jonathanmostov.workers.dev/mcp"
    }
  }
}

Third-party server, listed as discovered. Review its source before installing.

Agent-readiness: C (76/100)

C (76/100): 0 error(s), 3 warning(s) across 7 tool(s); ~2,008 tokens of tool definitions.
Scores higher than 14% of 15,375 MCP servers Glimind has audited.
Its tool list costs an agent ~2,008 tokens per session — lighter than 55% of servers.
76 → 76 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions70
Safety hints9
Token cost100
Client compatibility70
Protocol100
Reliability100
Stability100

What to fix (4)

7 of 7 tool(s) carry no readOnlyHint/destructiveHint annotations.

Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →

Tools: decision_log_guidance, evaluate_gate, kickoff_plan, kickoff_questions, next_procedure and 2 more

10 parameter(s) across 2 tool(s) have no description.

Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →

Tools: decision_log_guidance, standup_due

1 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.

Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →

Tools: kickoff_questions

No tool declares an outputSchema.

Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →

Auto-fix: 4 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 2 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.mostov82%2Fconducted-mcp/fixes

evaluate_gate 1 change
{
  "name": "evaluate_gate",
  "description": "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.",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "properties": {
      "gates": {
        "type": "array",
        "items": {
          "type": "object",
          "required": [
            "id",
            "resolved"
          ],
          "properties": {
            "id": {
              "type": "string"
            },
            "resolved": {
              "type": "boolean"
            }
          },
          "additionalProperties": false
        },
        "description": "Structured gate list."
      },
      "content": {
        "type": "string",
        "description": "A goal-brief markdown string whose GATE LIST is parsed."
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": true
  },
  "title": "Evaluate whether a goal brief's gates are resolved"
}
kickoff_questions 1 change
{
  "name": "kickoff_questions",
  "description": "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.",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "project_type"
    ],
    "properties": {
      "detected": {
        "type": "object",
        "properties": {
          "ci": {
            "type": "string"
          },
          "language": {
            "type": "string"
          },
          "framework": {
            "type": "string"
          },
          "project_name": {
            "type": "string"
          },
          "existing_docs": {
            "type": "array",
            "items": {
              "type": "string"
            }
          },
          "test_framework": {
            "type": "string"
          },
          "package_manager": {
            "type": "string"
          }
        },
        "description": "Facts the agent detected by inspecting the repo (brownfield only).",
        "additionalProperties": false
      },
      "project_type": {
        "enum": [
          "greenfield",
          "brownfield"
        ],
        "type": "string",
        "description": "'greenfield' or 'brownfield'."
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": true
  },
  "title": "Get the kickoff interview question set"
}
next_procedure 1 change
{
  "name": "next_procedure",
  "description": "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.",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "phase"
    ],
    "properties": {
      "facts": {
        "type": "object",
        "properties": {
          "ticket": {
            "type": "string"
          },
          "work_dir": {
            "type": "string"
          },
          "goal_brief": {
            "type": "string"
          }
        },
        "description": "Optional facts to weave into the procedure (e.g. ticket id, work dir).",
        "additionalProperties": false
      },
      "phase": {
        "enum": [
          "kickoff",
          "goal_brief",
          "intent_doc",
          "session_open",
          "session_active",
          "session_close",
          "standup"
        ],
        "type": "string",
        "description": "Which phase of the methodology loop the agent is in."
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": true
  },
  "title": "Get the procedure for a methodology phase"
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.github.mostov82/conducted-mcp"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/io.github.mostov82/conducted-mcp"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

Markdown
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.mostov82%2Fconducted-mcp.svg)](https://glimind.com/server/mcp-registry%2Fio.github.mostov82%2Fconducted-mcp?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fio.github.mostov82%2Fconducted-mcp?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.mostov82%2Fconducted-mcp.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.mostov82%2Fconducted-mcp.svg
   :target: https://glimind.com/server/mcp-registry%2Fio.github.mostov82%2Fconducted-mcp?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:dfbcef9a9f0d26c3…, first seen 2026-10-17, included at leaf 1053 of 22,425. Version history · verify what your client received.

Tools (7)

Compare: most reliable knowledge servers · most reliable other servers · most reliable productivity servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Mostov82 Conducted MCP server down right now?

As of 2026-10-18 15:06 UTC, the Mostov82 Conducted MCP server is up with a Glimind reliability score of 96/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

How many tools does Mostov82 Conducted MCP server provide?

Mostov82 Conducted MCP server advertises 7 tools, including decision_log_guidance, evaluate_gate, kickoff_plan, kickoff_questions, next_procedure.

How do I install Mostov82 Conducted MCP server?

Point your MCP client at this streamable-http endpoint: https://conducted-mcp.jonathanmostov.workers.dev/mcp

Is the Mostov82 Conducted MCP server safe to connect to an AI agent?

Glimind scanned all 7 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Mostov82 Conducted MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.