# io.github.inity13/scenariosim-mcp (remote · scenariosim-mcp.pages.dev)

Deterministic what-if & scenario simulation for AI agents: projections, sensitivity & break-even.

- Trust score: 66/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-20

## Components

- remote · `scenariosim-mcp.pages.dev`: 66/100 (this document), [markdown](https://verifymcp.io/servers/inity13-scenariosim-mcp/scenariosim-mcp.md), [page](https://verifymcp.io/servers/inity13-scenariosim-mcp/scenariosim-mcp)
- npm · `scenariosim-mcp`: 67/100, [markdown](https://verifymcp.io/servers/inity13-scenariosim-mcp/scenariosim-mcp-2.md), [page](https://verifymcp.io/servers/inity13-scenariosim-mcp/scenariosim-mcp-2)

## Channel facts

- Endpoint: `https://scenariosim-mcp.pages.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.2`

## 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-08-20.

- **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 6 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**: 67/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1536 tokens (~256/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 30/100
  - Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http inity13-scenariosim-mcp https://scenariosim-mcp.pages.dev/mcp
```

### Codex

```toml
[mcp_servers.inity13-scenariosim-mcp]
url = "https://scenariosim-mcp.pages.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "inity13-scenariosim-mcp": {
      "type": "remote",
      "url": "https://scenariosim-mcp.pages.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add inity13-scenariosim-mcp --url https://scenariosim-mcp.pages.dev/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  inity13-scenariosim-mcp:
    url: "https://scenariosim-mcp.pages.dev/mcp"
```

### Other

```json
{
  "mcpServers": {
    "inity13-scenariosim-mcp": {
      "type": "http",
      "url": "https://scenariosim-mcp.pages.dev/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-08-20 (score 66, +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-08-18 (score 65, +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-08-16 (score 64, +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-08-14 (score 63, +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-08-12 (score 62, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-08-11 (score 61)

First indexed and scored.

## MCP tools (6)

### `run_scenario` (~373 tokens)

Main simulation tool. Run a deterministic what-if projection from a pre-built template (saas_growth, pricing_change, churn_impact, cost_reduction, hiring_plan, cash_runway, unit_economics, marketing_funnel, compound_growth) OR a free-form 'metrics' model. Returns period-by-period projections, headline key_results, the exact assumptions used (with defaults filled in), the methodology, notes, and a plain-language explanation. Pass 'template' + 'inputs' (assumptions), plus optional 'horizon' and 'period_label'. 100% deterministic (40-digit decimal math).

Input parameters:

- `horizon` (integer): Number of periods to project forward (1..1200). Default depends on template (usually 12).
- `inputs` (object): Scenario assumptions as {name: value}. Which keys are valid depends on the template (call list_templates). Unlisted keys fall back to documented defaults; unknown keys are ignored and reported in not…
- `metrics` (array): For a CUSTOM free-form scenario (template omitted or 'custom'): a list of independently-growing metrics. Each: {name, start, growth_rate (per period, default 0), mode: 'compound' (default) | 'linear'…
- `period_label` (string): Label for each period; also sets annualization (periods/year).
- `template` (string): Pre-built scenario template id: saas_growth, pricing_change, churn_impact, cost_reduction, hiring_plan, cash_runway, unit_economics, marketing_funnel, compound_growth (aliases like 'saas','pricing','…

### `sensitivity_analysis` (~475 tokens)

Vary one or more input assumptions and show the impact on a target output metric (one-at-a-time sensitivity). Provide 'template', the input to sweep via 'variable' (or 'variables' array), and 'target_metric' (defaults to the template's primary output). Control the sweep with 'variation' (fractional +/- around the baseline, default 0.2), 'steps' (default 5), or explicit 'values' / 'min'+'max'. Returns per-variable sweeps, an elasticity estimate, the output range, and a ranking of the most influential inputs.

Input parameters:

- `horizon` (integer): Number of periods to project forward (1..1200). Default depends on template (usually 12).
- `inputs` (object): Scenario assumptions as {name: value}. Which keys are valid depends on the template (call list_templates). Unlisted keys fall back to documented defaults; unknown keys are ignored and reported in not…
- `max` (number): Sweep upper bound (with 'min').
- `min` (number): Sweep lower bound (with 'max').
- `period_label` (string): Label for each period; also sets annualization (periods/year).
- `steps` (integer): Number of sweep points per variable (2-200).
- `target_metric` (string): Output metric to track (see a template's 'outputs' via list_templates). Defaults to the template's primary output.
- `template` (string, required): Pre-built scenario template id: saas_growth, pricing_change, churn_impact, cost_reduction, hiring_plan, cash_runway, unit_economics, marketing_funnel, compound_growth (aliases like 'saas','pricing','…
- `values` (array): Explicit sweep values for a single 'variable'.
- `variable` (string): A single input name to sweep.
- `variables` (array): Multiple inputs to sweep (one at a time). Each: {name, variation?|values?|min?+max?, steps?}.
- `variation` (number): Fractional sweep around the baseline (0<v<=1). 0.2 = +/-20%.

### `break_even` (~375 tokens)

Solve for the input value required to make an output metric hit a target value (deterministic bisection root-finding). Provide 'template', 'solve_for' (the input to solve), 'target_metric' (defaults to the primary output), and 'target_value'. Optionally pass 'bounds' [low, high] to constrain the search. Returns the required input value, the change from baseline, the achieved metric, and the residual. Assumes the metric is monotonic in the solved input over the range.

Input parameters:

- `bounds` (array): Optional [low, high] search range for the solved input. Auto-derived + expanded if omitted.
- `horizon` (integer): Number of periods to project forward (1..1200). Default depends on template (usually 12).
- `inputs` (object): Scenario assumptions as {name: value}. Which keys are valid depends on the template (call list_templates). Unlisted keys fall back to documented defaults; unknown keys are ignored and reported in not…
- `period_label` (string): Label for each period; also sets annualization (periods/year).
- `solve_for` (string, required): Name of the input variable to solve for.
- `target_metric` (string): Output metric to hit (defaults to the template's primary output).
- `target_value` (number, required): The value the target_metric should reach.
- `template` (string, required): Pre-built scenario template id: saas_growth, pricing_change, churn_impact, cost_reduction, hiring_plan, cash_runway, unit_economics, marketing_funnel, compound_growth (aliases like 'saas','pricing','…

### `compare_scenarios` (~224 tokens)

Run 2-3 scenarios and compare their key_results side by side, with deltas against the first (baseline) scenario. Provide a 'scenarios' array where each entry is {name?, template, inputs} (each may set its own horizon, or pass a shared top-level 'horizon'). Optionally rank on 'compare_metric' with 'goal' ('max' default | 'min') to pick a winner, and set include_projections:true to also return per-period series.

Input parameters:

- `compare_metric` (string): Metric to rank scenarios on (optional).
- `goal` (string): Whether higher (max) or lower (min) is better for compare_metric.
- `horizon` (integer): Optional shared horizon applied to scenarios that don't set their own.
- `include_projections` (boolean): Include each scenario's full per-period projections.
- `scenarios` (array, required): 2-3 scenarios to compare. Each: {name?, template, inputs, horizon?, period_label?} or {name?, metrics:[...]} for a custom model.

### `list_templates` (~60 tokens)

Discovery tool: list every pre-built scenario template (id, label, category, description, primary output, documented inputs with defaults/units, and available output metrics), plus how to run a custom free-form scenario and the supported period labels. No required parameters.

### `health_check` (~29 tokens)

Server health, version, and capabilities (tools, templates, period labels, max horizon). No parameters.

## Diagnostics

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

## Score history

- 2026-08-20: 66
- 2026-08-19: 65
- 2026-08-18: 65
- 2026-08-17: 64
- 2026-08-16: 64
- 2026-08-15: 63
- 2026-08-14: 63
- 2026-08-13: 62
- 2026-08-12: 62
- 2026-08-11: 61

## Links

- Remote endpoint: https://scenariosim-mcp.pages.dev/mcp
- Repository: https://github.com/inity13/scenariosim-mcp
- Changelog RSS feed: https://verifymcp.io/servers/inity13-scenariosim-mcp/scenariosim-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/inity13-scenariosim-mcp/scenariosim-mcp.json
- HTML version of this page: https://verifymcp.io/servers/inity13-scenariosim-mcp/scenariosim-mcp