SRA-RiskGate MCP Server

What this does

SRA-RiskGate exposes a set of tools to Claude over the Model Context Protocol. After you add it to claude_desktop_config.json (snippet above) and restart Claude Desktop, those tools become callable inside any conversation.

Requirements

This server needs the following environment variables to be set before it can run:

SRA_BASE_URL
SRA_MODEL
SRA_MAX_AMOUNT
SRA_KNOWN_RECIPIENTS
SRA_KNOWN_RECIPIENTS_FILE
SRA_BLOCKED_ADDRESSES
SRA_BLOCKED_ADDRESSES_FILE
SRA_MAX_AUTH_VALIDITY_SECONDS
SRA_API_KEY
SRA_TIMEOUT
SRA_DEPEG_HOLD_PCT
SRA_DEPEG_REJECT_PCT
SRA_MAX_GATEWAY_VALIDITY_SECONDS
SRA_CIRCLE_WALLETS
SRA_CIRCLE_USDC_TOKEN_IDS
SRA_EXPECTED_DELEGATES
SRA_EXPECTED_DELEGATES_FILE

Set these via the env object in your MCP config (see claude_desktop_config.json snippet above).

How do I install SRA-RiskGate?

Run the Claude Code command in the install section to add SRA-RiskGate to Claude Code, or copy the ready-made config for your client from the install section on this page. Restart your client afterwards and the tools appear in your next conversation.

Which clients work with SRA-RiskGate?

This page carries setup and config for Claude Code, Claude Desktop, Cursor and VS Code. Any other MCP client that accepts a standard server config can connect to SRA-RiskGate as well.

Does SRA-RiskGate need an API key?

Yes. Before it can run, set these environment variables: SRA_BASE_URL, SRA_MODEL, SRA_MAX_AMOUNT, SRA_KNOWN_RECIPIENTS, SRA_KNOWN_RECIPIENTS_FILE, SRA_BLOCKED_ADDRESSES, SRA_BLOCKED_ADDRESSES_FILE, SRA_MAX_AUTH_VALIDITY_SECONDS, SRA_API_KEY, SRA_TIMEOUT, SRA_DEPEG_HOLD_PCT, SRA_DEPEG_REJECT_PCT, SRA_MAX_GATEWAY_VALIDITY_SECONDS, SRA_CIRCLE_WALLETS, SRA_CIRCLE_USDC_TOKEN_IDS, SRA_EXPECTED_DELEGATES, SRA_EXPECTED_DELEGATES_FILE. They go in the env block of your MCP config.