Systemic Risk Contagion

Name: Systemic Risk Contagion
Author: apifyforge

@apifyforge

Repository Homepage Documentation

About Systemic Risk Contagion

Systemic risk contagion analysis for financial networks, delivered as an MCP server your AI agent connects to directly.

Basic information

Config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "systemic-risk-contagion-mcp": {
      "url": "https://ryanclinton--systemic-risk-contagion-mcp.apify.actor/mcp"
    }
  }
}

Tools

No tools detected

We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.

Overview

What is Systemic Risk Contagion?

Systemic Risk Contagion is an MCP server for financial network contagion analysis. It integrates 16 public data sources to construct 4‑layer multiplex financial networks and runs algorithms such as DebtRank, Eisenberg‑Noe clearing, multivariate Hawkes processes, and supra‑adjacency tensor spectral decomposition. It is designed for financial stability professionals, regulators, researchers, and risk managers who need to quantify systemic risk without proprietary data or custom network code.

How to use Systemic Risk Contagion?

Add the server to an MCP‑compatible client (Claude Desktop, Cursor, Windsurf, Cline) by providing the URL https://systemic-risk-contagion-mcp.apify.actor/mcp and your Apify API token in the Authorization: Bearer header. Then issue natural‑language queries such as “Compute DebtRank for the US banking sector” to trigger one of the eight available tools (e.g., compute_debtrank, simulate_cascade_failure, generate_stability_report). Each tool call costs $0.045.

Key features of Systemic Risk Contagion

Integrates 16 publicly available data sources simultaneously.
Constructs 6‑layer multiplex networks with inter‑layer coupling tensors.
Implements four published mathematical frameworks for systemic risk.
Always‑on standby via Apify with no cold‑start delays.
Spend controls per session to cap runaway agent costs.
Scheduled recurring stability monitoring and webhook alerts.

Use cases of Systemic Risk Contagion

G‑SIB and D‑SIB identification using DebtRank scores.
Stress testing and resolution planning with cascade failure simulation.
Criticality regime assessment via supra‑adjacency eigenanalysis.
Temporal stress event monitoring using Hawkes branching ratios.
Sanctions compliance stress testing with BFS propagation.
Cross‑layer contagion channel mapping via tensor decomposition.

FAQ from Systemic Risk Contagion

What data sources does Systemic Risk Contagion use?

The server queries 16 sources including OpenCorporates, SEC EDGAR, FDIC Bank Search, FRED Economic Data, World Bank Indicators, OFAC Sanctions, and more, all fetched in parallel per request.

Do I need an Apify account to use Systemic Risk Contagion?

Yes. You need an Apify API token, available from your Apify account settings. The Apify Free plan includes $5 of monthly credits, sufficient for many analyses at $0.045 per tool call.

How does Systemic Risk Contagion handle authentication?

Connect via any MCP client by supplying the server URL and an Authorization: Bearer YOUR_APIFY_TOKEN header. The server runs on Apify’s infrastructure.

What are the system requirements for Systemic Risk Contagion?

No local installation is needed; the server runs persistently on Apify. You only need an MCP‑compatible client and an internet connection.

Are there any limits on queries?

Each tool call costs $0.045. Spend controls can be set per session to prevent runaway costs. More specific entity names in the query produce denser networks, but all 16 sources are always queried.