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.
Available components
Last scanned (12 hours ago)
Scores higher than 46% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Databases
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. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability48
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management50
- Stability observed for 15 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Checks we ran (12)
- TLS certificate
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation 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.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Nov 26 +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.
- 18 Nov 26 +1
- 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 security
- Server version: 0.6.0 → 0.7.0 functional
- Tool “validate_migration_discovery” changed its title: Review migration Discovery risks → Review data migration Discovery risks cosmetic
- 15 Nov 26 +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.
- 13 Nov 26 +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.
- 11 Nov 26 +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.
- 10 Nov 26 0
- Server version: 0.5.0 → 0.6.0 functional
- 9 Nov 26 +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.
- 8 Nov 26 0
- 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 security
- Schema quality: 1150 → 1439 ▼ functional
- Server version: 0.4.0 → 0.5.0 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Probed https://stratus-decide.onrender.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=onrender.com | CN=WE1,O=Google Trust Services,C=US | 19 Nov 2026 | 17 Feb 2027 | ECDSA 256 | ECDSA-SHA256 | 8d72a13c2c41648513b9d014eb5e0339 |
| SANs: onrender.com, *.onrender.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of stratus-decide.onrender.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| onrender.com. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://stratus-decide.onrender.com/mcp | Verified | 200 | |
| http (plaintext) | http://stratus-decide.onrender.com/mcp | HTTPS enforced | 301 | https://stratus-decide.onrender.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
validate_migration_discovery Review data migration Discovery risks ~268
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"}]}]}
| Name | Type | Req | Description |
|---|---|---|---|
| max_risks | integer | – | – |
| submission | – | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| changes | – | yes | Change since the last submission; needs engagement_id. |
| coverage_objects | array | yes | – |
| coverage_project | array | yes | – |
| engagement_id | – | yes | – |
| engine_version | string | yes | – |
| risks | array | yes | Highest severity first. |
| risks_omitted | integer | yes | Lower-severity risks left out by max_risks or the no-key limit. |
| summary | – | yes | – |
No examples provided.
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.
remote · stratus-decide.onrender.com
claude mcp add --transport http stratus-consulting-stratus-decide 'https://stratus-decide.onrender.com/mcp'
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.