Is the Inity13 Scenariosim MCP server down?

mcp-registry/io.github.inity13/scenariosim-mcp · v1.0.0-edge

Also listed as github/inity13/scenariosim-mcp, glama/inity13/scenariosim-mcp

healthy
Last checked 2026-10-18 04:28 UTC · handshake 200ms

As of 2026-10-18 04:28 UTC, the Inity13 Scenariosim MCP server is up with a Glimind reliability score of 96/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 2 outages in 90 days, with a median recovery of 25.7 hours.

uptime (30d checks)
100%
checks observed
3,644
outages (90d)
2
tools
6

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

Install Inity13 Scenariosim MCP server

Add to Cursor Add to VS Code

Claude Code

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

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "inity13-scenariosim-mcp-server": {
      "type": "http",
      "url": "https://scenariosim-mcp.pages.dev/mcp"
    }
  }
}

Third-party server, listed as discovered. Review its source before installing.

Agent-readiness: B (82/100)

B (82/100): 0 error(s), 2 warning(s) across 6 tool(s); ~2,765 tokens of tool definitions.
Scores higher than 40% of 15,354 MCP servers Glimind has audited.
Its tool list costs an agent ~2,765 tokens per session — more than 50% of servers.
82 → 82 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions100
Safety hints7
Token cost100
Client compatibility70
Protocol100
Reliability100
Stability100

What to fix (3)

6 of 6 tool(s) carry no readOnlyHint/destructiveHint annotations.

Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →

Tools: break_even, compare_scenarios, health_check, list_templates, run_scenario and 1 more

1 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.

Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →

Tools: run_scenario

No tool declares an outputSchema.

Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →

Auto-fix: 4 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.inity13%2Fscenariosim-mcp/fixes

compare_scenarios 1 change
{
  "name": "compare_scenarios",
  "description": "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.",
  "inputSchema": {
    "type": "object",
    "required": [
      "scenarios"
    ],
    "properties": {
      "goal": {
        "enum": [
          "max",
          "min"
        ],
        "type": "string",
        "default": "max",
        "description": "Whether higher (max) or lower (min) is better for compare_metric."
      },
      "horizon": {
        "type": "integer",
        "description": "Optional shared horizon applied to scenarios that don't set their own."
      },
      "scenarios": {
        "type": "array",
        "items": {
          "type": "object",
          "properties": {
            "name": {
              "type": "string"
            },
            "inputs": {
              "type": "object",
              "description": "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 notes. You may also pass assumptions at the top level."
            },
            "horizon": {
              "type": "integer",
              "default": 12,
              "description": "Number of periods to project forward (1..1200). Default depends on template (usually 12)."
            },
            "metrics": {
              "type": "array",
              "items": {
                "type": "object",
                "required": [
                  "name",
                  "start"
                ],
                "properties": {
                  "mode": {
                    "enum": [
                      "compound",
                      "linear"
                    ],
                    "type": "string",
                    "default": "compound"
                  },
                  "name": {
                    "type": "string"
                  },
                  "start": {
                    "type": "number"
                  },
                  "growth_rate": {
                    "type": "number"
                  }
                }
              },
              "description": "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'}."
            },
            "template": {
              "type": "string",
              "description": "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','runway','ltv' also resolve). Omit (or use 'custom') to run a free-form 'metrics' projection."
            },
            "period_label": {
              "enum": [
                "day",
                "week",
                "month",
                "quarter",
                "year"
              ],
              "type": "string",
              "default": "month",
              "description": "Label for each period; also sets annualization (periods/year)."
            }
          }
        },
        "description": "2-3 scenarios to compare. Each: {name?, template, inputs, horizon?, period_label?} or {name?, metrics:[...]} for a custom model."
      },
      "compare_metric": {
        "type": "string",
        "description": "Metric to rank scenarios on (optional)."
      },
      "include_projections": {
        "type": "boolean",
        "default": false,
        "description": "Include each scenario's full per-period projections."
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}
health_check 1 change
{
  "name": "health_check",
  "description": "Server health, version, and capabilities (tools, templates, period labels, max horizon). No parameters.",
  "inputSchema": {
    "type": "object",
    "properties": {}
  },
  "annotations": {
    "readOnlyHint": true
  }
}
list_templates 1 change
{
  "name": "list_templates",
  "description": "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.",
  "inputSchema": {
    "type": "object",
    "properties": {}
  },
  "annotations": {
    "readOnlyHint": true
  }
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.github.inity13/scenariosim-mcp"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/io.github.inity13/scenariosim-mcp"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

Markdown
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.inity13%2Fscenariosim-mcp.svg)](https://glimind.com/server/mcp-registry%2Fio.github.inity13%2Fscenariosim-mcp?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fio.github.inity13%2Fscenariosim-mcp?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.inity13%2Fscenariosim-mcp.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.inity13%2Fscenariosim-mcp.svg
   :target: https://glimind.com/server/mcp-registry%2Fio.github.inity13%2Fscenariosim-mcp?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:a2472ecdded42828…, first seen 2026-10-17, included at leaf 14573 of 20,335. Version history · verify what your client received.

Tools (6)

Compare: most reliable data servers · most reliable other servers · most reliable knowledge servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Inity13 Scenariosim MCP server down right now?

As of 2026-10-18 04:28 UTC, the Inity13 Scenariosim MCP server is up with a Glimind reliability score of 96/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 2 outages in 90 days, with a median recovery of 25.7 hours.

How many tools does Inity13 Scenariosim MCP server provide?

Inity13 Scenariosim MCP server advertises 6 tools, including break_even, compare_scenarios, health_check, list_templates, run_scenario.

How do I install Inity13 Scenariosim MCP server?

Point your MCP client at this streamable-http endpoint: https://scenariosim-mcp.pages.dev/mcp

Is the Inity13 Scenariosim MCP server safe to connect to an AI agent?

Glimind scanned all 6 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Inity13 Scenariosim MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.