conducted-mcp
https://conducted-mcp.jonathanmostov.workers.dev
Registry code: eea3f6eada601472
Stateless advisor + validator for Conducted Development: kickoff, artifact validation, rule checks.
from a public catalogue that lists it, not from the operator
- endpoint
- https://conducted-mcp.jonathanmostov.workers.dev/mcp
- protocol
- streamable-http ·2025-06-18
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is conducted-mcp live?
- Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
- Is conducted-mcp free to use?
- Not measured yet.
- What tools does conducted-mcp have?
- 7 tools: next_procedure, validate_artifact, kickoff_questions, kickoff_plan, standup_due, evaluate_gate, decision_log_guidance.
- Is conducted-mcp safe to connect?
- The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
90 days 99.7%· all time 99.7%
last good check
of 7 tools
- down → live
- degraded → live
- live → degraded· timeout after 20000ms
- unknown → live
- topic
- developer tools
- used for
- get kickoff questions for a project methodology
- validate a methodology artifact
- check whether a standup is due
- get the next procedure step
- takes → gives
- text, data → data, text
- tools
- 7 reads
Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.
through this hub
successful
what callers paid
Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.
next_procedure reads unknown never probed
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.
{ "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 }arguments 39 linesvalidate_artifact reads unknown never probed
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.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "artifact_type", "content" ], "properties": { "content": { "type": "string", "description": "The full markdown text of the artifact to validate." }, "artifact_type": { "enum": [ "goal_brief", "intent_doc", "session_log", "standup" ], "type": "string", "description": "Which artifact to validate." } }, "additionalProperties": false }arguments 25 lineskickoff_questions reads unknown never probed
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.
{ "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 }arguments 49 lineskickoff_plan reads unknown never probed
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).
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "project_type", "answers" ], "properties": { "answers": { "type": "object", "description": "Confirmed interview answers keyed by token id (e.g. PROJECT_NAME, LOCKED_DOCS).", "additionalProperties": { "anyOf": [ { "type": "string" }, { "type": "array", "items": { "type": "string" } } ] } }, "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 }, "existing": { "type": "object", "properties": { "files": { "type": "array", "items": { "type": "string" } } }, "description": "Agent inventory of files already present in the target (for idempotent re-runs).", "additionalProperties": false }, "project_type": { "enum": [ "greenfield", "brownfield" ], "type": "string", "description": "'greenfield' or 'brownfield'." } }, "additionalProperties": false }arguments 80 linesstandup_due reads unknown never probed
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 }.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": { "today": { "type": "string" }, "gate_reached": { "type": "boolean" }, "last_standup_date": { "type": "string" }, "dependency_intersection": { "type": "boolean" }, "working_days_since_last_standup": { "type": "number" } }, "additionalProperties": false }arguments 22 linesevaluate_gate reads unknown never probed
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.
{ "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 }arguments 31 linesdecision_log_guidance reads unknown never probed
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.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": { "escalation_fired": { "type": "boolean" }, "override_architectural": { "type": "boolean" }, "confined_to_one_session": { "type": "boolean" }, "affects_multiple_tickets": { "type": "boolean" }, "gate_resolved_cross_cutting": { "type": "boolean" } }, "additionalProperties": false }arguments 22 lines
This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.
Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your MCP server's instructions — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's ideea3f6eada601472.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/eea3f6eada601472/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/eea3f6eada601472?ref=badge)
The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.
An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.