# Idea to Product Sequencer (remote · mcp.modernmustardseed.com)

Rule-based product method: scores an idea, finds its riskiest assumption, sequences the build.

- Trust score: 75/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-22

## Components

- remote · `mcp.modernmustardseed.com`: 75/100 (this document), [markdown](https://verifymcp.io/servers/com-modernmustardseed-idea-sequencer/idea-sequencer.md), [page](https://verifymcp.io/servers/com-modernmustardseed-idea-sequencer/idea-sequencer)

## Channel facts

- Endpoint: `https://mcp.modernmustardseed.com/idea-sequencer`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-22.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 69/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 2717 tokens (~388/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 33/100
  - Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 96/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 88% of tool parameters carry a description.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "kill_or_continue" implies "kill" and declares readOnlyHint instead, contradicting what its own name says it does.
  - An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the Idea to Product Sequencer MCP server?

Idea to Product Sequencer is a hosted endpoint at https://mcp.modernmustardseed.com/idea-sequencer, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http com-modernmustardseed-idea-sequencer 'https://mcp.modernmustardseed.com/idea-sequencer'
```

### Cursor

```json
{
  "mcpServers": {
    "com-modernmustardseed-idea-sequencer": {
      "url": "https://mcp.modernmustardseed.com/idea-sequencer"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-modernmustardseed-idea-sequencer": {
      "type": "http",
      "url": "https://mcp.modernmustardseed.com/idea-sequencer"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-modernmustardseed-idea-sequencer]
url = "https://mcp.modernmustardseed.com/idea-sequencer"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-modernmustardseed-idea-sequencer": {
      "type": "remote",
      "url": "https://mcp.modernmustardseed.com/idea-sequencer",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-modernmustardseed-idea-sequencer --url 'https://mcp.modernmustardseed.com/idea-sequencer' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-modernmustardseed-idea-sequencer:
    url: "https://mcp.modernmustardseed.com/idea-sequencer"
```

### Netclaw

```json
{
  "McpServers": {
    "com-modernmustardseed-idea-sequencer": {
      "Transport": "http",
      "Url": "https://mcp.modernmustardseed.com/idea-sequencer"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-modernmustardseed-idea-sequencer -t streamable-http -u 'https://mcp.modernmustardseed.com/idea-sequencer'
```

### Other

```json
{
  "mcpServers": {
    "com-modernmustardseed-idea-sequencer": {
      "type": "http",
      "url": "https://mcp.modernmustardseed.com/idea-sequencer"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-21 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-19 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-17 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-14 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-13 (score 71, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-12 (score 71)

First indexed and scored.

## MCP tools (7)

### `classify_idea` (~522 tokens)

Classify an idea

Classify a product or business idea with fixed rules (no AI model): one of 10 product types and 9 buyer types with the words that matched, a 0 to 100 risk score on each of 10 assumptions (problem, buyer access, willingness to pay, solution fit, feasibility, retention, supply, regulatory, unit economics, operator capacity) with every rule that moved each score, the riskiest assumption written as a sentence a test can prove wrong, red flags, the stage of the Idea to Product method it is in, the build rules for its type, and the cheapest validation test for this week with pass and kill lines. Evidence already gathered (interviews, signups, deposits, payments) lowers risk along a fixed evidence ladder. The same input always gives the same answer.

Input parameters:

- `audience_size` (integer)
- `billing` (string): one_time, monthly, annual or per_use. Default one_time.
- `buyer_type` (string): Override the detected buyer type.
- `current_alternative` (string): What they use or do about the problem today, for example "spreadsheets and texts", "Jobber", or "nothing".
- `days_available` (integer): Days until a decision is needed. Default 7.
- `evidence` (array): What has been learned so far.
- `has_audience` (boolean): True if there is an existing list, following or customer base to test with.
- `has_prototype` (boolean): True if a working version is already in users' hands.
- `idea` (string, required): The idea in plain words: what it does and for whom.
- `price_usd` (number): Intended price in US dollars.
- `product_type` (string): Override the detected product type.
- `reachable_buyers` (integer): How many named buyers can be contacted this week.
- `runs_another_business` (boolean): True if the founder is building this alongside a business they already run.
- `start_date` (string): ISO date the work starts. Default today (UTC).
- `technical_builder` (boolean): False if nobody on the team can build the hardest part. Default true.
- `test_budget_usd` (number): Cash available for the validation test. Default 0.
- `who_pays` (string): The person who pays, by role and niche, for example "owners of 2 to 10 truck plumbing companies".
- `who_uses` (string): The person who uses it, if different from who pays.

### `validation_plan` (~549 tokens)

Plan a validation test

Pick the cheapest test that can prove one assumption about an idea wrong within the days available, from a library of 18 named tests (for example Five Past-Behavior Interviews, Pay Link Pre-sale, Smoke Test Landing Page, Letter of Intent Round, Concierge MVP, Wizard of Oz, Feasibility Spike, Hand-Seeded Supply, Unit Cost Teardown, Regulatory Read and One Call). Tests are filtered by the buyer type, the price, the audience, reachable buyers, budget and whether someone can build, then ranked by strength of evidence against cost and days. Returns the sample, steps, a pass line, a kill line and an inconclusive rule set before the test runs, the decision date, a backup test, and every ruled-out test with the reason. Defaults to the riskiest assumption; pass assumption to choose another.

Input parameters:

- `assumption` (string): The assumption to test. Default: the riskiest one the classifier finds.
- `audience_size` (integer)
- `billing` (string): one_time, monthly, annual or per_use. Default one_time.
- `buyer_type` (string): Override the detected buyer type.
- `current_alternative` (string): What they use or do about the problem today, for example "spreadsheets and texts", "Jobber", or "nothing".
- `days_available` (integer): Days until a decision is needed. Default 7.
- `evidence` (array): What has been learned so far.
- `has_audience` (boolean): True if there is an existing list, following or customer base to test with.
- `has_prototype` (boolean): True if a working version is already in users' hands.
- `idea` (string, required): The idea in plain words: what it does and for whom.
- `price_usd` (number): Intended price in US dollars.
- `product_type` (string): Override the detected product type.
- `reachable_buyers` (integer): How many named buyers can be contacted this week.
- `runs_another_business` (boolean): True if the founder is building this alongside a business they already run.
- `start_date` (string): ISO date the work starts. Default today (UTC).
- `technical_builder` (boolean): False if nobody on the team can build the hardest part. Default true.
- `test_budget_usd` (number): Cash available for the validation test. Default 0.
- `who_pays` (string): The person who pays, by role and niche, for example "owners of 2 to 10 truck plumbing companies".
- `who_uses` (string): The person who uses it, if different from who pays.

### `cut_mvp` (~237 tokens)

Cut an MVP

Sort a feature list into must, should and not now using 15 explicit rules on each feature's tags (core_job, revenue, compliance, trust_safety, onboarding, measurement, retention, integration, automation, admin, growth, analytics, customization, platform, scale, delight), whether it could be done by hand at first, and how many buyers asked for it. Dependencies of a must become must. Should-haves fill the build window by value per effort point in dependency order. Returns each feature with its tier, the rule and the reason, effort totals against capacity, and when the must-haves do not fit, the specific cuts that would make them fit. Rejects duplicate ids, unknown dependencies and cycles with the chain named.

Input parameters:

- `build_weeks` (integer): Build window in weeks. Default 6.
- `builders` (integer): People building in parallel. Default 1.
- `charge_at_launch` (boolean): True if buyers pay from launch. Default true.
- `features` (array, required)
- `points_per_week` (number): Effort points one builder clears in a week. Default 5.

### `sequence_build` (~368 tokens)

Sequence the build

Turn a feature list with dependencies into a dated build plan: applies the MVP cut, orders tasks by dependency, schedules them across the given number of builders on working days (weekends skipped), computes the critical path and each task's slack, adds the method's own tasks (record the success metric, take payment, launch kit, Hand Off) where missing, and dates the milestones: first core job end to end, MVP in real users' hands, launch, success metric review, and Hand Off. Every plan carries a success metric and a review date; a default per product type is used and flagged when none is given.

Input parameters:

- `build_weeks` (integer): Build window in weeks. Default 6.
- `builders` (integer): People building in parallel. Default 1.
- `charge_at_launch` (boolean): True if buyers pay from launch. Default true.
- `features` (array, required)
- `include_method_tasks` (boolean): Add the method's own tasks: metric recording, payment, launch kit and Hand Off. Default true.
- `points_per_week` (number): Effort points one builder clears in a week. Default 5.
- `product_type` (string): Used for the default success metric when none is given.
- `scope` (string): "mvp": must-haves only. "launch" (default): must-haves plus should-haves that fit the window. "all": everything.
- `start_date` (string): ISO date the build starts. Default today (UTC). Weekends are skipped.
- `success_metric` (object): The number that decides success, its target, and how many days after launch to read it.
- `validate_first_days` (integer): Working days of validation before the build starts. Default 0.

### `kill_or_continue` (~199 tokens)

Kill or continue

Make a push, iterate, park or kill call on 1 to 12 products from their metrics (target, actual, kill line, must-hit), evidence, stage, review date, last activity, and monthly revenue and cost, using 10 named decision rules: a must-hit metric past its kill line on the review date kills; a weighted score under 30 on the review date kills; more than 45 days idle parks; revenue under cost and falling kills or forces a price or cost change; 80 or more with the stage gate evidence pushes. Returns each call with its score, rule, reason, next action, next review date and what would flip it, then portfolio notes. Money and time already spent are recorded and deliberately ignored.

Input parameters:

- `as_of` (string): Review as of this date. Default today (UTC).
- `builders` (integer): People available to build across the portfolio.
- `products` (array, required)

### `build_scope_and_sequence` (~601 tokens)

Write a Scope and Sequence

Run the full Idea to Product method on one idea and its feature list and return a Scope and Sequence plan as a Markdown document, followed by a short JSON summary. The document covers the problem and buyer, the riskiest assumption with its risk table, this week's validation test with pass and kill lines, red flags, the MVP cut (must, should, not now, with reasons), the build sequence with builders and dates, milestones through Hand Off, the launch plan and success metric, kill criteria written before the work, build rules for the product type, and a Hand Off checklist. When there is no commitment-level evidence yet, the build is scheduled to start after the test's decision date.

Input parameters:

- `audience_size` (integer)
- `billing` (string): one_time, monthly, annual or per_use. Default one_time.
- `build_weeks` (integer): Build window in weeks. Default 6.
- `builders` (integer): People building in parallel. Default 1.
- `buyer_type` (string): Override the detected buyer type.
- `charge_at_launch` (boolean): True if buyers pay from launch. Default true.
- `current_alternative` (string): What they use or do about the problem today, for example "spreadsheets and texts", "Jobber", or "nothing".
- `days_available` (integer): Days until a decision is needed. Default 7.
- `evidence` (array): What has been learned so far.
- `features` (array, required)
- `has_audience` (boolean): True if there is an existing list, following or customer base to test with.
- `has_prototype` (boolean): True if a working version is already in users' hands.
- `idea` (string, required): The idea in plain words: what it does and for whom.
- `points_per_week` (number): Effort points one builder clears in a week. Default 5.
- `price_usd` (number): Intended price in US dollars.
- `product_type` (string): Override the detected product type.
- `reachable_buyers` (integer): How many named buyers can be contacted this week.
- `runs_another_business` (boolean): True if the founder is building this alongside a business they already run.
- `scope` (string)
- `start_date` (string): ISO date the work starts. Default today (UTC).
- `success_metric` (object)
- `technical_builder` (boolean): False if nobody on the team can build the hardest part. Default true.
- `test_budget_usd` (number): Cash available for the validation test. Default 0.
- `title` (string)
- `who_pays` (string): The person who pays, by role and niche, for example "owners of 2 to 10 truck plumbing companies".
- `who_uses` (string): The person who uses it, if different from who pays.

### `explain_method` (~124 tokens)

Explain the method

Return one of the method's reference tables: the four stages and their exit gates, the 10 assumptions, the evidence ladder, the 18 validation tests, the MVP cut rules, the feature tags, the 10 product types with their risk priors and build rules, the 9 buyer types, the decision rules, or the risk scoring rules. Static reference, no computation on user data.

Input parameters:

- `topic` (string, required): stages, assumptions, evidence_ladder, validation_tests, mvp_rules, feature_tags, product_types, buyer_types, decision_rules or risk_rules.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-modernmustardseed-idea-sequencer/idea-sequencer#diagnostics

## Score history

- 2026-10-22: 75
- 2026-10-21: 75
- 2026-10-20: 74
- 2026-10-19: 74
- 2026-10-18: 73
- 2026-10-17: 73
- 2026-10-16: 72
- 2026-10-15: 72
- 2026-10-14: 72
- 2026-10-13: 71
- 2026-10-12: 71

## Common questions

### What is the Idea to Product Sequencer MCP server?

Idea to Product Sequencer is an MCP server listed in the public MCP registry as com.modernmustardseed/idea-sequencer. Rule-based product method: scores an idea, finds its riskiest assumption, sequences the build. This page covers its hosted endpoint (https://mcp.modernmustardseed.com/idea-sequencer).

### Is the Idea to Product Sequencer MCP server safe to use?

Idea to Product Sequencer scores 75 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Idea to Product Sequencer MCP server expose?

Idea to Product Sequencer exposes 7 tools: classify_idea, validation_plan, cut_mvp, sequence_build, kill_or_continue, and 2 more. Their descriptions and schemas cost roughly 2,600 tokens of context every time the server is loaded.

### Does the Idea to Product Sequencer MCP server require authentication?

No. We connected to Idea to Product Sequencer without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Idea to Product Sequencer MCP server still maintained?

Idea to Product Sequencer is still listed as active in the MCP registry. We last reached this channel on 22 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://mcp.modernmustardseed.com/idea-sequencer
- Website: https://mcp.modernmustardseed.com/docs/idea-sequencer
- Changelog RSS feed: https://verifymcp.io/servers/com-modernmustardseed-idea-sequencer/idea-sequencer.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-modernmustardseed-idea-sequencer/idea-sequencer.json
- HTML version of this page: https://verifymcp.io/servers/com-modernmustardseed-idea-sequencer/idea-sequencer