conducted-mcp

MCPcommunitylive
v0.1.1Jonathan MostovMITUpdated 3mo agonpmGitHub

A stateless advisor + validator MCP server for the Conducted Development methodology — guided kickoff, artifact validation, phase procedures, and rule checks. Model- and tool-agnostic.

Endpoint healthlive
checked 4 days ago · 376ms
100% of the last 5 checks reached this endpoint
Works in
ClaudeCursorCopilotChatGPTGemini

Inferred from the transports this listing declares (stdio, streamable-http). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
3mo agoLast update
Package
AuthorJonathan Mostov
LicenseMIT
Version0.1.1
Sourcenpm+mcp-registry
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/20
→ Publisher: run `forge publish` from the package repo to claim ownership
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
—npm Trusted Publishing (Sigstore)+0/5
→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo
—npm maintainer match+0/5
→ Earned once your identity is verified above and that login is an npm maintainer of this package
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
Dependencies60 resolved · 1 with advisories
Tool surface7 tools · 1 privileged
Security scan✓ Cleanv0.1.1 · 1mo agoHow well does this scan work?
EvalsNone
IndexedJul 2, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

7 tools · 1 privileged
Statically extracted from the published packagev0.1.1 · 1mo ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

validate_artifactNo description published

This tool published no description. Forge does not invent one.

kickoff_questionsNo description published

This tool published no description. Forge does not invent one.

kickoff_planNo description published

This tool published no description. Forge does not invent one.

next_procedureNo description published

This tool published no description. Forge does not invent one.

standup_dueNo description published

This tool published no description. Forge does not invent one.

evaluate_gateprivilegedNo description published

This tool published no description. Forge does not invent one.

decision_log_guidanceNo description published

This tool published no description. Forge does not invent one.

0 of 7 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

A stateless advisor + validator MCP server for the Conducted Development methodology — guided kickoff, artifact validation, phase procedures, and rule checks. Model- and tool-agnostic.

Keywords
mcpmodel-context-protocolmodelcontextprotocolconducted-developmentmethodologyagentaiplanningkickoffvalidator
Alternatives
Comparing tool surfaces…

No dependency coverage

This package was last scanned before Forge began storing the resolved tree. The next scan will record it.