mcp-registry/money.barker/stablecoin-yield · v0.1.0
Also listed as glama/barkermoney/barker-stablecoin-yield
As of 2026-10-26 17:56 UTC, the Barker Stablecoin Yield MCP server is up with a Glimind reliability score of 88/100 (grade B). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 29 outages in 90 days, with a median recovery of 3 minutes.
Barker's real-time stablecoin yield index + AI advisor + non-custodial deposit/redeem (x402 paid).
Point your MCP client at this streamable-http endpoint: https://mcp.barker.money/mcp
12 of 12 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
5 parameter(s) across 3 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →
2 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.
Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 3 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fmoney.barker%2Fstablecoin-yield/fixes
{
"name": "barker_executable_pools",
"description": "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",
"inputSchema": {
"type": "object",
"properties": {
"asset": {
"type": "string",
"description": "Optional stablecoin symbol filter, case-insensitive: usdc, usdt. Omit to list all assets."
},
"chain": {
"type": "string",
"description": "Optional chain filter (lowercase), e.g. base, ethereum"
},
"limit": {
"type": "integer",
"maximum": 100,
"minimum": 1,
"description": "Max rows (default 20)"
},
"query": {
"type": "string",
"description": "Optional pool keyword, e.g. 'Steakhouse USDC'"
},
"action": {
"enum": [
"deposit",
"redeem"
],
"type": "string",
"description": "Filter by executable action"
},
"min_tvl": {
"type": "number",
"description": "Min TVL floor in USD (default 1000000)"
}
}
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
}
}{
"name": "barker_execution_quote",
"description": "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 cont",
"inputSchema": {
"type": "object",
"required": [
"pool_uid",
"amount_base_units",
"signer_address"
],
"properties": {
"action": {
"enum": [
"deposit",
"redeem"
],
"type": "string",
"description": "Default deposit"
},
"amount": {
"type": "string",
"description": "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."
},
"chain_id": {
"type": "integer",
"description": "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": {
"type": "string",
"description": "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 exactly; partial names and keywords are rejected (POOL_NOT_FOUND), because this is a money path and Barker never guesses the pool. If one contract hosts several products (e.g. Pendle PT vs LP), you get 409 POOL_AMBIGUOUS with the exact candidates to choose from."
},
"slippage": {
"type": "number",
"description": "Optional slippage tolerance, e.g. 0.005"
},
"signer_address": {
"type": "string",
"description": "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."
},
"amount_base_units": {
"type": "string",
"description": "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)."
}
}
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
}
}{
"name": "barker_pool_search",
"description": "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)",
"inputSchema": {
"type": "object",
"required": [
"keyword"
],
"properties": {
"limit": {
"type": "integer",
"maximum": 50,
"minimum": 1
},
"keyword": {
"type": "string"
}
}
},
"annotations": {
"readOnlyHint": true
}
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/money.barker/stablecoin-yield"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/money.barker/stablecoin-yield"}) over MCP.
barker_execution_quote ~627 tokensbarker_executable_pools ~330 tokensbarker_yield_advisor ~274 tokensbarker_paper_hedge_farm ~268 tokensbarker_defi_vaults ~262 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fmoney.barker%2Fstablecoin-yield?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fmoney.barker%2Fstablecoin-yield?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fmoney.barker%2Fstablecoin-yield.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fmoney.barker%2Fstablecoin-yield.svg :target: https://glimind.com/server/mcp-registry%2Fmoney.barker%2Fstablecoin-yield?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:d23928227f3c850e…, first seen 2026-10-17, included at leaf 754 of 74,552. Version history · verify what your client received.
Compare: most reliable finance servers · most reliable other servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-26 17:56 UTC, the Barker Stablecoin Yield MCP server is up with a Glimind reliability score of 88/100 (grade B). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 29 outages in 90 days, with a median recovery of 3 minutes.
Barker Stablecoin Yield MCP server advertises 12 tools, including barker_crosschain_routes, barker_defi_vaults, barker_executable_pools, barker_execution_quote, barker_market_overview.
Point your MCP client at this streamable-http endpoint: https://mcp.barker.money/mcp
Glimind scanned all 12 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.