SRA-RiskGate
PYPI · SRA-RISKGATE-MCP
Check stablecoin and x402 payments before an AI agent pays: approve, hold or reject.
Available components
Last scanned (9 hours ago)
Scores higher than 65% of PyPI servers
Category Crypto and Web3
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs setuptools.build_meta at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 1 of 29 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 1 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability60
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 633 tokens (~211/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 14 Oct 26 +31
- Injection markers: unverified → pass ▲ security
- Source repository: fail → pass ▲ security
- First check of Judged manipulation: pass security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- Security disclosure: unverified → fail ▼ functional
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- First check of Tool coverage: 0 functional
- First check of Schema quality: fail functional
- First check of Destructive annotations: pass functional
- First check of Schema quality: fail functional
- First check of Schema quality: good functional
- First check of Tool coverage: 100 functional
- 12 Oct 26 +10
- Source repository: pass → fail ▼ security
- Malware scan: unverified → pass ▲ security
- Security disclosure: fail → unverified ▼ functional
- 8 Oct 26 24
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 17 Oct 2026 · Analysed pypi/sra-riskgate-mcp@0.1.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | setuptools.build_meta |
Background: Why install scripts are a supply-chain risk →
Dependencies 29 packages
| Packages resolved | 29 |
|---|---|
| No linked repository | 1 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_payment_rules ~148
Instant deterministic checks for a USDC payment, before sending it. Checks address validity, self-transfers, the zero address, a per-payment amount ceiling and, if peg_deviation_pct is given (USDC's deviation from $1.00 in percent, e.g. -1.2), depegs in both directions. No model or GPU needed. Returns decision (approve | hold | reject), flags, explanation and required_actions. Only send the payment if decision is "approve".
| Name | Type | Req | Description |
|---|---|---|---|
| amount_usdc | number | yes | – |
| chain_id | integer | yes | – |
| peg_deviation_pct | – | – | – |
| recipient | string | yes | – |
| sender | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
check_payment_with_model ~218
Full risk review of a stablecoin payment by the SRA-RiskGate-4B model. Needs the model running locally (for example: ollama pull sriram1983007/sra-riskgate). Arguments follow the model's training format: now_unix current Unix time policy the receiving policy (e.g. max_amount_usdc, trusted_attesters, allowed_assets) payload the payment exactly as received (treated as untrusted) tool_results outputs of real verification tools: decoded payment, signature check, risk attestations and sanctions screening The model reasons over tool_results; it does not run those checks itself. Returns decision (approve | hold | reject), risk_level, flags, explanation and required_actions. If the model is unavailable or answers off-schema, returns "hold". Only proceed if decision is "approve".
| Name | Type | Req | Description |
|---|---|---|---|
| now_unix | integer | yes | – |
| payload | object | yes | – |
| policy | object | yes | – |
| tool_results | object | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
check_x402_payment ~170
Check an x402 payment requirement BEFORE signing it. Pass the fields from the 402 response's chosen payment requirement: network (CAIP-2 such as "eip155:8453", or a legacy name such as "base-sepolia"), asset (token contract address), amount (in the token's smallest unit, as a string) and pay_to (recipient). payer is the agent's own wallet address. Only USDC on Ethereum, Base and Base Sepolia is checked; anything else is rejected. Only sign and pay if decision is "approve".
| Name | Type | Req | Description |
|---|---|---|---|
| amount | string | yes | – |
| asset | string | yes | – |
| network | string | yes | – |
| pay_to | string | yes | – |
| payer | string | yes | – |
| peg_deviation_pct | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the SRA-RiskGate MCP server?
SRA-RiskGate runs locally as a PyPI package, launched with uvx sra-riskgate-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · sra-riskgate-mcp
claude mcp add sriram1983007-dev-sra-riskgate-mcp -- uvx sra-riskgate-mcp
What is the SRA-RiskGate MCP server?
SRA-RiskGate is an MCP server listed in the public MCP registry as io.github.sriram1983007-dev/sra-riskgate-mcp. Check stablecoin and x402 payments before an AI agent pays: approve, hold or reject. This page covers its PyPI package (sra-riskgate-mcp).
Is the SRA-RiskGate MCP server safe to use?
SRA-RiskGate scores 65 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 17 October 2026. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the SRA-RiskGate MCP server expose?
SRA-RiskGate exposes 3 tools: check_payment_rules, check_x402_payment, check_payment_with_model. Their descriptions and schemas cost roughly 536 tokens of context every time the server is loaded.
Is the SRA-RiskGate MCP server still maintained?
SRA-RiskGate is still listed as active in the MCP registry. We last reached this channel on 17 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the SRA-RiskGate MCP server under?
SRA-RiskGate declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.