io.github.inity13/scenariosim-mcp
REMOTE · SCENARIOSIM-MCP.PAGES.DEV · 2 COMPONENTS · SCANNED OCT 4
Deterministic what-if & scenario simulation for AI agents: projections, sensitivity & break-even.
Available components
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 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. 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 Usability67
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.inity13/scenariosim-mcp server?
io.github.inity13/scenariosim-mcp is a hosted endpoint at https://scenariosim-mcp.pages.dev/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 · scenariosim-mcp.pages.dev
claude mcp add --transport http inity13-scenariosim-mcp 'https://scenariosim-mcp.pages.dev/mcp'
{
"mcpServers": {
"inity13-scenariosim-mcp": {
"url": "https://scenariosim-mcp.pages.dev/mcp"
}
}
} {
"servers": {
"inity13-scenariosim-mcp": {
"type": "http",
"url": "https://scenariosim-mcp.pages.dev/mcp"
}
}
} [mcp_servers.inity13-scenariosim-mcp] url = "https://scenariosim-mcp.pages.dev/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"inity13-scenariosim-mcp": {
"type": "remote",
"url": "https://scenariosim-mcp.pages.dev/mcp",
"enabled": true
}
}
} openclaw mcp add inity13-scenariosim-mcp --url 'https://scenariosim-mcp.pages.dev/mcp' --transport streamable-http
mcp_servers:
inity13-scenariosim-mcp:
url: "https://scenariosim-mcp.pages.dev/mcp" {
"McpServers": {
"inity13-scenariosim-mcp": {
"Transport": "http",
"Url": "https://scenariosim-mcp.pages.dev/mcp"
}
}
} assistant mcp add inity13-scenariosim-mcp -t streamable-http -u 'https://scenariosim-mcp.pages.dev/mcp'
{
"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.
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.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 10 Sept 26 +1
- Stability: 0.97 → pass security
- 8 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 6 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 12 Aug 26 0
- Stability: unverified → 0.03 ▲ functional
- 11 Aug 26 0
First indexed and scored.
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 5 Oct 2026 · Probed https://scenariosim-mcp.pages.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=scenariosim-mcp.pages.dev | CN=WE1,O=Google Trust Services,C=US | 11 Aug 2026 | 9 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | a7821da95afa33e0e1e265a965d990c |
| SANs: scenariosim-mcp.pages.dev, *.scenariosim-mcp.pages.dev | ||||||
| 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 scenariosim-mcp.pages.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| pages.dev. | absent | 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://scenariosim-mcp.pages.dev/mcp | Verified | 200 | |
| http (plaintext) | http://scenariosim-mcp.pages.dev/mcp | HTTPS enforced | 301 | https://scenariosim-mcp.pages.dev/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 →
break_even ~375
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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 | yes | The value the target_metric should reach. |
| template | string | yes | 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','… |
No output schema declared.
No examples provided.
compare_scenarios ~224
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 2-3 scenarios to compare. Each: {name?, template, inputs, horizon?, period_label?} or {name?, metrics:[...]} for a custom model. |
No output schema declared.
No examples provided.
health_check ~29
Server health, version, and capabilities (tools, templates, period labels, max horizon). No parameters.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_templates ~60
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
run_scenario ~373
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).
| Name | Type | Req | Description |
|---|---|---|---|
| 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','… |
No output schema declared.
No examples provided.
sensitivity_analysis ~475
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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%. |
No output schema declared.
No examples provided.
What is the io.github.inity13/scenariosim-mcp server?
io.github.inity13/scenariosim-mcp is listed in the public MCP registry as io.github.inity13/scenariosim-mcp. Deterministic what-if & scenario simulation for AI agents: projections, sensitivity & break-even. This page covers its hosted endpoint (https://scenariosim-mcp.pages.dev/mcp).
Is the io.github.inity13/scenariosim-mcp server safe to use?
io.github.inity13/scenariosim-mcp scores 77 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 io.github.inity13/scenariosim-mcp server expose?
io.github.inity13/scenariosim-mcp exposes 6 tools: run_scenario, sensitivity_analysis, break_even, compare_scenarios, list_templates, health_check. Their descriptions and schemas cost roughly 1,536 tokens of context every time the server is loaded.
Does the io.github.inity13/scenariosim-mcp server require authentication?
No. We connected to io.github.inity13/scenariosim-mcp without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.inity13/scenariosim-mcp server still maintained?
io.github.inity13/scenariosim-mcp is still listed as active in the MCP registry. We last reached this channel on 4 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.