Get started

Get started

MCP server

Connect an AI assistant to the daily screen. It can search instruments, explain a score, compare candidates and read the report, and it answers with the numbers and the time of the screen they come from.

What it is

The Model Context Protocol (MCP) is an open standard for giving AI assistants tools. The Yield Sniper MCP server exposes the same data as the API as 9 tools and 2 resources, so an assistant can look things up instead of guessing.

  • Every result has a short text summary for the assistant to read and structured content for it to parse.
  • The server tells the assistant that data comes from the daily screen, gives the units, and asks it to quote as_of with the numbers.
  • Results are research, not financial advice. The server doesn't place transactions and never asks for wallet access.
AI assistantyield-sniper

Which low-risk stablecoin instruments pay at least 6%? Largest first.

Called screen_instrumentsq: "apy >= 6 and band = low and class = stablecoin and verdict = pass sort tvl desc"

10 stablecoin instruments pass the screen with a low risk band and at least 6% APY. The three largest:

InstrumentAPYTVLScore
SUSDAIUSD AI · Arbitrum6.22%$554.1M80
STEAKUSDGMorpho Blue · Robinhood Chain7.18%$541.0M100
USD1Dolomite · Ethereum8.14%$317.5M80

Screen as of 23 Oct 2026, 23:45 UTC. Research, not financial advice.

Connect a client

  1. Create a key with the read scope in Settings → API & MCP. Settings also shows this configuration with your key filled in.
  2. Add a remote MCP server to your client with the URL https://yieldsniper.finance/api/mcp and the header Authorization: Bearer ys_live_…. Clients that read a JSON file take the configuration on the right.
  3. Restart the client or reload its tools. The server name is yield-sniper.

Transport: Streamable HTTP, stateless; every call is a single POST with the key. Clients that only run local servers can reach it through any local stdio-to-HTTP bridge.

MCP config
{
  "mcpServers": {
    "yield-sniper": {
      "url": "https://yieldsniper.finance/api/mcp",
      "headers": {
        "Authorization": "Bearer ys_live_…"
      }
    }
  }
}
Check the connection
curl https://yieldsniper.finance/api/mcp \
  -H "Authorization: Bearer $YS_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{"jsonrpc": "2.0", "id": 1, "method": "tools/list"}'

Tools

Inputs are JSON Schema objects; the client shows them to the assistant. Field names and units match the REST API.

screen_instruments

Searches the whole daily screen and returns compact rows with the total match count.

Input
  • q string · Query in the query language. Alternative to where.
  • where object[] · Structured filters { field, op, value }, joined with and.
  • sort object[] · { field, direction }, up to 3. Overrides a sort in q.
  • search string · Free text over name, label, protocol and chain.
  • limit integer · Rows to return, 1–25. Default 10.
  • cursor string · next_cursor from a previous call with the same query.
Output
Rows with id, name, venue, asset class, total, native and incentive APY, TVL, score, band, verdict, failed rule and in-report flag, plus total, next_cursor and as_of.
Try asking
“Which low-risk stablecoin instruments pay at least 6%? Largest first.”

get_instrument

Returns one instrument in full, with a plain-language explanation of its score.

Input
  • id string required · Instrument id, "ins_…".
  • include_history boolean · Also return the daily series and a summary. Default false.
  • window enum · 7d, 30d (default) or 90d.
Output
The Instrument, a risk explanation built from its signals, and the history and its summary when asked.
Try asking
“Why does ins_4c29f40abec73e1b score 90 and not 100?”

compare_instruments

Puts 2 to 5 instruments side by side.

Input
  • ids string[] required · 2 to 5 instrument ids.
Output
The key yield, liquidity and safety metrics of each, which one pays more, which one is safer, and the signals that separate them.
Try asking
“Compare ins_4c29f40abec73e1b and ins_0abd5ec576be07e6 on yield, exit and risk.”

get_daily_report

Returns a published report: the top 5 passing instruments per asset class.

Input
  • date string · YYYY-MM-DD. Latest when omitted.
Output
The Report, with the screening summary of that day.
Try asking
“Summarise today's report in three bullet points.”

get_screen_summary

Returns the summary of one daily screen over the whole universe.

Input
  • date string · YYYY-MM-DD. Latest when omitted.
Output
The Screen: universe size, outcome, failures by rule and the leader of each asset class.
Try asking
“How many instruments failed the TVL floor this morning?”

get_methodology

Returns the rules, signals, bands, ranking and schedule.

Input
No input.
Output
The Methodology.
Try asking
“Which hard rules can exclude an instrument with $200M TVL?”

list_watchlists

Returns the user's watchlists with their instruments.

Input
No input.
Output
Each watchlist with its instruments as compact rows from the latest screen.
Try asking
“How do the instruments on my watchlist look today?”

check_wallet

Risk check of a wallet: every yield position it holds, scored against the latest screen, with exposure and what needs attention.

Input
  • address string required · 0x address, ENS name (name.eth) or Solana address.
Output
The WalletRisk (deposits, loans with their health factor, Morpho markets, liquidity and fixed-rate positions; wallet score and band; totals; exposure; alerts; comparisons) and a plain-language summary. Read-only; balances are cached 10 minutes per address.
Try asking
“How risky is my wallet 0x99e6…1367? Is any loan close to liquidation?”

list_watched_wallets

Returns the user's watched wallets with the result of their last daily re-check.

Input
No input.
Output
Each watched wallet: id, label, address, chain_family, ens_name, email_alerts, last_checked_at, score, band, previous_score, score_change (null when either score is missing), alert counts by severity and value.
Try asking
“Did anything get worse in my watched wallets this morning?”
Request · tools/call
{
  "jsonrpc": "2.0",
  "id": 3,
  "method": "tools/call",
  "params": {
    "name": "screen_instruments",
    "arguments": {
      "q": "apy >= 6 and band = low and class = stablecoin and verdict = pass sort tvl desc",
      "limit": 3
    }
  }
}
Response200
{
  "jsonrpc": "2.0",
  "id": 3,
  "result": {
    "content": [
      {
        "type": "text",
        "text": "10 instruments match (showing 3, screen as of 2026-10-23T23:45:21.116Z).\n\n| id | name | protocol | chain | total APY | TVL | score | verdict |\n|---|---|---|---|---|---|---|---|\n| ins_34406302e83e9164 | SUSDAI | USD AI | Arbitrum | 6.22% | $554.1M | 80 low | pass |\n| ins_091f220c4d3996a8 | STEAKUSDG | Morpho Blue | Robinhood Chain | 7.18% | $541.0M | 100 low | pass, in report |\n| ins_f3cbaa85fd31098b | USD1 | Dolomite | Ethereum | 8.14% | $317.5M | 80 low | pass, in report |\n\nMore results: call again with cursor = next_cursor."
      }
    ],
    "structuredContent": {
      "total": 10,
      "has_more": true,
      "next_cursor": "eyJoIjoiOWFlZjM4ODgiLCJ2IjpbMzE3NTI2OTUxLCIwODdmNjQ0ZTVlZGI5MmEzIl19",
      "as_of": "2026-10-23T23:45:21.116Z",
      "rows": [
        {
          "id": "ins_34406302e83e9164",
          "name": "SUSDAI",
          "venue": {
            "protocol": "USD AI",
            "chain": "Arbitrum"
          },
          "asset_class": "stablecoin",
          "total_apy": 6.22,
          "native_apy": 6.22,
          "incentive_apy": 0,
          "tvl": 554068188,
          "score": 80,
          "band": "low",
          "verdict": "pass",
          "failed_rule": null,
          "in_report": false
        },
        {
          "id": "ins_091f220c4d3996a8",
          "name": "STEAKUSDG",
          "venue": {
            "protocol": "Morpho Blue",
            "chain": "Robinhood Chain"
          },
          "asset_class": "stablecoin",
          "total_apy": 7.1808,
          "native_apy": 3.97563,
          "incentive_apy": 3.20518,
          "tvl": 541048126,
          "score": 100,
          "band": "low",
          "verdict": "pass",
          "failed_rule": null,
          "in_report": true
        },
        {
          "id": "ins_f3cbaa85fd31098b",
          "name": "USD1",
          "venue": {
            "protocol": "Dolomite",
            "chain": "Ethereum"
          },
          "asset_class": "stablecoin",
          "total_apy": 8.13962,
          "native_apy": 3.81247,
          "incentive_apy": 4.32715,
          "tvl": 317526951,
          "score": 80,
          "band": "low",
          "verdict": "pass",
          "failed_rule": null,
          "in_report": true
        }
      ]
    }
  }
}

Resources

Resources are documents a client can attach to a conversation without a tool call.

  • yieldsniper://methodologyThe methodology, as JSON.
  • yieldsniper://reports/latestThe latest published report, as JSON.

Limits

Each tool call counts as one request against the key's limits: 60 per minute and 5,000 per day by default, shared with REST calls on the same key. See Rate limits and usage.

Assistants can misread or over-summarise. The structured content of each result is the source of truth; check figures against the Explorer before acting on them.