IriusRisk MCP Registry

This registry contains MCP (Model Context Protocol) server configurations for IriusRisk CLI integrations.

Available Servers

1. iriusrisk-cli (Stdio Mode)

For: Local AI assistants (Claude Desktop, Cursor, etc.)

Transport: stdio (standard input/output)

Installation:

pip install iriusrisk-cli

MCP Configuration:

{
  "mcpServers": {
    "iriusrisk-cli": {
      "command": "iriusrisk",
      "args": ["mcp"]
    }
  }
}

Setup:

1. Install the CLI
2. Configure credentials via iriusrisk config set-api-key or environment variables
3. Add the MCP configuration to your AI assistant's config file
4. Restart your AI assistant

---

2. iriusrisk-cli-http (HTTP Server Mode)

For: Remote AI assistants, distributed teams, shared infrastructure

Transport: HTTP (streamable-http)

Installation:

pip install iriusrisk-cli

Start Server:

# Local development
iriusrisk mcp --server --port 8000

# Production (behind reverse proxy)
iriusrisk mcp --server --host 0.0.0.0 --port 8000

MCP Configuration:

{
  "mcpServers": {
    "iriusrisk-http": {
      "url": "http://localhost:8000/mcp",
      "headers": {
        "X-IriusRisk-API-Key": "YOUR_API_KEY_HERE",
        "X-IriusRisk-Hostname": "https://your-instance.iriusrisk.com"
      }
    }
  }
}

Required Headers:

• X-IriusRisk-API-Key: Your IriusRisk API key (get from User Settings > API Tokens)
• X-IriusRisk-Hostname: Your IriusRisk instance URL

Features:

• ✅ Multi-tenant: Each client uses their own credentials
• ✅ Stateless: No local file dependencies
• ✅ Remote access: Run on shared infrastructure
• ✅ HTTPS ready: Deploy behind reverse proxy (nginx, etc.)

Key Differences from Stdio Mode:

Feature	Stdio Mode	HTTP Mode
Access	Local only	Remote capable
State	Filesystem-based	Stateless
Auth	Per-user config	Per-request headers
Project Context	Local .iriusrisk/	Explicit project_id
Tools	All tools	Stateless tools only
Deployment	Single user	Multi-tenant

---

Tools Available

HTTP Mode Tools

• list_projects - Search and list projects
• get_project - Get project details
• get_threats - Retrieve threats as JSON
• get_countermeasures - Retrieve countermeasures as JSON
• import_otm - Import OTM from string content
• update_threat_status - Direct API threat updates
• update_countermeasure_status - Direct API countermeasure updates
• get_diagram - Get base64 encoded diagram
• Plus all shared guidance tools

Stdio Mode Additional Tools

• sync - Download data to local filesystem
• track_threat_update - Track updates locally
• track_countermeasure_update - Track updates locally
• show_diagram - Save diagram to file
• generate_report - Generate and save reports

---

Getting API Credentials

1. Log into your IriusRisk instance
2. Navigate to User Settings > API Tokens
3. Click Create New Token
4. Copy the API key
5. Use in your MCP configuration

---

Support

• Documentation: https://github.com/iriusrisk/iriusrisk_cli
• Issues: https://github.com/iriusrisk/iriusrisk_cli/issues
• License: MIT

---

Version History

v0.2.0 (2025-11-21)

• Added HTTP MCP server mode for remote access
• Multi-tenant support with per-request authentication
• 8 new HTTP-specific stateless tools
• Modular architecture separating stdio and HTTP modes

v0.1.0 (2025-10-20)

• Initial release with stdio mode
• Full threat modeling workflow
• Local filesystem-based operations