money.barker/stablecoin-yield
REMOTE · MCP.BARKER.MONEY · SCANNED SEP 20
Barker's real-time stablecoin yield index + AI advisor + non-custodial deposit/redeem (x402 paid).
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 → Why this is hard to score →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 11 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- 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 Usability67
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2068 tokens (~188/item across 11 items; 11 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management94
- Stability check failed: schema churn in the 30 days we've observed: 0 tool removals, 1 breaking changes, 0 auth/transport breaks, 0 additions. See how to fix → Fail
Tool Coverage96
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 88% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the money.barker/stablecoin-yield MCP server?
money.barker/stablecoin-yield is a hosted endpoint at https://mcp.barker.money/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.
remote · mcp.barker.money
claude mcp add --transport http money-barker-stablecoin-yield 'https://mcp.barker.money/mcp'
{
"mcpServers": {
"money-barker-stablecoin-yield": {
"url": "https://mcp.barker.money/mcp"
}
}
} {
"servers": {
"money-barker-stablecoin-yield": {
"type": "http",
"url": "https://mcp.barker.money/mcp"
}
}
} [mcp_servers.money-barker-stablecoin-yield] url = "https://mcp.barker.money/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"money-barker-stablecoin-yield": {
"type": "remote",
"url": "https://mcp.barker.money/mcp",
"enabled": true
}
}
} openclaw mcp add money-barker-stablecoin-yield --url 'https://mcp.barker.money/mcp' --transport streamable-http
mcp_servers:
money-barker-stablecoin-yield:
url: "https://mcp.barker.money/mcp" {
"McpServers": {
"money-barker-stablecoin-yield": {
"Transport": "http",
"Url": "https://mcp.barker.money/mcp"
}
}
} assistant mcp add money-barker-stablecoin-yield -t streamable-http -u 'https://mcp.barker.money/mcp'
{
"mcpServers": {
"money-barker-stablecoin-yield": {
"type": "http",
"url": "https://mcp.barker.money/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.
- 12 Sept 26 −1
- Stability: pass → fail ▼ security
- A breaking change shipped without a version bump: still 0.1.0 ▼ security
- “barker_crosschain_routes” made “from_chain” required, so existing callers break ▼ functional
- “barker_crosschain_routes” made “symbol” required, so existing callers break ▼ functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 +1
- Stability: 0.97 → pass security
- 23 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 1 Aug 26 0
- Schema quality: 161 → 179 ▼ functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 28 Jul 26 0
- Schema quality: good → excellent functional
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 20 Sept 2026 · Probed https://mcp.barker.money/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=barker.money | CN=WE1,O=Google Trust Services,C=US | 23 Jul 2026 | 21 Oct 2026 | ECDSA 256 | ECDSA-SHA256 | 32419c583d8150af0e7d4dd8bf72eb7f |
| SANs: barker.money, *.barker.money | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.barker.money. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| money. | present | 4450 | 8 | Verified |
| barker.money. | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.barker.money/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.barker.money/mcp | Inconclusive | 405 |
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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
barker_crosschain_routes ~85
Barker's cross-chain route availability for a stablecoin from a given chain (bridge/venue coverage). Use for 'bridge USDC from arbitrum', '跨链路径'. (paid: $0.01 per call via x402)
| Name | Type | Req | Description |
|---|---|---|---|
| from_chain | string | yes | Origin chain (lowercase) |
| symbol | string | yes | Stablecoin symbol (lowercase) |
No output schema declared.
No examples provided.
barker_defi_vaults ~225
Query real-time stablecoin supply yield pools from Barker's index of 500+ DeFi protocols. Returns ranked rows with protocol_name, chain_name, asset_symbol, supply_apy_total (decimal — multiply by 100 for %), and supply_tvl (USD). Use for questions like 'best stablecoin yield', 'where to earn on USDC', 'compare lending rates', '稳定币利率'. (paid: $0.001 per call via x402)
| Name | Type | Req | Description |
|---|---|---|---|
| asset | string | – | Stablecoin symbol (lowercase): usdt, usdc, dai, usde, usds, fdusd, gho, crvusd, pyusd, sdai, frxusd, tusd, lusd, dola, etc. |
| chain | string | – | Chain name (lowercase): ethereum, bsc, arbitrum, base, polygon, optimism, avalanche, solana, etc. |
| limit | integer | – | Row count (default 50, max 100) |
| sort | string | – | Sort key |
No output schema declared.
No examples provided.
barker_executable_pools ~287
EXECUTION DISCOVERY: which stablecoin vaults in Barker's index support direct deposit/redeem through barker_execution_quote. Returns executable pools with adapter support, live deposit capacity (is_full) and APY/TVL. Call this before barker_execution_quote — every pool listed here can be quoted, and its pool_uid is the exact string that tool expects (its vault_token_address works there too). Skip this call entirely if you already know the vault contract address. All parameters are optional: call with no arguments to get the top executable pools across every asset. APY unit: decimal (0.05 = 5%). Use for 'which pools can my agent actually deposit into', '哪些池子能直接存'. (paid: $0.01 per call via x402)
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | – | Filter by executable action |
| asset | string | – | Optional stablecoin symbol filter, case-insensitive: usdc, usdt. Omit to list all assets. |
| chain | string | – | Optional chain filter (lowercase), e.g. base, ethereum |
| limit | integer | – | Max rows (default 20) |
| min_tvl | number | – | Min TVL floor in USD (default 1000000) |
| query | string | – | Optional pool keyword, e.g. 'Steakhouse USDC' |
No output schema declared.
No examples provided.
barker_execution_quote ~592
EXECUTION QUOTE (non-custodial): buy an unsigned, ready-to-sign transaction that deposits into or redeems from a stablecoin vault. Returns transaction_request {chainId,from,to,data,value} + route + risk summary + approval info. Barker NEVER broadcasts and never holds funds — return the transaction to YOUR user's wallet to sign; vault shares always go to signer_address (receiver is not a parameter). Same-chain only (self/portals adapters). pool_uid takes EITHER a Barker pool_uid OR the vault contract address — if you already know the vault address, quote directly, no discovery call needed. Flow: barker_yield_advisor → barker_executable_pools → this tool → your user signs. Asset identity is resolved by the selected pool; symbols and underlying-asset token addresses are never accepted as identity (pass the VAULT contract, not the asset contract). If a pool has multiple possible underlying assets, the backend rejects ambiguity instead of guessing. Use for 'deposit 1000 USDC into this vault', '帮我把 USDC 存进这个池子(自己签名)'. (paid: $0.05 per call via x402)
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | – | Default deposit |
| amount | string | – | Same amount in human units ("1000" = 1000 USDC), converted server-side using the pool's own asset decimals. Use this if you don't want to compute base units yourself. Alternative to amount_base_units. |
| amount_base_units | string | yes | Integer amount in token base units (1 USDC = 1000000). For redeem: underlying assets to withdraw. Send either this OR `amount` — not both (they are cross-checked and a mismatch is rejected). |
| chain_id | integer | – | Optional, only useful when pool_uid is a contract address that is deployed at the same address on several chains (e.g. Aave aTokens). EVM chain id, e.g. 8453 for Base. |
| pool_uid | string | yes | Either the exact pool_uid from barker_executable_pools (copy verbatim), OR the vault contract address (0x + 40 hex) if that is what you already have — no discovery call needed. Both are matched exact… |
| signer_address | string | yes | EVM address that will sign AND receive vault shares / redeemed assets. Mandatory — it is the tx sender and the share recipient, so Barker can never infer or default it. |
| slippage | number | – | Optional slippage tolerance, e.g. 0.005 |
No output schema declared.
No examples provided.
barker_market_overview ~81
Barker's stablecoin market snapshot: total market cap, yield-bearing cap, asset distribution, chain distribution. Use for 'stablecoin market cap', 'USDT market share', '稳定币市场份额'. share_pct fields are decimals (0.425 = 42.5%). (paid: $0.001 per call via x402)
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
barker_market_trend ~94
Barker's historical APY trend for stablecoins vs. US Treasury benchmark over a lookback window (7–180 days). Use for 'DeFi vs treasury', 'is stablecoin APY going up', 'crypto yield trend', '稳定币利率走势'. (paid: $0.001 per call via x402)
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | Lookback window in days (default 30) |
No output schema declared.
No examples provided.
barker_pool_detail ~89
Full single-pool dossier from Barker's index by pool_uid: all APY components (percent unit), TVL, terms, execution capability, reward breakdown. Use after barker_defi_vaults / barker_yield_advisor to inspect one pool. (paid: $0.005 per call via x402)
| Name | Type | Req | Description |
|---|---|---|---|
| pool_uid | string | yes | Pool uid from list tools |
No output schema declared.
No examples provided.
barker_pool_history ~93
Per-pool APY/TVL time series from Barker's index (default 30d, APY percent unit) for trend and volatility analysis of one pool_uid. Use for 'is this pool's APY stable', '这个池子收益稳不稳'. (paid: $0.005 per call via x402)
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | – |
| pool_uid | string | yes | – |
No output schema declared.
No examples provided.
barker_pool_search ~70
Fuzzy search Barker's pool index by keyword (protocol name / pool name / asset). Resolves natural-language pool references to pool_uid for the detail/history tools. (paid: $0.001 per call via x402)
| Name | Type | Req | Description |
|---|---|---|---|
| keyword | string | yes | – |
| limit | integer | – | – |
No output schema declared.
No examples provided.
barker_vault_position ~236
VAULT POSITION (on-chain read): current redeemable value of a wallet's ERC-4626 vault position. Pass the pool_uid (from barker_executable_pools / barker_execution_quote) and the wallet address; Barker resolves the vault contract and reads balanceOf + convertToAssets directly on-chain, returning shares and current_value in the vault's underlying asset (value_asset, e.g. USDC). Barker does not store your deposit baseline — record the principal you deposited yourself; earned = current_value - your net deposits. Use after depositing via barker_execution_quote to monitor a position: 'how much is my vault position worth now', '我存进金库的 USDC 现在值多少'. (paid: $0.001 per call via x402)
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | EVM wallet address holding the vault shares (0x + 40 hex) |
| pool_uid | string | yes | Barker pool uid of the ERC-4626 vault, e.g. morpho-vault_base_usdc_0xee8f4ec5 (from barker_executable_pools) |
No output schema declared.
No examples provided.
barker_yield_advisor ~216
FLAGSHIP: 'Where should I park my stablecoins right now?' Returns a ranked top-N recommendation across Barker's DeFi yield index (500+ protocols) with data-derived reasons and risk flags per pick (APY vs market median, TVL depth, incentive-dependence, lock terms). Use for 'best place for my USDC', '钱放哪收益最好', 'recommend stablecoin yield with low risk'. APY unit: percent (6.2 = 6.2%). (paid: $0.03 per call via x402)
| Name | Type | Req | Description |
|---|---|---|---|
| asset | string | – | Stablecoin symbol (lowercase): usdt, usdc, dai, usde, ... |
| chain | string | – | Optional chain filter (lowercase) |
| limit | integer | – | Top-N picks (default 5) |
| min_tvl | number | – | Optional explicit TVL floor (USD) |
| risk | string | – | Risk band → TVL floor $10M/$1M/$100K |
No output schema declared.
No examples provided.
What is the money.barker/stablecoin-yield MCP server?
money.barker/stablecoin-yield is an MCP server listed in the public MCP registry as money.barker/stablecoin-yield. Barker's real-time stablecoin yield index + AI advisor + non-custodial deposit/redeem (x402 paid). This page covers its hosted endpoint (https://mcp.barker.money/mcp).
Is the money.barker/stablecoin-yield MCP server safe to use?
money.barker/stablecoin-yield scores 71 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 money.barker/stablecoin-yield MCP server expose?
money.barker/stablecoin-yield exposes 11 tools: barker_defi_vaults, barker_market_overview, barker_market_trend, barker_yield_advisor, barker_pool_detail, and 6 more. Their descriptions and schemas cost roughly 2,068 tokens of context every time the server is loaded.
Does the money.barker/stablecoin-yield MCP server require authentication?
No. We connected to money.barker/stablecoin-yield without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the money.barker/stablecoin-yield MCP server still maintained?
money.barker/stablecoin-yield is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.