mcp server
mcp
Stablecoin Yield Index (SYX) and live USDC vault APYs across Ethereum, Base, Arbitrum.
Description as published by the maintainer. Source
- version 2.0.0
- active
active — Registry entry last updated 2026-06-14.
What this server can do
14 functions, named and described by the server itself. Parameter names are shown because they say more about what a function does than its name usually does.
calculate_yield(months, target_id, amount_usdc)- Project compound returns for a USDC deposit into any ACCRUE vault or model portfolio over a given holding period. Uses live APY data and applies the ACCRUE platform fee, which is charged on PRINCIPAL (0.25%/yr standalone, 0.50%/yr managed falling to 0.25% above $1M) and never on yield. Returns gross yield, platform fee, net yield and final balance. Because the fee is on principal, net yield can be negative over a short horizon — net_is_negative flags that. Use this when the user asks "how much would I earn" or "what would my $X grow to". Required: amount_usdc, months.
compare_vaults(vault_ids)- Compare two or more ACCRUE vaults side by side. Returns each vault's live APYs, TVL, chain, and risk tier, plus a comparison summary highlighting the highest yield, highest TVL, and whether the vaults share a risk tier. Use this for "compare X and Y" or "is Aave or Compound better right now" type questions. Required: vault_ids.
get_platform_info- Get high-level facts about the ACCRUE platform: fee structure, custody model, supported chains, wallets, KYC requirements, withdrawal terms, and AI agent integration status. Use this when the user asks "what is ACCRUE", "how does ACCRUE work", "what are the fees", or anything about the platform itself rather than a specific vault.
get_portfolio_details(portfolio)- Get full details on a single model portfolio: its underlying vault allocations, the live APY of each underlying vault, and the blended portfolio APY. Use this when the user asks about a specific portfolio like "what is in Core on Ethereum" or "how does Foundation on Base work". Required: portfolio.
get_syx_components- List the current SYX components with their live weights, APYs, and total value locked. SYX is composed of 8 onchain USDC supply markets: Aave v3 (Ethereum, Base, Arbitrum), Compound v3 (Ethereum), and Morpho v2 Prime USDC vaults from Steakhouse Financial and Gauntlet (Ethereum, Base). Use this when the user asks what is inside SYX, or wants to see the per-component breakdown.
get_syx_history- Get historical SYX index readings. Use this when the user asks how SYX has moved over time, wants a chart of recent readings, or wants to compare current SYX to its recent trend. Returns time-series data points.
get_syx_methodology- Get the full SYX methodology — how the index is constructed, which onchain components are included, how weights are calculated, the measurement windows, and the exclusion rules. Use this when the user asks "how is SYX calculated" or "what does SYX measure" or "what protocols does SYX include".
get_syx_value- Get the current Stablecoin Yield Index (SYX) value and rolling averages (7-day, 30-day, 90-day). SYX is a TVL-weighted benchmark for conservative USDC yield, calculated directly from canonical onchain contracts on Ethereum, Base, and Arbitrum — not aggregated from third-party APIs. Use this when the user asks "what is the current stablecoin yield" or "what is SYX right now" or any benchmark/reference-rate question about USDC yield.
get_vault_details(vault)- Get full details on a single ACCRUE yield vault by ID or name. Returns the live spot APY, 7-day realized APY, 30-day realized APY, TVL, chain, risk tier, underlying protocol, and metadata. Use this when the user asks about a specific vault like "tell me about Steakhouse Prime on Ethereum" or "how is the Aave Base vault doing". Required: vault.
list_model_portfolios(chain, risk_tier)- List all model portfolios on ACCRUE, organised per chain. Each portfolio is a pre-built blend of underlying vaults sized to a risk profile. Returns each portfolio with its live blended APY computed from underlying vault yields. Use this when the user asks "what portfolios are available" or wants a one-click diversified option.
list_vaults- List all stablecoin yield vaults available on ACCRUE with their current live APYs, risk tiers, chains, and underlying protocols. Returns spot, 7-day realized, and 30-day realized APYs for each vault. Use this when the user asks "what vaults are available", "what strategies does ACCRUE offer", or wants to browse options.
recommend_strategy(goal, chain, risk_profile)- Recommend a vault or model portfolio for a user based on their risk profile and chain preference. Uses live APY data to choose the best current option. Returns a recommendation with reasoning. Use this when the user describes what they want ("I want safe yield on Base", "maximise returns on Ethereum") rather than asking about a specific vault. Always reminds users this is informational, not financial advice. Required: risk_profile.
search(query)- Natural-language search across all ACCRUE vaults and portfolios. Use this for vague queries like "find me high-yield options", "show me lending strategies on Base", or "what aggressive options are there". Returns matching vaults and portfolios with live data. Required: query.
search_vaults(chain, protocol, risk_tier, min_apy_pct)- Filter ACCRUE vaults by chain, risk tier, protocol, and/or minimum APY. Returns the matching vaults with live APY data. Use this when the user wants to narrow down by criteria like "Base vaults only", "highest yield on Arbitrum", or "show me conservative options above 4%".
Last successful function declaration observed on . Source: https://accrue.cc/mcp. We list what the server declared; we do not call any of these functions.
Endpoint status observed on . Source: https://accrue.cc/mcp.
Signals
These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.
| Signal | Value | What it measures | Window | Observed | Source |
|---|---|---|---|---|---|
| Latest published version | 2.0.0 | Latest version string the maintainer published to the registry. | as of fetch | Model Context Protocol | |
| Registry record last updated | 2026-06-14 | When the registry record was last updated by its maintainer. | point in time | Model Context Protocol | |
| First listed in the MCP Registry | 2026-06-14 | Date this server was first published to the official MCP Registry. Not a usage or quality measure. | point in time | Model Context Protocol | |
| mcp tools declared | 14 tools | Number of functions the server itself declared when asked to list them. This is what the server offers an agent, not a measure of how well any of them work. | as of probe | accrue.cc | |
| mcp endpoint status | ok | The server listed 14 functions when asked. | as of probe | accrue.cc |
Where to get it
This record as data
Every field on this page, with its source and observation date, is in the catalog JSON. Fetch the whole kind at once instead of parsing this HTML.
GET /api/v1/entries/mcp_server.json