sra-riskgate-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SRA_MODEL | No | Model name on the OpenAI-compatible endpoint. | sriram1983007/sra-riskgate |
| SRA_API_KEY | No | API key, if the endpoint needs one. | none |
| SRA_TIMEOUT | No | Seconds to wait for the model. | 120 |
| SRA_BASE_URL | No | OpenAI-compatible endpoint serving the model (Ollama, llama.cpp, vLLM). | http://localhost:11434/v1 |
| SRA_MAX_AMOUNT | No | Rule ceiling in USDC; larger payments are held. | 1000 |
| SRA_DEPEG_HOLD_PCT | No | USDC depeg hold threshold in percent. | 1 |
| SRA_DEPEG_REJECT_PCT | No | USDC depeg reject threshold in percent. | 5 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| check_address_sanctionsA | Check addresses against the OFAC SDN list before dealing with them, for example before creating a payment. |
| check_payment_rulesA | Instant deterministic checks for a USDC payment, before sending it. |
| check_x402_paymentA | Check an x402 payment requirement BEFORE signing it. |
| check_payment_with_modelA | Full risk review of a stablecoin payment by the SRA-RiskGate-4B model. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
check_address_sanctions is clearly distinct (pure address screening), and check_x402_payment targets a specific x402 flow. However, check_payment_rules and check_payment_with_model both pre-screen stablecoin payments and could be confused; the deterministic-vs-model distinction helps, but an agent must read carefully to pick correctly, and there is overlap in the OFAC/depeg logic across three of the four tools.
All four tools use the same check_<subject> snake_case pattern (check_payment_rules, check_address_sanctions, check_x402_payment, check_payment_with_model). No camelCase mixing or inconsistent verb styles, so intent is predictable from the name.
Four tools is a tight, well-scoped set for a pre-payment risk gate, with each tool covering a distinct check type. It is on the lean side — no dedicated utility for list metadata or policy inspection — but nothing feels redundant or missing at the count level.
The surface covers the core gating workflow: deterministic rules, sanctions screening, x402 requirement checks, and a model-based full review, each returning decision/flags/actions. Minor gaps exist — no tool to report the SDN snapshot freshness or validate policy input independently — but agents can work around these within the stated purpose.