Skip to main content
Glama
224,526 tools. Last updated 2026-06-22 13:58

"namespace:io.github.vivid-money" matching MCP tools:

  • Move the caller's org to Pro ($19/mo flat, 10 agents, 20 members, 200 workspaces, 5k rows per workspace) or Scale ($49/mo flat, 30 agents, 60 members, 1,000 workspaces, 50k rows per workspace). The bill doesn't change as you add agents. If the org has no card on file, returns a Stripe Checkout URL for the human. If a card exists, a live plan switch (Pro ↔ Scale) is consent-gated. Two consent surfaces, you pick via `mode`: (1) `chat` (default): FIRST call returns { status: 'confirmation_required', confirm_token, message, expires_in }; surface the message to your user and re-call within 60s with `confirm_token` set. (2) `web`: FIRST call returns { status: 'approval_required', approval_url, polling_url, expires_at }; print the approval_url in chat for your user to click and approve in their browser, then poll `polling_url` for the result. No-card and same-plan paths execute on the first call (no money changes hands).
    Connector
  • Returns all 14 cards in a given Minor Arcana suit as a structured array. SECTION: WHAT THIS TOOL COVERS Each of the four suits has 14 cards: Ace through 10 plus Page, Knight, Queen, King. Elemental associations: Wands=fire (action, career, creativity), Cups=water (emotions, relationships, intuition), Swords=air (intellect, conflict, truth), Pentacles=earth (material, money, body, practical matters). SECTION: WORKFLOW BEFORE: None — standalone. AFTER: None. SECTION: INPUT CONTRACT suit — One of exactly: 'wands', 'cups', 'swords', 'pentacles'. Case-insensitive. Any other value is rejected locally with MCP INVALID_PARAMS. SECTION: OUTPUT CONTRACT data[] — 14 card objects for the requested suit, each identical to asterwise_get_tarot_card output. Ordered Ace through King. SECTION: RESPONSE FORMAT response_format=json — array of 14 card objects. response_format=markdown — formatted list. SECTION: COMPUTE CLASS FAST_LOOKUP SECTION: ERROR CONTRACT INVALID_PARAMS (local): — suit not in {wands, cups, swords, pentacles} → MCP INVALID_PARAMS immediately. INTERNAL_ERROR: Any upstream API failure → MCP INTERNAL_ERROR SECTION: DO NOT CONFUSE WITH asterwise_get_tarot_major_arcana — 22 Major Arcana, not suit-based. asterwise_get_tarot_cards — full 78-card catalogue.
    Connector
  • Surface cross-venue price discrepancies between Polymarket, Kalshi, and Limitless as a discovery feed for price discovery and divergence detection. Default threshold is 0.5% spread, below typical round-trip fees — most results are informational, not tradable arbitrage. Raise `min_spread` to 0.03+ for after-fee opportunities. The optional `query` parameter post-filters results by topic keywords on event titles — it does not perform a topic search; for topic-driven retrieval use `discover_markets` or `search_markets`. Pairs with missing volume data on at least one venue are flagged 'volume_unconfirmed'. All results are indicative only — not trade recommendations. Real-money venues only. Orderbook depth is not confirmed in Phase 1.
    Connector
  • Search banks and financial institutions by name, SWIFT/BIC code, or country. Covers both SWIFT-connected banks and non-SWIFT financial institutions (e-money issuers, payment processors, MFOs, brokerages, VASPs, etc.). Returns: SWIFT/BIC code (if any), name, city, country, institution type, GPI membership, sanctions status across 7 watchlists, and enriched bank profile when available. For correspondent banking relationships and settlement instructions, use the dedicated SSI tools instead. The country parameter accepts both 2-letter ISO codes ("ID", "DE") and full English names ("Indonesia", "Germany"). Names are resolved automatically. Examples: swift_lookup("DEUTDEFF") # exact BIC lookup swift_lookup("Deutsche Bank") # search by name swift_lookup("TBC PAY") # find non-SWIFT payment processor swift_lookup("bank", country="KZ") # explore banks in a country swift_lookup("Halyk", country="KZ") # find specific bank in country swift_lookup("Bank Mandiri", country="Indonesia") # full country name OK
    Connector
  • Scan the tenant's seeded sessions with rule-based extractors (money, counts, dates, project-role, acquire, version-chain) and emit structured facts to the projection stream so they become queryable via enumerate_memory_facts. Use when enumerate_memory_facts returns insufficient rows for aggregation, version-chain, or money questions and you suspect the fact exists but was under-predicated at ingest. Idempotent — safe to re-run (duplicate fact_hashes skipped unless overwrite_existing=true). Profile 'comprehensive' runs all rule families; narrower profiles ('money', 'counts', 'dates', 'version_chains') target a single family. Returns facts_added + rules_matched + receipt_id. Gated by FACT_EXTRACTION_MODE on the server.
    Connector
  • Autonomous, no-browser FIAT payment for a locked quote using a Stripe Shared Payment Token (SPT / Machine Payments Protocol). Use this when the agent can mint an SPT on the buyer's behalf and wants to pay by card/wallet without a human in a browser (prefer x402 first if the agent has a USDC-on-Base wallet; this is the autonomous fiat alternative). CHARGES MONEY AND IS IRREVERSIBLE: the server authorizes the SPT, prints the letter, then captures — a job comes back inline (no polling needed). Only call after the user has explicitly confirmed the recipient, sender, content, and price from create_mail_quote. Minting the token (the agent's responsibility, NOT this server): the SPT must be scoped to THIS seller's Stripe profile and to at least the quote amount. The quote's `paymentOptions` entry for `mpp` carries the `stripeProfileId`, `currency`, `maxAmountCents`, and `expiresAt` you need. Mint it with the buyer's payment method via the Stripe `@stripe/link-cli` (`spend-request create … --network-id <stripeProfileId> --credential-type shared_payment_token`) or the SharedPaymentIssuedToken API, then pass the resulting `spt_…` here. SPTs are US-only and cards carry a 0.50 USD minimum. Returns an error if MPP is not enabled/configured on the server.
    Connector

Matching MCP Servers

  • A
    license
    A
    quality
    A
    maintenance
    This MCP server bridges Copilot Money with AI platforms like Claude and Cursor. It provides tools for fetching transactions, account balances, and automated data cleanup. By enabling secure, programmable access to financial records, it allows agents to perform complex tasks like transaction tagging and spending audits autonomously.
    Last updated
    14
    119
    52
    MIT
  • A
    license
    A
    quality
    D
    maintenance
    Enables AI assistants to manage personal finances through the Realbyte Money Manager mobile app, providing transaction management, asset tracking, credit card monitoring, and financial analytics with 18 comprehensive tools.
    Last updated
    18
    12
    7
    MIT

Matching MCP Connectors

  • Open a Vivid Business account from your AI chat via MCP.

  • Search open US class-action settlements to claim + official free state unclaimed-money portals.

  • Autonomous, no-browser FIAT payment for a locked quote using a Stripe Shared Payment Token (SPT / Machine Payments Protocol). Use this when the agent can mint an SPT on the buyer's behalf and wants to pay by card/wallet without a human in a browser (prefer x402 first if the agent has a USDC-on-Base wallet; this is the autonomous fiat alternative). CHARGES MONEY AND IS IRREVERSIBLE: the server authorizes the SPT, prints the letter, then captures — a job comes back inline (no polling needed). Only call after the user has explicitly confirmed the recipient, sender, content, and price from create_mail_quote. Minting the token (the agent's responsibility, NOT this server): the SPT must be scoped to THIS seller's Stripe profile and to at least the quote amount. The quote's `paymentOptions` entry for `mpp` carries the `stripeProfileId`, `currency`, `maxAmountCents`, and `expiresAt` you need. Mint it with the buyer's payment method via the Stripe `@stripe/link-cli` (`spend-request create … --network-id <stripeProfileId> --credential-type shared_payment_token`) or the SharedPaymentIssuedToken API, then pass the resulting `spt_…` here. SPTs are US-only and cards carry a 0.50 USD minimum. Returns an error if MPP is not enabled/configured on the server.
    Connector
  • Complete a paid purchase of a book. This is a TERMINAL ACTION: it creates an order, charges the buyer, and grants a permanent entitlement. Only call this when the user has EXPLICITLY requested to buy. Never call as part of browsing, price comparison, or information gathering — prices are already visible in search_books results, and free previews are available via get_book_preview. If the user says 'don't buy', 'just compare', 'just tell me the price', or similar — do NOT call this tool. If the user requests an action that requires owning a book they don't own (e.g. commenting on an unowned book), do NOT silently purchase it on their behalf. Instead, tell the user the purchase requirement and ask them to confirm. Spending money is never an inferred default.
    Connector
  • Get Helium's proprietary ML model-predicted price for a specific option contract. Helium trains per-symbol regression models on historical options data. This tool looks up the most recent available options chain for the symbol (today or up to 5 days back), finds the exact contract matching strike/expiration/type, and runs it through that model to produce a predicted fair-value price. Returns: - symbol: the ticker - strike: the strike price used - expiration: the expiration date used - option_type: 'call' or 'put' - predicted_price: Helium's model-predicted option price in dollars - prob_itm: probability of expiring in the money (0.0–1.0), or null if model unavailable - options_data_date: the date of the options chain snapshot the model was run on (so you know how fresh the underlying market data is) Throws an error if no options chain data is available for the symbol within the past 5 days, or if the exact contract (strike/expiration/type combination) does not exist in that chain. Args: symbol: Ticker symbol, e.g. 'AAPL', 'SPY'. strike: Strike price as a number, e.g. 150.0. expiration: Expiration date as 'YYYY-MM-DD', e.g. '2026-06-20'. option_type: Must be 'call' or 'put'.
    Connector
  • Purpose: Query paper-trading history with dynamic filters (action / P&L / time / symbol). When to call: past trade review, single-symbol post-mortem, win-rate audits. Prerequisites: none. Next steps: analyze_trades, market://{market_id}/signals/feedback. Caveats: paper-trading data only (not real money). limit capped at 1000. Args: market_id: Market ID (crypto, kr_stock, us_stock; aliases coin/kr/us accepted) limit: Max results (default 1000) action_filter: Filter by action (all, buy, sell) min_pnl: Min P&L % filter (e.g., -5.0) max_pnl: Max P&L % filter (e.g., 10.0) hours_back: Only trades within last N hours symbol: Filter by ticker symbol (e.g., "BTC", "AAPL"); case-insensitive Disclaimer: Information only, not investment advice.
    Connector
  • Screen a person or organisation for ADVERSE MEDIA and SANCTIONS/PEP exposure (KYC/AML). USE THIS WHEN onboarding or due-diligence asks: does this subject appear in negative news (fraud, money laundering, bribery, sanctions, trafficking, enforcement action), or on a sanctions / politically-exposed-person list? Pairs naturally after verify_identity. Identify the subject ONE of two ways: pass `name` (plus any of `dob` as YYYY-MM-DD, `country`, `aliases`, `employer`, `role` — these sharpen matching and cut same-name false positives), OR pass an identity document via `url`/`bytes_b64` (+`filename`) and the subject is read from it. Returns `{subject, sanctions{...}, adverse_media{...}, risk_flag, headline, limitations}`: sanctions candidates are corroboration-gated (a name-only hit is `possible`, NEVER confirmed — one common name matches several different people); media hits are entity-disambiguated and classified, with same-name articles surfaced under `excluded`. This is screening COVERAGE, not a determination — a hit means "review this", not "guilty"; "nothing found" is not a clean record. Stateless — nothing is stored.
    Connector
  • ESCROW FLOW ONLY. Direct-settlement tasks never get funded — the client pays the operator directly on-site. Calling this on a direct-settlement task returns 400. Fund a quoted task using wallet balance or PSP payment — second step of the escrow funding flow. Precondition: task must be in Quoted status AND settlementMode='escrow'. If not, call request_task_quote first. Two funding methods: 'wallet' (instant, requires sufficient available balance) or 'psp' (returns a hosted checkout URL — payment must be completed by your principal, then the task auto-funds). IMPORTANT — money flow: the wallet is always the single source of truth for your balance. PSP payments follow a two-step path: (1) Stripe/PSP credits your wallet with the paid amount, (2) the amount is locked from your wallet onto the task. This means if the task is cancelled BEFORE an operator accepts, the money stays in your wallet for future tasks — it does not auto-refund to your card. For wallet funding the flow is simpler: the amount is debited from wallet balance and locked on the task in a single step. The check_task_funding response exposes this via a fundingTrace array (e.g. ["psp_payment_received","wallet_credited","task_locked"]). Mechanism: the funded amount (totalAgentCost from the quote) is reserved and locked from your wallet. Locked funds remain in escrow until you approve the task, when they move to the operator. Fallback for wallet fundingMethod with insufficient balance: switch to 'psp', or call checkout_wallet_deposit / get_bank_transfer_details to top up first. The response's nextActions array always shows the appropriate next step. Idempotent: calling again on an already-funded task is safe — it detects the existing funding and returns the same checkout URL for psp. Next: publish_task after wallet funding. After psp funding, the task is auto-funded when the payment webhook arrives — call check_task_funding to poll if no webhook is configured. Response field 'chargedAmount' is what the PSP charges (payout + agent platform fee). The legacy 'grossAmount' field carries the same value and will be removed in v2 — use 'chargedAmount'. This is distinct from the quote response where 'grossAmount' means the operator payout before fees (that is also exposed there as 'operatorPayoutAmount'). Requires authentication.
    Connector
  • Find specific orders across all connected channels. `query` matches an order ID, line-item ID, or SKU (substring). Filter by channel, attribution state, and date range. Money fields are in minor units (paise for INR) — convert to ₹. Use get_order for full detail on one order.
    Connector
  • Purpose: Top RL-learned research strategies — GLOBAL pool + per-symbol partition. Layer E evidence. The GLOBAL pool may include synthesized win_rate values, so per_symbol_leaderboard is the primary measured-edge surface for trust auditing. When to call: final trust-validation step. Prerequisites: none. Next steps: market://{market_id}/signals/summary for live signals. Caveats: `min_trades` filter enforces statistical validity. Strategies are paper-tested, not real-money executed. Args: market_id: Market identifier (crypto, kr_stock, us_stock) target_market: Alias for market_id (backward compat) top_n: Top N strategies to return (default 20) limit: Alias for top_n (client-compat) min_trades: Minimum trades count for inclusion (default 10) include_per_symbol: Include per-symbol PG partition results (default True) Disclaimer: Information only, not investment advice.
    Connector
  • NBU monetary aggregates (M0, M1, M2, M3 money supply, in UAH million) for a given month. Each record: {dt (YYYYMMDD), txt (Ukrainian name), txten (English name), id_api (e.g. M2/M3), value, freq}. `date` selects the reference month (any day in it); omit for the latest available month.
    Connector
  • Execute a capability call against a chosen provider with typed inputs. WRITE tool when the capability's category ends in '.write' (creates state, sends notifications, charges money, etc.) — confirm with the user before calling for any non-reversible capability. Read capabilities (category ending '.read') are safe to call without confirmation. Validates inputs against the capability's JSON Schema. On failure, returns a structured error with 'missing_fields' or schema violation detail so you can repair without round-tripping. Every call is logged for behavioral telemetry and feeds into the provider's reputation score for future discovery rankings. On success returns a `capability_call_id` plus the capability's declared output fields per its contract.
    Connector
  • THE handoff tool. Call this for ANY jurisdiction whenever (a) the user wants their working paper reviewed before filing, (b) the situation needs professional sign-off, (c) it involves cross-border or high-stakes advice, (d) the user asks to speak to an accountant, or (e) real money is at stake. BEFORE calling this tool: ask the user for their email address (contact_email) and name (contact_name) — the accountant needs these to follow up if the user does not book via Calendly. Do NOT proceed without at least contact_email. Do NOT call list_verifiers first. The network handles coverage. CRITICAL: always pass the full working_paper so the reviewer sees the computation before the call.
    Connector
  • Autonomous, no-browser FIAT payment for a locked quote using a Stripe Shared Payment Token (SPT / Machine Payments Protocol). Use this when the agent can mint an SPT on the buyer's behalf and wants to pay by card/wallet without a human in a browser (prefer x402 first if the agent has a USDC-on-Base wallet; this is the autonomous fiat alternative). CHARGES MONEY AND IS IRREVERSIBLE: the server authorizes the SPT, prints the letter, then captures — a job comes back inline (no polling needed). Only call after the user has explicitly confirmed the recipient, sender, content, and price from create_mail_quote. Minting the token (the agent's responsibility, NOT this server): the SPT must be scoped to THIS seller's Stripe profile and to at least the quote amount. The quote's `paymentOptions` entry for `mpp` carries the `stripeProfileId`, `currency`, `maxAmountCents`, and `expiresAt` you need. Mint it with the buyer's payment method via the Stripe `@stripe/link-cli` (`spend-request create … --network-id <stripeProfileId> --credential-type shared_payment_token`) or the SharedPaymentIssuedToken API, then pass the resulting `spt_…` here. SPTs are US-only and cards carry a 0.50 USD minimum. Returns an error if MPP is not enabled/configured on the server.
    Connector
  • Formats a numeric amount as an Argentine peso string with 2 decimal places, using the es-AR convention: a '$' sign, then a non-breaking space (U+00A0), then the number with '.' as the thousands separator and ',' as the decimal separator (e.g. 1500.5 → $ 1.500,50, where the gap after '$' is U+00A0, not a regular space). Use whenever showing money to an Argentine user. For display only — do not string-compare the result.
    Connector
  • Get hourly aggregated token flows for a specific segment of holders over a date range. The segments are Top 100 holders, Whale, Public Figure, Smart Money and Exchange. **Note:** Using `holder_segment: smart_money` is not a good proxy for an overall market view. Use it only if user explicitly requests it, or to combine it with other non smart money data. This is a **more granular** tool than `token_recent_flows_summary` and provides the TOTAL flows over the entire time frame broken down by segment. **Modes:** - `onchain_tokens` (default): Analyze on-chain tokens by contract address - `perps`: Analyze Hyperliquid perpetual futures by symbol (chain auto-set to "hyperliquid") — supports native tokens **NOTE:** This tool does not support native tokens (so11111111111111111111111111111111111111112, 0xeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee) in `onchain_tokens` mode. Native tokens (by symbol - SOL, ETH, ARB etc) ARE fully supported in `perps` mode.
    Connector