# SYRI — Stablecoin Yield Risk Index (remote · syri.rfsrisk.ai)

0-100 risk score for stablecoin yield venues (Aave, Morpho, Ondo, Ethena). Pay per call via x402.

- Trust score: 76/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-25

## Components

- remote · `syri.rfsrisk.ai`: 76/100 (this document), [markdown](https://verifymcp.io/servers/ai-rfsrisk-syri/syri.md), [page](https://verifymcp.io/servers/ai-rfsrisk-syri/syri)

## Channel facts

- Endpoint: `https://syri.rfsrisk.ai/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `2026.2.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-25.

- **Endpoint Security**: 66/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 81/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 322 tokens (~107/item across 3 items; 3 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 50/100
  - Stability observed for 15 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the SYRI — Stablecoin Yield Risk Index MCP server?

SYRI — Stablecoin Yield Risk Index is a hosted endpoint at https://syri.rfsrisk.ai/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http ai-rfsrisk-syri 'https://syri.rfsrisk.ai/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "ai-rfsrisk-syri": {
      "url": "https://syri.rfsrisk.ai/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "ai-rfsrisk-syri": {
      "type": "http",
      "url": "https://syri.rfsrisk.ai/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.ai-rfsrisk-syri]
url = "https://syri.rfsrisk.ai/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ai-rfsrisk-syri": {
      "type": "remote",
      "url": "https://syri.rfsrisk.ai/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ai-rfsrisk-syri --url 'https://syri.rfsrisk.ai/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  ai-rfsrisk-syri:
    url: "https://syri.rfsrisk.ai/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "ai-rfsrisk-syri": {
      "Transport": "http",
      "Url": "https://syri.rfsrisk.ai/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add ai-rfsrisk-syri -t streamable-http -u 'https://syri.rfsrisk.ai/mcp'
```

### Other

```json
{
  "mcpServers": {
    "ai-rfsrisk-syri": {
      "type": "http",
      "url": "https://syri.rfsrisk.ai/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-25 (score 76, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-24 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-22 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-20 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-18 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-16 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-14 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-12 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (3)

### `list_syri_venues` (~43 tokens)

List scored stablecoin yield venues

Free. Returns every venue RFS currently scores, with pricing, payment terms and data freshness. Venues outside this list return an error and are never charged.

### `get_syri_score` (~149 tokens)

Get the SYRI risk score for a venue (paid)

PAID: $0.05 USDC on Base per venue, via x402. Returns the risk band (Conservative / Moderate / Speculative) and 0-100 composite. Called without payment, this returns the payment terms rather than the score — that is the expected first response, not a failure. If you can settle x402 payments, pass the encoded authorization as x_payment to receive the score.

Input parameters:

- `entity` (string, required): Venue slug, token, protocol or alias — e.g. usdc-aave-v3, ousg, sdai, usde.
- `x_payment` (string): Optional base64 x402 payment authorization (sent as Payment-Signature).

### `get_syri_status` (~45 tokens)

Service status and data freshness

Free. Reports whether the service is healthy, which network it settles on, how many venues are scored, and how old the data is. Useful before depending on a score.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/ai-rfsrisk-syri/syri#diagnostics

## Score history

- 2026-09-25: 76
- 2026-09-24: 76
- 2026-09-23: 75
- 2026-09-22: 75
- 2026-09-21: 74
- 2026-09-20: 74
- 2026-09-19: 73
- 2026-09-18: 73
- 2026-09-17: 72
- 2026-09-16: 72
- 2026-09-15: 71
- 2026-09-14: 71
- 2026-09-13: 70
- 2026-09-12: 70
- 2026-09-11: 69
- 2026-09-10: 69

## Common questions

### What is the SYRI — Stablecoin Yield Risk Index MCP server?

SYRI — Stablecoin Yield Risk Index is an MCP server listed in the public MCP registry as ai.rfsrisk/syri. 0-100 risk score for stablecoin yield venues (Aave, Morpho, Ondo, Ethena). Pay per call via x402. This page covers its hosted endpoint (https://syri.rfsrisk.ai/mcp).

### Is the SYRI — Stablecoin Yield Risk Index MCP server safe to use?

SYRI — Stablecoin Yield Risk Index scores 76 out of 100 on VerifyMCP. 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 SYRI — Stablecoin Yield Risk Index MCP server expose?

SYRI — Stablecoin Yield Risk Index exposes 3 tools: list_syri_venues, get_syri_score, get_syri_status. Their descriptions and schemas cost roughly 237 tokens of context every time the server is loaded.

### Does the SYRI — Stablecoin Yield Risk Index MCP server require authentication?

No. We connected to SYRI — Stablecoin Yield Risk Index without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the SYRI — Stablecoin Yield Risk Index MCP server still maintained?

SYRI — Stablecoin Yield Risk Index is still listed as active in the MCP registry. We last reached this channel on 25 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://syri.rfsrisk.ai/mcp
- Website: https://syri.rfsrisk.ai/
- Changelog RSS feed: https://verifymcp.io/servers/ai-rfsrisk-syri/syri.xml
- Changelog JSON feed: https://verifymcp.io/servers/ai-rfsrisk-syri/syri.json
- HTML version of this page: https://verifymcp.io/servers/ai-rfsrisk-syri/syri