cc.accrue/mcp
REMOTE · ACCRUE.CC · SCANNED AUG 4
Stablecoin Yield Index (SYX) and live USDC vault APYs across Ethereum, Base, Arbitrum.
Available components
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. How we score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability80
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 1471 tokens (~105/item across 14 items; 14 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management30
- Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · accrue.cc
claude mcp add --transport http cc-accrue-mcp https://accrue.cc/mcp
[mcp_servers.cc-accrue-mcp] url = "https://accrue.cc/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"cc-accrue-mcp": {
"type": "remote",
"url": "https://accrue.cc/mcp",
"enabled": true
}
}
} openclaw mcp add cc-accrue-mcp --url https://accrue.cc/mcp --transport streamable-http
mcp_servers:
cc-accrue-mcp:
url: "https://accrue.cc/mcp" {
"mcpServers": {
"cc-accrue-mcp": {
"type": "http",
"url": "https://accrue.cc/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 4 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Aug 26 +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.
- 31 Jul 26 +3
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 +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.
- 28 Jul 26 +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.
- 27 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 66
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 4 Aug 2026 · Probed https://accrue.cc/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=accrue.cc | CN=YR1,O=Let's Encrypt,C=US | 30 Jul 2026 | 28 Oct 2026 | RSA 2048 | SHA256-RSA | 5b2a630bd3de12c5418d4b6d3a84c239903 |
| SANs: accrue.cc | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
DNSSEC insecure
Validation of accrue.cc. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| cc. | present | 12593 | 13 | Verified |
| accrue.cc. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline'; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com; font-src 'self' https://fonts.gstatic.com; img-src 'self' data: https:; connect-src 'self' https://api.anthropic.com https://fonts.googleapis.com https://eth-mainnet.g.alchemy.com https://*.walletconnect.com https://*.walletconnect.org wss://*.walletconnect.com wss://*.walletconnect.org https://*.safe.global https://*.web3modal.org; frame-ancestors 'self'; base-uri 'self'; form-action 'self'; |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), payment=() |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://accrue.cc/mcp | Verified | 200 | |
| http (plaintext) | http://accrue.cc/mcp | HTTPS enforced | 308 | https://accrue.cc/mcp |
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.
calculate_yield ~140
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 10% performance fee on yield earned. Returns gross yield, performance fee, net yield, and final balance. Use this when the user asks "how much would I earn" or "what would my $X grow to".
| Name | Type | Req | Description |
|---|---|---|---|
| amount_usdc | number | yes | USDC deposit amount in dollars |
| months | number | yes | Holding period in months |
| target_id | string | — | Optional vault ID or portfolio ID. If omitted, projects across all vaults and portfolios. |
No output schema declared.
No examples provided.
compare_vaults ~106
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.
| Name | Type | Req | Description |
|---|---|---|---|
| vault_ids | array | yes | Array of 2–6 vault IDs or names to compare. |
No output schema declared.
No examples provided.
get_platform_info ~83
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_portfolio_details ~108
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 Optimal Yield on Ethereum" or "how does Stable Yield Base work".
| Name | Type | Req | Description |
|---|---|---|---|
| portfolio | string | yes | Portfolio ID or name. Examples: "stable-yield-eth", "Optimal Yield Portfolio", "enhanced-yield-eth", "Stable Yield Portfolio Base". |
No output schema declared.
No examples provided.
get_syx_components ~106
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_syx_history ~56
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_syx_methodology ~75
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".
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_syx_value ~111
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_vault_details ~143
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".
| Name | Type | Req | Description |
|---|---|---|---|
| vault | string | yes | Vault ID, name, or partial name. Examples: "aave-eth", "Aave USDC Supply (Base)", "Gauntlet Frontier", "morpho-steakhouse-prime-eth". |
No output schema declared.
No examples provided.
list_model_portfolios ~101
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.
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | — | Filter to a specific chain |
| risk_tier | string | — | Filter to a risk tier |
No output schema declared.
No examples provided.
list_vaults ~85
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
recommend_strategy ~121
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.
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | — | Preferred chain (optional) |
| goal | string | — | User's primary goal |
| risk_profile | string | yes | User's risk tolerance |
No output schema declared.
No examples provided.
search ~71
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.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Free-form search query |
No output schema declared.
No examples provided.
search_vaults ~165
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%".
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | — | Filter to a specific chain |
| min_apy_pct | number | — | Minimum effective APY in percent (e.g. 4 for 4%). |
| protocol | string | — | Filter by protocol substring, e.g. "Aave", "Compound", "Morpho", "Steakhouse", "Gauntlet" |
| risk_tier | string | — | Filter to a risk tier |
No output schema declared.
No examples provided.