sra-riskgate-mcp
Related Servers
Alternatives to sra-riskgate-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceProvides a pre-signature payment-risk verdict (GO/HOLD/STOP) for x402 payments based on counterparty reputation, price anomaly, and OFAC sanctions.-
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to verify proposed payments against their assigned task, budgets, permitted categories, and counterparties, returning an ALLOW or DENY decision with a tamper-evident audit trail.MIT

Collar Guardrailofficial
AlicenseNot gradedqualityBmaintenanceEnables AI trading agents to submit proposed trades for deterministic pre-execution risk evaluation, returning allow/warn/deny decisions, risk scores, and tamper-evident audit hashes. It also supports token safety checks, balance simulation, asset registry lookup, and audit trail verification.MIT- AlicenseNot gradedqualityFmaintenanceEnables verification of AI agent identity, authority, and integrity at transaction time, returning signed verdicts for allow, step-up, review, or block.MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to run a free fail-closed preflight gate on x402 payment challenges and transactions before signing, plus five USDC-paid on-chain truth checks covering arbitrage profitability, token safety, swap routing, quote validation, and trade sizing. Each check returns a verdict with pinned-block evidence and a verifiable receipt.Apache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to run pre-sign risk checks on transactions, approvals, EIP-712 signatures, token addresses, wallet approvals, sanctions screening, and prompt-injection texts, returning green/orange/red verdicts with machine-readable reason codes before signing.1AGPL 3.0
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.