All servers / Other / Warmio MCP server
Warmio MCP server
Warm local stdio MCP server
Tested by ConnectATDScore 83 out of 100. Tested 2026-11-19 on package version 11.3.1. Package: @warmio/mcp · source
Score breakdown
| Runs | 18 / 20 | |
|---|---|---|
| Tool descriptions | 17 / 20 | |
| Package safety | 20 / 20 | |
| Maintenance | 20 / 20 | |
| Adoption | 8 / 20 |
What we saw
- Starts and answers the MCP handshake: yes (4.6 seconds including download)
- Tools offered: 7
- Last published: 2026-11-15
- Weekly downloads (npm): 933
- License: MIT · Direct dependencies: 6
Want this server set up for your team?
ConnectATD builds AI automation and wires up MCP servers like this one. Tell us what you are trying to do.
Talk to ConnectATDTools and how they are described
Agents choose tools from these descriptions. Under each name you can see how many of its parameters are explained.
get_financial_contextno parametersRead-only compact FinancialContext JSON. Includes status.position, status.accounts, transaction index total/months, recurring, budgets, goals, snapshots, liabilities, holdings, and health. The status.position field is a point-in-time (as-of-date) balance snapshot, separate from transaction and behavior windows. A null position means no position snapshot is available. Transaction items are not inline; use get_transactions for items.
get_transactions2 of 2 parameters describedRead-only transactions from the FinancialContext artifact. Pass exactly one of `period` or `periods`. Use `period: "latest"` for the fixed 10-day window, `period: "YYYY-MM"` for one month, or `periods` for two or three distinct months. Multi-month output contains one month page per requested period in input order. The latest window is not caller-configurable. Months outside the covered range return an error.
request_handoff1 of 2 parameters describedCreate a link for a person to open and complete the existing Warm flow. The link carries an opaque ID. This only requests a human action; it never connects a bank or changes a payment. Use get_handoff_status to read server-confirmed status. A bank connection and data_ready are separate states. For plan_change, status cannot confirm what happened in the Stripe portal, so the handoff remains open.
get_handoff_status0 of 1 parameter describedRead the server-confirmed status of a human handoff. A bank connection and data_ready are separate states. For plan_change, status cannot confirm what happened in the Stripe portal, so the handoff remains open.
search_operations1 of 1 parameter describedSearch the supported Warm operation catalog. Use this first to find the smallest matching operation.
describe_operation1 of 2 parameters describedDescribe one operation, including its input schema and risk. For write operations, pass the exact intended input to receive an approval with its ID, status, URL, and expiry. If approval.status is approved, invoke_operation can run right away. If approval.status is pending, show the user approval_url and wait for them to approve it in Warm.
invoke_operation2 of 3 parameters describedInvoke one previously discovered Warm operation. Every write operation requires an approved approval_id returned for the exact same input by describe_operation. An already approved result can be invoked right away. For pending approvals, wait for the user to approve it in Warm at approval_url.
Tested in a sandbox with an empty environment: no API keys, a throwaway folder, nothing from a real account. A passing test shows the server runs and responds. It is not a security audit.