agents.yoshi.ai
https://agents.yoshi.ai/mcp
active Production-safe Score 87/100 http no auth
At a glance
| Endpoint | https://agents.yoshi.ai/mcp |
|---|---|
| Source | https://github.com/UsefulSoftwareCo/integrations/blob/main/output/mcp-endpoints.json |
| Transport | http |
| Tools | 72 |
| Auth | none |
| First seen | 2026-08-29 01:50:39 |
| Last checked | 2026-11-17 21:57:19 |
Observed reliability
| 7-day uptime | 100% |
|---|---|
| 24-hour uptime | 100% |
| Handshake success | 100% |
| Latency p50 / p95 | 1169 / 1542 ms |
| Last successful check | 2026-11-17 21:57:19 |
Measured by Arclan's validator via repeated live MCP handshakes. How this is computed →
Tools (72)
get_financial_overview— Get a comprehensive overview of the user's finances: net worth, assets vs liabilities, and account breakdown by type. Start here for any broget_net_worth_history— Get the user's net worth trend over time. Shows how total net worth (assets - liabilities) has changed, with period start/end values and perget_security_quotes— Get the latest quotes for one or more securities (equities, ETFs, mutual funds). Use this tool when the user asks about a stock price, markeget_security_details— Get live fundamentals and profile data for any security. Use this tool when the user asks about a company's fundamentals, sector, industry,get_security_price_history— Get historical price data for a single security over a date range. Use this tool when the user asks about stock price trends, performance ovget_security_news— Get provider news headlines and optional press releases for a stock, ETF, or mutual fund. Use this for ticker-specific news or move explanatget_approval_status— Check the canonical state of a trade or transfer submitted with submit_trade or submit_transfer. Pass the thread_id those tools return. Retuget_shared_receiving_instructions— Get the details someone needs to send money into the user's own Yoshi account (account holder name, account and routing numbers, bank name arender_accounts_dashboard— Render the accounts dashboard widget showing account balances and optional balance chart. Call list_accounts (and optionally get_balance_hisget_credit_and_debt_profile— Get the user's credit score and debt profile in one call. This runs two Yoshi reads with the arguments below, and each read's guidance follolist_pending_transactions— List the user's pending Yoshi account transactions. Use this when the user asks what has not posted yet or what is still processing. It takesearch_transactions— Search the user's Yoshi account transactions for a counterparty or description, such as 'Starbucks' or 'Netflix'. The search text is matchedcreate_automation— Create a Yoshi automation from the user's request in plain language. It covers alerts and monitoring ('alert me when any transaction over $5pause_automation— Pause one of the user's Yoshi automations. A paused automation stops running until it is resumed; its configuration and history are kept. Paresume_automation— Resume one of the user's paused Yoshi automations. Pass the automation's id from list_automations. The change takes effect immediately, withrun_financial_review— Run a full financial review of the user's accounts: cash flow, balances, obligations, spending patterns, and notable events over the lookbacget_latest_financial_review— Get the user's most recent saved financial review without running a new one. Use this when the user asks what the last review found or recomget_domain_concept— Get the full definition of business concept(s). Call this when you want to get more business logic or concepts before generating responsupdate_financial_review_preferences— Save standing preferences that shape ALL future financial reviews. Use when the user says "remember this", "always focus on X", or "skip Y"preview_transaction_correction— Preview how transaction corrections change income/expense totals. Use only when the user asks to see impact before changing data; do not useapply_transaction_correction— Apply transaction corrections when the current turn clearly requests or confirms the change. Do not call preview first in the same turn whenapply_account_correction— Apply account-level corrections when the current turn clearly requests or confirms the change. Use for account renames, scoring-role overridlist_transaction_corrections— List active transaction corrections for the current user.list_account_corrections— List active account corrections for the current user. Use this before disable_account_correction when the user asks to undo, revert, remove,disable_transaction_correction— Disable all overrides for a specific transaction.disable_account_correction— Disable all overrides for a specific account.update_preferred_name— Set or update the user's preferred display name. Use when: - User explicitly asks to be called something different - User clearly identifiesshare_receiving_instructions— Share the details someone needs to send money INTO the user's own Yoshi account: account holder name, account and routing numbers, bank namecheck_security_advice_readiness— Check whether Yoshi can give the user a personalized recommendation about one to five securities, and open the advice session that Yoshi's rget_personalized_security_recommendation— Get Yoshi's personalized recommendation on the securities from a ready advice readiness check. Pass the advice_session_id that check_securisubmit_trade— Request a trade (buy or sell) on the user's Yoshi trading account. Creates an approval brief — the trade is NOT executed until the user revlist_briefs— Find the user's actual Briefs, including archived history. Use for 'what needs my attention', 'find yesterday's earnings Brief', 'which reviget_brief— Read one exact owned Brief: content/evidence, family, lifecycle state, proposal revision and execution outcome, available controls, source amanage_brief— Use an explicitly requested control on one exact owned Brief. Identify it with list_briefs/get_brief and ask which if ambiguous. operation=shandoff_to_app— Get a link to the Yoshi app screen where the user connects or verifies a bank account, which needs Yoshi's interactive account-connection sclist_automations— List the user's existing automations, including Rules and Strategies. Use this when the user asks what automations they have, whether sometset_price_move_brief_coverage— Turn default-on 10% holding-move Briefs for the investments in the user's Yoshi account off or back on. Use enabled=false when the user saysset_earnings_brief_coverage— Turn pre-earnings or post-earnings Briefs for holdings in the user's Yoshi account off or back on. The phases are independent: changing oneset_portfolio_recap_cadence— Change the portfolio recap for the user's Yoshi account to daily, weekly, monthly, or off. Use only when the user explicitly asks to change,set_account_review_brief_coverage— Turn the default-on weekly review of the user's Yoshi account and Method-tracked debt off or back on. The cadence is fixed weekly. Use onlylist_proactive_brief_history— List the proactive Briefs Yoshi delivered to the user, newest first, and what they chose afterward. Each returned row is one delivered Brielist_activity— Discover an existing order or payment before inspecting or canceling it. This list is NOT an exact receipt. For a cancellation-outcome questget_activity— Retrieve current state, receipt details and cancellation availability of one exact owned activity. Use list_activity first when the target icancel_activity— Cancel an identified owned order, transfer, bill payment, issued mailed check or queued one-time action when the user explicitly asks. Execuget_investment_holdings— Fetch the user's current investment holdings grouped by asset class with live pricing and day change. Use this when the user asks about theget_investment_performance— Fetch portfolio performance metrics including Time-Weighted Return (TWR), peak-to-current drawdown, maximum drawdown, peak date, and optionaget_dividend_reinvestment_settings— Read live account-wide dividend reinvestment (DRIP) for an owned Yoshi brokerage account. ON reinvests future eligible dividends in full inget_financial_metrics— Resolve canonical financial metrics using the same definitions and implementation used by one-time and recurring automations. Prefer this ovget_investment_realized_gains— Fetch realized gain/loss events from investment sales with summary metrics. Use this when the user asks about realized gains or losses, caplist_investment_tax_lots— List the user's current/open investment tax lots with acquisition dates, remaining quantities, cost basis, current value, unrealized gain/lolist_investment_transactions— List the user's investment transactions with account, security, date, quantity, price, amount, and fee fields. A simple last-trade answer nereplay_benchmark— Replay arbitrary benchmark allocations against a cash-flow chronology. Use this when the user asks "what if these deposits had gone into Xresearch_security— Research a security using Yoshi's normalized investment detail endpoint. Use this for questions about a stock, ETF, mutual fund, or a user'get_options_chain— Fetch a bounded delayed options chain slice for an underlying equity symbol. Use this only when the user explicitly asks about options, calget_portfolio_exposures— Analyze the user's portfolio exposure with fund/ETF look-through when provider data is available. Use this when the user asks about portfolget_portfolio_news— Fetch recent provider news for the user's largest current portfolio holdings. Use this when the user asks what news affects their portfoliocompare_securities— Compare multiple securities using normalized detail data. Use this when the user asks to compare stocks, ETFs, or funds by fundamentals, exsearch_securities— Search Yoshi's security universe by ticker, company name, or fund name. Use this before researching a security when the user gives a name iget_news_article— Fetch provider article details by reference from a prior headline result. Use this only after a headline result returned a reference and thlist_transactions— Search and filter the user's transactions with rich filtering options. For paychecks/payday, use paycheck="verified" (Yoshi deposits only).
Validation history
| Checked | Reachable | Handshake | Latency | Score | State |
|---|---|---|---|---|---|
| 2026-11-17 21:57:19 | ✓ | ✓ | 1141 ms | 85 | active |
| 2026-11-17 21:26:44 | ✓ | ✓ | 1249 ms | 85 | active |
| 2026-11-17 20:43:51 | ✓ | ✓ | 1207 ms | 85 | active |
| 2026-11-17 19:58:25 | ✓ | ✓ | 1157 ms | 85 | active |
| 2026-11-17 19:43:22 | ✓ | ✓ | 1072 ms | 85 | active |
| 2026-11-17 19:28:18 | ✓ | ✓ | 1158 ms | 85 | active |
| 2026-11-17 19:13:17 | ✓ | ✓ | 1214 ms | 85 | active |
| 2026-11-17 18:58:13 | ✓ | ✓ | 1203 ms | 85 | active |
| 2026-11-17 18:43:11 | ✓ | ✓ | 1169 ms | 85 | active |
| 2026-11-17 18:28:10 | ✓ | ✓ | 1488 ms | 85 | active |
| 2026-11-17 18:13:08 | ✓ | ✓ | 1240 ms | 85 | active |
| 2026-11-17 17:58:07 | ✓ | ✓ | 1179 ms | 85 | active |
| 2026-11-17 17:43:06 | ✓ | ✓ | 1126 ms | 85 | active |
| 2026-11-17 17:28:05 | ✓ | ✓ | 1082 ms | 85 | active |
| 2026-11-17 17:13:02 | ✓ | ✓ | 1464 ms | 85 | active |
Query this programmatically
Agents can pull this record live over the MCP protocol or REST:
get_server("https://agents.yoshi.ai/mcp") # via the Arclan MCP endpoint https://arclan.ai/mcp
GET https://arclan.ai/api/registry/agents-yoshi-ai-mcp # JSON