Skip to main content
Glama
650,529 tools. Updated 2026-10-14 07:08

"How to import transaction history to YNAB" matching MCP tools:

  • Get one page of decoded transaction history for an EVM wallet across DeBank-supported chains. Returns send, receive, and approval categories with protocol, token, exchange, gas, and USD metadata. Use the returned next_cursor as start_time to page backward. Use when: Use for wallet activity discovery, protocol interaction history, exchange exposure, and gas analysis. Page backward with next_cursor for older activity. Use get_transaction or decode_transaction when one known transaction needs block-level details. Limitations: DeBank returns at most 20 entries per call and the data may be stale. This tool is not a complete ledger, PnL engine, or cost-basis calculator because historical execution prices and all transfer semantics are not guaranteed. Alternatives: get_transaction, decode_transaction
    ConnectorNo auth
  • Get one page of decoded transaction history for an EVM wallet across DeBank-supported chains. Returns send, receive, and approval categories with protocol, token, exchange, gas, and USD metadata. Use the returned next_cursor as start_time to page backward. Use when: Use for wallet activity discovery, protocol interaction history, exchange exposure, and gas analysis. Page backward with next_cursor for older activity. Use get_transaction or decode_transaction when one known transaction needs block-level details. Limitations: DeBank returns at most 20 entries per call and the data may be stale. This tool is not a complete ledger, PnL engine, or cost-basis calculator because historical execution prices and all transfer semantics are not guaranteed. Alternatives: get_transaction, decode_transaction
    ConnectorNo auth
  • Get transaction history for a specific account with running balance. Shows transactions in reverse chronological order with a running balance column, useful for seeing how the balance changed over time. By default, only transactions dated **today or earlier** are returned — this keeps the running-balance trail anchored to the live ``current_balance``. Pass ``include_scheduled=True`` to also see future-dated rows (e.g. recurring transactions the cron will spawn); when scheduled rows are included, the running-balance walk anchors at the projected balance (``current_balance`` plus the sum of unapplied future impacts) so the math still reconciles, and each future row carries an ``is_scheduled: True`` flag. Args: account_id: Account to show history for limit: Maximum transactions to return (default 50, max 200) include_scheduled: When False (default), filter out future-dated rows. When True, include them and walk from the projected balance. Returns: Account info and transaction history with running balances. Response includes ``include_scheduled`` so callers know which view they got and ``projected_balance`` when scheduled rows are included.
    ConnectorAPI key
  • Move people's membership from one campaign to another, keeping their invite and message history — nothing is re-created, so the sequence continues where it was. This is how you correct a batch that landed in the wrong campaign; before it existed the only option was to stop every person and re-import them, which loses their history. Both campaigns must send from the SAME account: a campaign is bound to one LinkedIn login, so moving across accounts would change who is approaching this person mid-sequence. Refused if the target already holds them (one membership per campaign) or is completed. Their scheduled steps belong to the target campaign afterwards. ⚠️ Moving people into a PAUSED campaign holds further INVITES but does NOT hold a message step that is already scheduled — nothing checks the campaign at send time for those. Three forms: one person, a list of profileUrls, or allInCampaign for everyone still in the source, which is the shape a mis-filed import actually has. A list refuses outright if some cannot move rather than splitting the group across two campaigns; allInCampaign previews first and needs the count echoed back before it writes.
    Connector
    Destructive
    OAuth
  • Fetch full metadata plus a ready-to-paste React usage example for one specific UploadKit component. When to use: once you know the exact component name (from list_components or search_components) and need to show the user how to drop it into their code. The returned "usage" field is copy-pasteable TSX including the correct import line and the styles.css import. Returns: JSON { name, category, description, inspiration, usage }. If the name does not match any component, returns a suggestion message with the 5 closest matches. Read-only, idempotent.
    ConnectorNo auth
  • Historical rate timeseries for a symbol. Recent history (~30 days) is per-tick; older history is daily granularity. Depth is clamped to your plan (up to 365 days on Pro) and bounded by how far back data has been recorded. (Current plan: up to 1825 days of history.)
    ConnectorNo auth

Matching MCP Servers

  • A
    license
    Not graded
    quality
    D
    maintenance
    A minimal MCP server with get_weather and create_ticket tools, used for testing MCP servers across protocol, unit, eval, transport, and auth layers.
    MIT

Matching MCP Connectors

  • Remote MCP server for converting PDFs and scanned documents to Markdown with OCR, and Markdown to PDF. Provides asynchronous conversion jobs, result retrieval, and usage checks; requires a PDF to MD API key.

  • Extract structured JSON from any document: invoices, receipts, contracts, purchase orders, bills. Auto-detects type and returns vendor, customer, line items, totals.

  • Relay a signed Ethereum transaction to the Arbitrum network. The transaction must have been pre-signed by the caller using prepare_gmx_order output. This endpoint does NOT sign — it only broadcasts an already-signed transaction.
    Connector
    Destructive
    No auth
  • A wallet's Aave transaction history (supply, borrow, repay, withdraw, collateral changes) on v3, v4, or both. Most recent first. v4 covers every chain; v3 reads one market on one chain at a time, because upstream paginates per market, so it states its scope as 'chainsCovered' and 'market' and you pass chainId to read another. Use get_user_positions, not this, to find out where a wallet holds anything.
    ConnectorNo auth
  • Builds an unsigned transaction blueprint for creating a borrow auction — you post collateral and ask lenders to compete to lend against it — including the prerequisite collateral approval. Every term is yours to set: which collateral and how much, which loan token and how much, the maximum repayment you will accept, the loan duration, how long the auction runs, and the bid step. This tool encodes what you specify and warns about consequences; it does not propose terms, rates or a loan size. Lenders bid DOWN from your maximum repayment, so max_repayment is your worst acceptable price — set it too low and the auction may attract no bids. Returns an unsigned transaction blueprint for the requested intent. The user is responsible for reviewing, signing, and broadcasting via their own wallet. Aletheia does not hold keys or dispatch transactions.
    ConnectorNo auth
  • A wallet's Aave transaction history (supply, borrow, repay, withdraw, collateral changes) on v3, v4, or both. Most recent first. v4 covers every chain; v3 reads one market on one chain at a time, because upstream paginates per market, so it states its scope as 'chainsCovered' and 'market' and you pass chainId to read another. Use get_user_positions, not this, to find out where a wallet holds anything.
    ConnectorNo auth
  • Public, no-auth storefront for agents. Returns what ScanScam Integrity can verify, the commercial model, and how to express demand. Do not send transaction data.
    ConnectorNo auth
  • List recent changes to the household (the change history / "Recent Moves"): budget assignments and moves, transaction edits, category/account/payee/goal/rule/recurrence/tag changes — newest first, with who made each one and whether it can be undone. Use the returned id with undo_change / redo_change. Reversals (undos/redos) are listed too unless includeReversals is false.
    ConnectorOAuth
  • Which FDA import alerts are in here, and how many firms are on each? Returns the alert number, FDA's own title for it, the number of firms red-listed, how many countries they are in, and the newest listing date. Call this first to see what can be answered, and to get an alert number for list_alert_firms.
    ConnectorNo auth
  • Quote how much HYPE a given amount of $AI returns right now, net of the on-chain sell fee. Use it to preview a sell; it returns no transaction. To get the calldata, call ai_build_sell_tx with the same ai amount.
    ConnectorNo auth
  • Returns the complete how-to for Quillm: the view code contract, a working template, the libraries you can import, styling rules, and dataset conventions. Read this once per session before you call create_view or update_view. It is short.
    ConnectorOAuth
  • Get recent insider trading transactions for a stock from SEC Forms 4 and 5, newest first. Form 3 supplies initial ownership rather than a transaction. The Type column carries the SEC transaction code meaning: 'Buy'/'Sell' are open-market purchases/sales only, while Award, Conversion, Exercise, Tax Payment, Expiration, Gift, Inheritance, Discretionary and Other are compensation or derivative mechanics — not conviction trades. The 10b5-1 column marks trades made under a pre-arranged Rule 10b5-1 plan ('-' = filing predates the 2023 checkbox). Per-row Shares/Price/Value are as filed; Owned After is the post-transaction balance restated onto today's split basis, tracked per security kind and ownership form. Supports optional date-range, transaction-type and insider-name filters to reach history beyond the newest rows. Use this to understand insider buying/selling activity.
    ConnectorNo auth
  • Use this for any question about building credit as an immigrant, newcomer, international student, or temporary resident in Canada. Returns the ordered path for someone new to Canada: what to do before a SIN arrives, whether their home-country history can be imported and at which banks, how to get a first tradeline, and what accumulates after that. Supply the home country for a specific answer on credit import; coverage is partial, and several of the largest source countries for Canadian newcomers are not covered at all. Returns bundled reference material, optionally filtered or calculated from inputs; does not fetch live data or change accounts.
    ConnectorNo auth
  • Categorise bank-statement transaction descriptions into the fixed vocabulary this product maps to balance sheet lines (sales, software, owner-in, …). Send description strings only, never amounts or dates. Sum the amounts per returned category yourself, then call totals_to_figures. One statement import is one quota unit; previously seen descriptions are answered from a shared cache free.
    ConnectorNo auth
  • Submit one already-signed XRPL transaction to the network. `tx_blob` must be the complete signed transaction encoded as hexadecimal; obtain it from the caller's local signing step, normally after `n9t2_xrpl_prepare_transaction`. This action mutates ledger state when the transaction is accepted into the XRPL network and must never receive private keys, seeds, or wallet secrets. `fail_hard` forwards rippled's option and defaults to false; when true, a transaction that fails locally is not retried or relayed. The result preserves the raw submit response, including `engine_result` and `engine_result_message` and, when returned, `accepted`, `queued`, `validated`, and transaction data. Submission is tentative; use `n9t2_xrpl_get_transaction` with the returned transaction hash to confirm validated-ledger inclusion. Invalid hexadecimal or XRPL-rejected blobs return an error.
    Connector
    Destructive
    No auth
  • Read-only XRPL transaction lookup for one canonical transaction hash. `transaction` is the required hash; set `binary=true` only when binary-encoded transaction data is required, otherwise use the normal transaction representation. The result retrieves transaction data for that hash without modifying the ledger, and calls are subject to the configured gateway rate limits. Use this when the transaction hash is already known; use n9t2_xrpl_list_account_transactions for account-wide transaction history instead.
    ConnectorNo auth
  • Read this workspace's current billing period: requests used, plan, monthly limit, and any metered overage. Call this to see how close you are to the quota before a big import.
    ConnectorNo auth