Yomio
REMOTE · MCP.YOMIO.APP · 2 COMPONENTS
Read Yomio expense, income, account, budget, and spending data in an MCP-compatible AI client.
Available components
Last scanned (22 hours ago)
Scores higher than 85% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Finance and Payments
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 Security83
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token. See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- 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 Usability72
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1006 tokens (~67/item across 15 items; 15 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management57
- Stability observed for 17 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage98
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 93% 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 15 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 15 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
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 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Oct 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.
- 24 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Oct 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.
- 20 Oct 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.
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 Nov 2026 · Probed https://mcp.yomio.app/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.yomio.app | CN=Amazon RSA 2048 M01,O=Amazon,C=US | 11 Sept 2026 | 27 Mar 2027 | RSA 2048 | SHA256-RSA | 941aa54690faf73751b8a6b12f179ac |
| SANs: *.yomio.app | ||||||
| CN=Amazon RSA 2048 M01,O=Amazon,C=US (CA) | CN=Amazon Root CA 1,O=Amazon,C=US | 23 Aug 2022 | 23 Aug 2030 | RSA 2048 | SHA256-RSA | 77312380b9d6688a33b1ed9bf9ccda68e0e0f |
| CN=Amazon Root CA 1,O=Amazon,C=US (CA) | CN=Starfield Services Root Certificate Authority - G2,O=Starfield Technologies\, Inc.,L=Scottsdale,ST=Arizona,C=US | 25 May 2015 | 31 Dec 2037 | RSA 2048 | SHA256-RSA | 67f944a2a27cdf3fac2ae2b01f908eeb9c4c6 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.yomio.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| yomio.app. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer resource_metadata="https://mcp.yomio.app/.well-known/oauth-protected-resource/mcp", scope="mcp:read"
Bearer resource_metadata="https://mcp.yomio.app/.well-known/oauth-protected-resource/mcp", scope="mcp:read"Protected resource metadata
| Document | https://mcp.yomio.app/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | No |
| Problem | metadata_http_error |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.yomio.app/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.yomio.app/mcp | HTTPS enforced |
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 →
compare_periods ~84
Compare spending between two time periods.
| Name | Type | Req | Description |
|---|---|---|---|
| period1EndDate | string | yes | End of first period YYYY-MM-DD |
| period1StartDate | string | yes | Start of first period YYYY-MM-DD |
| period2EndDate | string | yes | End of second period YYYY-MM-DD |
| period2StartDate | string | yes | Start of second period YYYY-MM-DD |
No output schema declared.
No examples provided.
get_accounts ~23
Get all payment accounts (cash, cards, bank accounts) with balances.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_balance_overview ~43
Get income vs expenses balance overview.
| Name | Type | Req | Description |
|---|---|---|---|
| endDate | string | yes | End date YYYY-MM-DD |
| startDate | string | yes | Start date YYYY-MM-DD |
No output schema declared.
No examples provided.
get_budget_status ~62
Get budget status and spending vs budget for a specific month.
| Name | Type | Req | Description |
|---|---|---|---|
| budget | number | yes | Monthly budget amount in user currency |
| month | number | yes | Month number (1-12) |
| year | number | yes | Year (e.g. 2025) |
No output schema declared.
No examples provided.
get_categories ~53
Get all available expense categories — both system defaults and user-created custom categories. Returns code, name, description, color, and icon. Call this before reclassify_item if you do not already know a valid category code.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_expense_detail ~43
Get full details of a single expense by ID, including all line items with prices, quantities, and categories.
| Name | Type | Req | Description |
|---|---|---|---|
| expenseId | string | yes | The expense ID |
No output schema declared.
No examples provided.
get_expenses ~116
List expenses with optional date, merchant, category, account, and text filters.
| Name | Type | Req | Description |
|---|---|---|---|
| accountId | string | – | Account ID |
| categories | array | – | Category codes |
| endDate | string | – | End date (YYYY-MM-DD) |
| limit | integer | – | – |
| merchants | array | – | Merchant names |
| offset | integer | – | – |
| search | string | – | Search by merchant or item name |
| startDate | string | – | Start date (YYYY-MM-DD) |
| transactionType | string | – | – |
No output schema declared.
No examples provided.
get_income_list ~71
List individual income entries with optional date filtering. Returns source, amount, date, and account per entry.
| Name | Type | Req | Description |
|---|---|---|---|
| endDate | string | – | Optional end date YYYY-MM-DD |
| limit | number | – | Max results (default 20) |
| startDate | string | – | Optional start date YYYY-MM-DD |
No output schema declared.
No examples provided.
get_income_summary ~53
Get income summary for a date range. Returns total income amount and count of income entries.
| Name | Type | Req | Description |
|---|---|---|---|
| endDate | string | yes | End date YYYY-MM-DD |
| startDate | string | yes | Start date YYYY-MM-DD |
No output schema declared.
No examples provided.
get_recurring_payments ~37
Get recurring payments (subscriptions, bills, upcoming charges).
| Name | Type | Req | Description |
|---|---|---|---|
| status | string | – | Filter by status (omit for all statuses) |
No output schema declared.
No examples provided.
get_spending_summary ~102
Get an aggregate spending total across a date range, grouped by category or merchant. For describing or summarizing a single expense the user already has open, use the expense data already provided instead — this tool is for totals across multiple transactions, not a narrative description of one.
| Name | Type | Req | Description |
|---|---|---|---|
| endDate | string | yes | End date YYYY-MM-DD |
| groupBy | string | yes | How to group spending |
| startDate | string | yes | Start date YYYY-MM-DD |
No output schema declared.
No examples provided.
get_spending_trends ~59
Get spending trends over time (daily, weekly, or monthly).
| Name | Type | Req | Description |
|---|---|---|---|
| endDate | string | yes | End date YYYY-MM-DD |
| period | string | yes | Granularity |
| startDate | string | yes | Start date YYYY-MM-DD |
No output schema declared.
No examples provided.
get_top_merchants ~59
Get top merchants ranked by total spending.
| Name | Type | Req | Description |
|---|---|---|---|
| endDate | string | yes | End date YYYY-MM-DD |
| limit | number | – | Max merchants to return (default 10) |
| startDate | string | yes | Start date YYYY-MM-DD |
No output schema declared.
No examples provided.
get_top_products ~106
Get the top 5 most-purchased products/items ranked by total cost, with similar product names merged (e.g. "MANGO" and "MANGO FRESH" count as one). Use this — not search_expenses — when the user wants to know what they buy most, or for suggesting a recipe from frequently-bought ingredients.
| Name | Type | Req | Description |
|---|---|---|---|
| endDate | string | – | Optional end date YYYY-MM-DD |
| startDate | string | – | Optional start date YYYY-MM-DD |
No output schema declared.
No examples provided.
search_expenses ~95
Search for expenses by keyword (merchant or item name). Returns the actual purchased item names for each matching expense — use this to find out what products/groceries the user bought.
| Name | Type | Req | Description |
|---|---|---|---|
| endDate | string | – | Optional end date YYYY-MM-DD |
| limit | number | – | Max results (default 20) |
| query | string | yes | Search keyword |
| startDate | string | – | Optional start date YYYY-MM-DD |
No output schema declared.
No examples provided.
How do I install the Yomio MCP server?
Yomio is a hosted endpoint at https://mcp.yomio.app/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.yomio.app
claude mcp add --transport http app-yomio-yomio-mcp 'https://mcp.yomio.app/mcp'
What is the Yomio MCP server?
Yomio is an MCP server listed in the public MCP registry as app.yomio/yomio-mcp. Read Yomio expense, income, account, budget, and spending data in an MCP-compatible AI client. This page covers its hosted endpoint (https://mcp.yomio.app/mcp).
Is the Yomio MCP server safe to use?
Yomio scores 82 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 Yomio MCP server expose?
Yomio exposes 15 tools: get_spending_summary, compare_periods, search_expenses, get_top_merchants, get_spending_trends, and 10 more. Their descriptions and schemas cost roughly 1,006 tokens of context every time the server is loaded.
Does the Yomio MCP server require authentication?
Yes. Yomio asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the Yomio MCP server still maintained?
Yomio is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.