DECIDE: Migration Discovery Risk Review

io.github.stratus-consultingPublished by GitHub account stratus-consultingv0.4.0Updated Nov 7, 2026

Run after each discovery iteration to see what's still uncertain, who to ask next, and what changed.

The publisher's own server: Review Expert

VerifiedStreamable HTTPWeb executableProductivity & WorkflowData & Analytics

Overview

AI-generated overview

A remote risk-review service that takes a migration's discovery findings and returns open risks, highest severity first, each with who to ask next.

What you can do
  • Submit cumulative discovery findings (scope baseline, project questions, investigated objects, out-of-scope discoveries) under one engagement ID
  • Get open risks, gaps and unanswered questions ranked by severity, each with a recommended next step naming who to ask and what to ask
  • See which risks are new, closed or dropped since the previous submission, and per-category coverage as covered, partial, missing or not applicable
  • Flag blockers on objects and mark consent, compliance or legal items that must be confirmed
When to use it
Useful during a data or system migration engagement when discovery runs in iterations and you want a structured list of what is still uncertain and who to follow up with. It is a review aid, not a pass/fail validator, and returns no score.
Requirements
A remote streamable HTTP endpoint; no package, account, API key or header is declared. The assistant must supply structured findings, including a stable engagement_id, and should send the full cumulative set each time. Submissions are capped (up to 300 items per the instructions).
Before you install
Findings are sent to a third-party hosted service, so send metadata and summaries rather than customer records, credentials, personal information or proprietary datasets. Identify sources by role, not name. Results only reflect what was submitted: anything omitted is treated as gone, so a risk can appear closed without being resolved. Nothing is monitored between calls.

Installation

In SourceWeft

  1. Open DECIDE: Migration Discovery Risk Review in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.stratus-consulting%2Fstratus-decide/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "decide-migration-discovery-risk-review": {
      "type": "http",
      "url": "https://stratus-decide.onrender.com/mcp"
    }
  }
}

Tools

1

validate_migration_discovery

Review migration Discovery risks

Review a migration's current discovery findings and return the open risks, highest severity first, each with a next step: who to ask and what to ask. Call after each discovery iteration with the full, cumulative findings (open questions with answer null) and the same engagement_id, to see which risks are new, still open or closed. Minimal example submission: {"engagement_id": "acme-crm-2026", "sow": {"use_case": "Consolidate two legacy CRMs into one Salesforce org.", "sold_scope": ["Account", "Contact", "Opportunity"]}, "project_items": [{"category": "purpose_and_success", "question": "Why now?", "answer": "Legacy CRM contract ends in Q2.", "source": {"who": "VP Sales"}}], "objects": [{"name": "Account", "criticality": "high", "has_hierarchy": true, "items": [{"category": "meaning_and_use", "question": "What does Account mean?", "answer": null}], "flags": [{"description": "Parent hierarchy source not provided", "owner": "Finance"}]}]}

Parametersmax_riskssubmissionrequired

Version history

1
  1. v0.4.0LatestNov 7, 2026

Score

83% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.

Other Review integrations