Skip to content

SYRI — Stablecoin Yield Risk Index MCP server

ai.rfsrisk/syrirfsrisk.aistreamable-httpv2026.2.0Scanned

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

3 tools: 3 only read.

Tools: 0 delete, 0 irreversible, 0 write, 3 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

Decide which of this server's tools your agent can use.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the SYRI — Stablecoin Yield Risk Index MCP server can do

The SYRI — Stablecoin Yield Risk Index MCP server is published by rfsrisk.ai, a domain the MCP Registry verified. It has 3 tools. Every one of them only reads: going by their definitions, none of them creates, changes, sends or deletes anything.

None of its tools reads private data, brings in text other people write, or sends data out.

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 11, 2026, version 2026.2.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

3 tools

Only reads 3Show 3 read-only tools
  • get_syri_scorePAID: $0.05 USDC on Base per venue, via x402.No findings

    Why it is in this group

    • The name "get_syri_score" says "get": a word for reading.
    Description, as the server wrote it
    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.
  • get_syri_statusFree.No findings

    Why it is in this group

    • The name "get_syri_status" says "get": a word for reading.
    Description, as the server wrote it
    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.
  • list_syri_venuesFree.No findings

    Why it is in this group

    • The name "list_syri_venues" says "list": a word for reading.
    Description, as the server wrote it
    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.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:27 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
0
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 2026.2.0. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__syri__list_syri_venues",
      "mcp__syri__get_syri_score",
      "mcp__syri__get_syri_status"
    ],
    "ask": [],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as syri. Review it before you use it.

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/ai.rfsrisk/syri/verify?hash=335fe963127fd1b63998a82ee87e95d0c8e26fd7e5a4f4e2ac60a2c0bd7d5af8" | jq -e '.changed == false'

Pinned hash 335fe963127f, from Nov 11, 2026, 21:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/ai.rfsrisk/syri/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for ai.rfsrisk/syri
[![Anlyon Radar](https://radar.anlyon.com/badge/ai.rfsrisk/syri.svg)](https://radar.anlyon.com/servers/ai.rfsrisk/syri)

Source: MCP Registry. Synced Oct 21, 2026, 17:43 UTC.

SYRI — Stablecoin Yield Risk Index MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

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

No scan can promise that. What its definitions show: 3 tools, all of which only read, and 0 findings from fixed checks. Read-only tools can still pass private data to a model.

Can the SYRI — Stablecoin Yield Risk Index MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the SYRI — Stablecoin Yield Risk Index MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the SYRI — Stablecoin Yield Risk Index MCP server have?

3 tools: 3 read. list_syri_venues, get_syri_score and get_syri_status.

Does the SYRI — Stablecoin Yield Risk Index MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the SYRI — Stablecoin Yield Risk Index MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the SYRI — Stablecoin Yield Risk Index MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 11, 2026.