Skip to main content
Glama
484,048 tools. Updated 2026-08-28 08:22

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

  • Find out whether your transaction will succeed before you pay for it. Simulates on mainnet and returns the decoded error (translated to plain language), logs, compute units consumed, and expected account changes. Use before submitting any unfamiliar or high-value transaction. Never sends — simulation only. $0.02 per call in USDC on Solana. transaction_base64: base64-encoded signed or unsigned Solana transaction
    Connector
  • Version history of an artifact's AI reviews (F5): every review run is a version with its score, model, cost, who/what generated it, and whether it's the current one. Read-only; returns the version list, empty when the artifact has never been reviewed. Use it to see how a feature/experiment/page's review changed over time and to pick the version_id to pass to revert_to_version. Takes the same target_id/target_type you'd pass to review_artifact.
    Connector
  • Internal transfers produce NO transaction hash because no transaction occurs — this append-only journal is their only record. Never truncated; page with `before` (a seq number). Use this when a user asks to verify or dispute an internal payment, since there is no chain to check.
    Connector
  • Measured design CHANGE HISTORY for a live-decoded domain — the Decode Ledger. Token-level diffs between deep decodes over time: "radius 4px→8px", "primary hover #4032C8→#0A2540", "motion dominant 150ms→200ms", each dated. Use it to see how a product's design system is EVOLVING (no screenshot library can backfill this). site = a domain ("stripe.com") or product name. Returns first/last decode dates, decode_count and the dated change entries; empty history = measured, stable so far.
    Connector
  • Retrieves bank account details and recent transaction history via a connected bank API integration. Returns a list of transactions for the specified account, or for all linked accounts when no account ID is provided. Use bank_accounts when an agent needs to inspect account balances, review recent spending, categorise transactions, or reconcile records against a specific bank account. Prefer open_banking_transactions when the integration uses a PSD2 Open Banking provider (TrueLayer) covering 300+ UK and European banks — open_banking_transactions returns richer transaction metadata including merchant names, categories, and running balances. Prefer stripe_payments when the source of payments is a Stripe merchant account rather than a retail bank account. This tool requires a valid bank API credential to be configured on the server.
    Connector
  • Returns the complete setup and usage guide for SwapWizard. Call this FIRST before using any other tool. Covers: required configuration (API key, Alchemy RPC URL, private key), how to use poolId correctly, step-by-step operational flows for swap/zap in/zap out/analyze, transaction execution details, and approval rules.
    Connector

Matching MCP Servers

  • A
    license
    Not graded
    quality
    C
    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

  • Transform any blog post or article URL into ready-to-post social media content for Twitter/X threads, LinkedIn posts, Instagram captions, Facebook posts, and email newsletters. Pay-per-event: $0.07 for all 5 platforms, $0.03 for single platform.

  • Track download history for 70,000+ agent skills. Search and get daily snapshots.

  • Retrieves bank account balances and transaction history via PSD2 Open Banking (TrueLayer), covering 300+ UK and European banks. Returns the account balance, ISO 4217 currency code, and up to 100 recent transactions — each with date, merchant description, amount, and category. Supports optional date filtering to narrow the transaction window. Use this tool when an agent needs to inspect a user's spending history, verify a payment has cleared, assess account affordability, categorise recent bank transactions, or produce a financial summary from live bank data. Do not use for payment initiation — this tool is strictly read-only. Do not use for Stripe-specific payment records, subscription billing, or failed charge investigation — use stripe_payments instead. Requires a TrueLayer access token; returns structured mock data if no token is configured.
    Connector
  • Get comprehensive transaction information. Unlike standard eth_getTransactionByHash, this tool returns enriched data including decoded input parameters, detailed token transfers with token metadata, transaction fee breakdown (priority fees, burnt fees) and categorized transaction types. By default, the raw transaction input is omitted if a decoded version is available to save context; request it with `include_raw_input=True` only when you truly need the raw hex data. Essential for transaction analysis, debugging smart contract interactions, tracking DeFi operations.
    Connector
  • 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.
    Connector
  • THE pre-transaction question in one free call: should my agent deal with this counterparty right now? Returns proceed / caution / reject with reasoning. Liveness-aware: an agent with no public activity signal in 30+ days never gets a clean proceed, even if well-ranked. Use before paying, delegating to, or integrating any agent. Deeper analysis (full risk decomposition, history, signed attestation) is x402/Pro priced — pointers included in the response.
    Connector
  • 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.)
    Connector
  • $0.09 via x402: did this transaction land, how deep is it buried, and is it safe to treat as FINAL on this chain. Returns status, block, tip, confirmations, gas used, fee paid and log count, compared against the chain's own finality threshold (Ethereum 64, Polygon 128, OP-stack 60). A success with two confirmations is not a settled payment. Also distinguishes 'no receipt yet' from 'failed' — conflating those is how agents double-spend.
    Connector
  • Side-by-side raw data for 2–5 Amazon products by ASIN — price, sales/revenue estimates, reviews, listing quality, plus history when available. Pure data fetch (no AI analysis) — do the comparison yourself. For a single ASIN, analyzeProduct is the equivalent. How to use: compare demand (est. sales), revenue, review moat and rating, price positioning, listing quality, and history trends (growing vs declining), then give a verdict on which product is the stronger opportunity and why.
    Connector
  • Import a telegram_mtproto userbot's existing chats as contacts — DM partners, groups, and channels — so everything the account already talks to becomes a valid send_message target without waiting for each chat to message first. Requires the manage_broadcasts permission. Reads the account's dialog list live (the userbot must be connected; large accounts can take up to a minute) and creates missing contacts; existing contacts are untouched, so the call is idempotent. Pass kinds to narrow the import (e.g. ["group","channel"] to leave personal DMs out). Does NOT change the watched-groups list. botId may be omitted when the application has exactly one userbot.
    Connector
  • Delete or void a journal entry. For entries tied to a transaction prefer re-categorizing the transaction (the entry re-derives). Deleting a derived entry is temporary — the engine re-creates it on the next sync; deleting a manual per-transaction override reverts the transaction to its automatic entry; a standalone manual entry is voided (kept for audit, excluded from reports). Every outcome is audit-logged.
    Connector
  • Multi-chain wallet, token, ENS, and transaction-simulation lookups, paid per call in USDC/USDm directly from the caller's own wallet via the x402 protocol — no Abstraxn account needed. Pick one `action`: - wallet_balances ($0.005): token balances for a wallet across 20+ chains. Requires `chain` and `address`. - wallet_transactions ($0.005): transaction history with asset transfers for a wallet. Requires `address`. Optional `chain`, `limit`. - wallet_pnl ($0.01): realized and unrealized profit/loss per token for a wallet. Requires `chain` and `address`. - token_metadata ($0.002): name/symbol/decimals for a token contract. Requires `chain` and `address`. - ens_resolve ($0.001): resolve an ENS name to an Ethereum address. Requires `name`. - ens_reverse ($0.001): resolve an Ethereum address to its ENS name. Requires `address`. - tx_simulate ($0.01): simulate an EVM transaction before sending — gas estimate, execution trace, revert reason. Requires `network_id`, `from`, `to`. Optional `value`, `data`, `gas`. Prices above are indicative — the exact charge for a given call is always whatever the live payment challenge specifies for that request. The first call (no `paymentPayload`) returns `paymentRequired`; retry with the same arguments plus `paymentPayload` to complete payment and get the real result.
    Connector
  • Current live ML ensemble voter weights (latest history row, broken out per market regime). Call it to know how the ensemble is blending its voters before interpreting a prediction; use tengu_ml_weights_history for drift over time.
    Connector
  • Multi-chain wallet, token, ENS, and transaction-simulation lookups, paid per call in USDC/USDm directly from the caller's own wallet via the x402 protocol — no Abstraxn account needed. Pick one `action`: - wallet_balances ($0.005): token balances for a wallet across 20+ chains. Requires `chain` and `address`. - wallet_transactions ($0.005): transaction history with asset transfers for a wallet. Requires `address`. Optional `chain`, `limit`. - wallet_pnl ($0.01): realized and unrealized profit/loss per token for a wallet. Requires `chain` and `address`. - token_metadata ($0.002): name/symbol/decimals for a token contract. Requires `chain` and `address`. - ens_resolve ($0.001): resolve an ENS name to an Ethereum address. Requires `name`. - ens_reverse ($0.001): resolve an Ethereum address to its ENS name. Requires `address`. - tx_simulate ($0.01): simulate an EVM transaction before sending — gas estimate, execution trace, revert reason. Requires `network_id`, `from`, `to`. Optional `value`, `data`, `gas`. Prices above are indicative — the exact charge for a given call is always whatever the live payment challenge specifies for that request. The first call (no `paymentPayload`) returns `paymentRequired`; retry with the same arguments plus `paymentPayload` to complete payment and get the real result.
    Connector
  • 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
  • Rank history for an app's tracked keywords — daily ranks over the requested window, one history array per keyword. Use this to check how rankings moved after a metadata change or to find keywords trending up or down. Cursor-paginated over keywords (default 50 per page). Requires an Indie plan (trial counts).
    Connector