Donets Risk Intelligence MCP

Connect peer-reviewed AI risk intelligence to Claude, Codex, Cursor, VS Code, or any MCP-compatible client.

Quick setup

  1. 1
    Add to your client

    Choose your client and copy the matching configuration.

  2. 2
    Restart and verify

    Restart once, sign in, and confirm the MCP tool appears.

  3. 3
    Authentication options

    Use native OAuth when your client supports it, or `mcp-remote` when it needs a browser bridge.

1

Add to your client

Claude Desktop

Open your config file:

  • ~/Library/Application Support/Claude/claude_desktop_config.json

Add (or merge into your existing config):

{
  "mcpServers": {
    "donets-risk-intelligence": {
      "type": "http",
      "url": "https://mcp.donets.org"
    }
  }
}

Claude Code

Run this in your terminal:

claude mcp add --transport http donets-risk-intelligence https://mcp.donets.org
Alternative: use mcp-remote

Runs as a local bridge and handles sign-in through your browser:

{
  "mcpServers": {
    "donets-risk-intelligence": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://mcp.donets.org"]
    }
  }
}

Run this in your terminal:

codex mcp add donets-risk-intelligence --url https://mcp.donets.org

Or configure manually — add to ~/.codex/config.json:

{
  "mcpServers": {
    "donets-risk-intelligence": {
      "type": "http",
      "url": "https://mcp.donets.org"
    }
  }
}
Alternative: use mcp-remote

Runs as a local bridge and handles sign-in through your browser:

{
  "mcpServers": {
    "donets-risk-intelligence": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://mcp.donets.org"]
    }
  }
}

Add to .cursor/mcp.json in your project root:

{
  "mcpServers": {
    "donets-risk-intelligence": {
      "type": "http",
      "url": "https://mcp.donets.org"
    }
  }
}

Create or open .vscode/mcp.json in your workspace root and add:

{
  "servers": {
    "donets-risk-intelligence": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://mcp.donets.org"]
    }
  }
}

mcp-remote handles OAuth in your browser. You'll see a link in the terminal on first run — open it to sign in.

Alternative: use native HTTP transport

VS Code also supports native HTTP transport. Use this if you'd rather not install mcp-remote:

{
  "servers": {
    "donets-risk-intelligence": {
      "type": "http",
      "url": "https://mcp.donets.org"
    }
  }
}

Or add to user settings (Cmd+Shift+P → Preferences: Open User Settings (JSON)):

{
  "mcp": {
    "servers": {
      "donets-risk-intelligence": {
        "type": "http",
        "url": "https://mcp.donets.org"
      }
    }
  }
}

Use mcp-remote to connect any MCP-compatible client:

npx -y mcp-remote https://mcp.donets.org
Setup for Windsurf

Open Windsurf Settings → MCP and add:

{
  "mcpServers": {
    "donets-risk-intelligence": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://mcp.donets.org"]
    }
  }
}
Setup for Zed

Add to your Zed settings.json:

{
  "context_servers": {
    "donets-risk-intelligence": {
      "command": {
        "path": "npx",
        "args": ["-y", "mcp-remote", "https://mcp.donets.org"]
      }
    }
  }
}

Clients with native Streamable HTTP support can use "type": "http" directly — no mcp-remote needed.

2

Restart and verify

Restart your client. On first use, sign in in your browser or terminal, approve the connection, and you're ready.

If this MCP server was already configured and OAuth still fails, remove and re-add the server entry once to refresh cached discovery metadata.

Donets Risk Intelligence MCP appears in your client's MCP tools list

Try a prompt like:

"What are the top risks for an LLM agent with tool access to customer data?"

You'll get scored risks with links to papers, citations, and authors.

You're connected.

Donets Risk Intelligence MCP is now available in every conversation. Browse the risk database →

Authentication options

Donets Risk Intelligence MCP uses strict per-server OAuth for MCP:

  • OAuth 2.1 with PKCE — your client handles sign-in automatically. Every MCP request uses a bearer access token, and 24-hour access tokens refresh silently for 90 days.
  • mcp-remote — a temporary bridge that manages the same OAuth flow in your browser when your client does not support it natively.

API keys are still available for the direct REST API, but MCP clients should sign in with OAuth. Connected clients appear in your Access settings. Revoke access anytime.