# DECIDE: Data Migration Discovery Risk Review (remote · stratus-decide.onrender.com)

Reviews data migration discovery after each iteration: open risks, who to ask next, what changed.

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

## Components

- remote · `stratus-decide.onrender.com`: 64/100 (this document), [markdown](https://verifymcp.io/servers/stratus-consulting-stratus-decide/stratus-decide.md), [page](https://verifymcp.io/servers/stratus-consulting-stratus-decide/stratus-decide)

## Channel facts

- Endpoint: `https://stratus-decide.onrender.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.7.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-11-21.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 1 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - 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**: 48/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1552 tokens (~1552/item across 1 items; 1 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 50/100
  - Stability observed for 15 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 71/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 2 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 DECIDE: Data Migration Discovery Risk Review MCP server?

DECIDE: Data Migration Discovery Risk Review is a hosted endpoint at https://stratus-decide.onrender.com/mcp, 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 stratus-consulting-stratus-decide 'https://stratus-decide.onrender.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "stratus-consulting-stratus-decide": {
      "url": "https://stratus-decide.onrender.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "stratus-consulting-stratus-decide": {
      "type": "http",
      "url": "https://stratus-decide.onrender.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.stratus-consulting-stratus-decide]
url = "https://stratus-decide.onrender.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "stratus-consulting-stratus-decide": {
      "type": "remote",
      "url": "https://stratus-decide.onrender.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add stratus-consulting-stratus-decide --url 'https://stratus-decide.onrender.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  stratus-consulting-stratus-decide:
    url: "https://stratus-decide.onrender.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "stratus-consulting-stratus-decide": {
      "Transport": "http",
      "Url": "https://stratus-decide.onrender.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add stratus-consulting-stratus-decide -t streamable-http -u 'https://stratus-decide.onrender.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "stratus-consulting-stratus-decide": {
      "type": "http",
      "url": "https://stratus-decide.onrender.com/mcp"
    }
  }
}
```

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-11-20 (score 64, +1)

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

### 2026-11-18 (score 63, +1)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “validate_migration_discovery” rewrote its description, which is the text the model reads
- [functional] Server version: 0.6.0 → 0.7.0
- [cosmetic] Tool “validate_migration_discovery” changed its title: Review migration Discovery risks → Review data migration Discovery risks

### 2026-11-15 (score 62, +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-11-13 (score 61, +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-11-11 (score 60, +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-11-10 (score 59, 0)

- [functional] Server version: 0.5.0 → 0.6.0

### 2026-11-09 (score 59, +1)

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

### 2026-11-08 (score 58, 0)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “validate_migration_discovery” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 1150 → 1439
- [functional] Server version: 0.4.0 → 0.5.0

## MCP tools (1)

### `validate_migration_discovery` (~268 tokens)

Review data migration Discovery risks

Review a data 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.", "scope": ["Account", "Contact", "Opportunity"]}, "project_items": [{"category": "process", "question": "Which team runs month-end invoicing in the legacy CRM?", "answer": "Finance operations, from a weekly export.", "source": {"who": "Finance operations lead"}}], "objects": [{"name": "Account", "criticality": "high", "has_hierarchy": true, "items": [{"category": "object_context", "question": "Do regional sales teams use separate Account layouts?", "answer": null}], "flags": [{"description": "Parent hierarchy source not provided", "owner": "Finance"}]}]}

Input parameters:

- `max_risks` (integer)
- `submission` (required)

Output parameters:

- `changes`: Change since the last submission; needs engagement_id.
- `coverage_objects` (array)
- `coverage_project` (array)
- `engagement_id`
- `engine_version` (string)
- `risks` (array): Highest severity first.
- `risks_omitted` (integer): Lower-severity risks left out by max_risks or the no-key limit.
- `summary`

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/stratus-consulting-stratus-decide/stratus-decide#diagnostics

## Score history

- 2026-11-21: 64
- 2026-11-20: 64
- 2026-11-19: 63
- 2026-11-18: 63
- 2026-11-17: 62
- 2026-11-16: 62
- 2026-11-15: 62
- 2026-11-14: 61
- 2026-11-13: 61
- 2026-11-12: 60
- 2026-11-11: 60
- 2026-11-10: 59
- 2026-11-09: 59
- 2026-11-08: 58
- 2026-11-07: 58
- 2026-11-06: 57

## Common questions

### What is the DECIDE: Data Migration Discovery Risk Review MCP server?

DECIDE: Data Migration Discovery Risk Review is an MCP server listed in the public MCP registry as io.github.stratus-consulting/stratus-decide. Reviews data migration discovery after each iteration: open risks, who to ask next, what changed. This page covers its hosted endpoint (https://stratus-decide.onrender.com/mcp).

### Is the DECIDE: Data Migration Discovery Risk Review MCP server safe to use?

DECIDE: Data Migration Discovery Risk Review scores 64 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 DECIDE: Data Migration Discovery Risk Review MCP server expose?

DECIDE: Data Migration Discovery Risk Review exposes 1 tool: validate_migration_discovery. Their descriptions and schemas cost roughly 268 tokens of context every time the server is loaded.

### Does the DECIDE: Data Migration Discovery Risk Review MCP server require authentication?

No. We connected to DECIDE: Data Migration Discovery Risk Review without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the DECIDE: Data Migration Discovery Risk Review MCP server still maintained?

DECIDE: Data Migration Discovery Risk Review is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the DECIDE: Data Migration Discovery Risk Review MCP server?

VerifyMCP ran 12 checks on DECIDE: Data Migration Discovery Risk Review, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about DECIDE: Data Migration Discovery Risk Review: Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://stratus-decide.onrender.com/mcp
- Repository: https://github.com/stratus-consulting/decide-mcp
- Website: https://stratus-decide.onrender.com/docs
- Changelog RSS feed: https://verifymcp.io/servers/stratus-consulting-stratus-decide/stratus-decide.xml
- Changelog JSON feed: https://verifymcp.io/servers/stratus-consulting-stratus-decide/stratus-decide/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/stratus-consulting-stratus-decide/stratus-decide.json
- HTML version of this page: https://verifymcp.io/servers/stratus-consulting-stratus-decide/stratus-decide
