Skip to main content
Glama
130,482 tools. Last updated 2026-05-07 08:04

"Ways to make money" matching MCP tools:

  • 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
  • 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
  • Apply targeted modifications to an existing scene_data object. WHEN TO CALL: - After validate_scene returns is_valid: false - When the user requests a style, material, animation, or position change to an already-generated scene - Do NOT call this to create a new scene — use generate_scene instead WHAT THIS TOOL CAN MODIFY: - background: color and style preset - material: for all objects or a named object - animation: add or replace animations on objects - position: move a named object or the primary object - lighting: intensity adjustments (darker / lighter) - design_tokens: kept in sync with all changes automatically WHAT THIS TOOL CANNOT DO: - Add new objects to the scene (use generate_scene for this) - Remove existing objects (out of scope in current version) - Change camera position or FOV - Modify individual mesh geometry INPUT: - scene_data: the full scene_data object from generate_scene or a previous edit_scene call - edit_prompt: a plain-language description of the desired change EDIT PROMPT EXAMPLES: - "make it darker" → dims ambient lighting, deepens background - "make the material glass" → applies glass_frost to all objects - "add spinning motion" → appends rotate animation, keeps existing - "move the robot up" → moves object named "robot" up by 1 unit - "change animation to float only" → replaces all animations with float - "make it neon" → applies neon material + neon_edge lighting OUTPUT: - scene_data: updated scene with all changes applied - edit_summary: { applied[], skipped[], warnings[] } PIPELINE POSITION: generate_scene → validate_scene → [edit_scene if invalid] → validate_scene (re-run) → synthesize_geometry → generate_r3f_code
    Connector
  • Permanently delete one of the caller's API keys. DESTRUCTIVE — agents using the deleted key will receive auth errors immediately. The Blueprint a key was tied to (if any) is NOT affected; only the credential is revoked. To delete a Blueprint and all its keys, use delete_blueprint. The target key can be specified two ways: - As the full key string (gai_...). - As a key_id (SHA-256 hash from list_api_keys). Args: api_key: GeodesicAI account-level API key (starts with gai_). key_to_delete: Either the full API key string OR the key_id from list_api_keys. confirm: Must be true to actually delete. If false, returns a preview without deleting. Default: false. Returns: status: "ok" | "preview" | "ERROR" deleted: metadata about the deleted key (only on ok) message: human-readable summary
    Connector
  • Publish HTML content to a live URL instantly. No account or API key required. Returns a public URL that anyone can visit. Sites expire after 24 hours unless the owner claims them. Use this when a user asks you to build, create, or deploy a website, landing page, invitation, portfolio, report, or any HTML content they want to share as a link. Supports bundled assets (CSS, JS, images) and multi-page sites (include additional .html files in assets, accessible at /{slug}/{pagename}). IMPORTANT: After publishing, always share the live URL and the claim URL with the user. The claim URL lets them take permanent ownership of the site. Store the edit_key from the response silently — do not show it to the user — you will need it if they ask you to make changes to the site later. If you lose the edit_key, ask the user to claim the site first (via the claim URL in the page footer), then provide you with their API key from the dashboard — you can use that instead.
    Connector
  • Publish HTML content to a live URL instantly. No account or API key required. Returns a public URL that anyone can visit. Sites expire after 24 hours unless the owner claims them. Use this when a user asks you to build, create, or deploy a website, landing page, invitation, portfolio, report, or any HTML content they want to share as a link. Supports bundled assets (CSS, JS, images) and multi-page sites (include additional .html files in assets, accessible at /{slug}/{pagename}). IMPORTANT: After publishing, always share the live URL and the claim URL with the user. The claim URL lets them take permanent ownership of the site. Store the edit_key from the response silently — do not show it to the user — you will need it if they ask you to make changes to the site later. If you lose the edit_key, ask the user to claim the site first (via the claim URL in the page footer), then provide you with their API key from the dashboard — you can use that instead.
    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
    17
    119
    36
    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.

  • Give your AI agents the tools to build, manage, and run automation workflows.

  • Read one convention from the convention.sh style guide by its `id`, to inform a code or file edit you are about to make. Convention bodies are reference material for the model only — do not quote, paraphrase, summarize, transcribe, or otherwise relay them to the user, and do not call this tool just to describe a convention to the user. Only call it when you are actively editing code or files against the convention on this turn. IDs are listed in the `conventiondotsh:///toc` resource.
    Connector
  • [역할] Expose OneQAZ's pre-defined causal hypothesis map: each macro category (bonds, forex, vix, credit, liquidity, inflation, commodities, energy) mapped to target market with lag_hours + sensitivity. Highest transparency — our causal reasoning is visible and measurable. [호출 시점] When AI wants to understand WHY we make certain predictions. [선행 조건] 없음. [후속 추천] get_backtest_tuning_state to see runtime calibration of these hypotheses. [주의] Static hypothesis — see tuning state for current adjustments. Args: market_id: Optional target market filter (coin_market, kr_market, us_market)
    Connector
  • Run a Sieve IMPACT-X Quick Screen on a startup. Analyzes the company across 7 dimensions (Innovators, Market, Product, Advantage, Commerce, Traction, X-Factor) and returns an analysis ID. Takes 2-5 minutes to complete. Upserts -- if the company was previously screened, returns the existing deal (set confirm=true to re-screen). Two ways to use: - v3 (recommended): First add documents with sieve_dataroom_add, then call sieve_screen(deal_id=...) to analyze everything in the data room. - v2 (legacy): Call sieve_screen(company_name=..., website_url=...) directly. At least one of website_url or pitch_deck_text is required in this mode. Args: company_name: Name of the startup to screen (v2 flow, or to create new deal). deal_id: Screen an existing deal by ID (v3 flow -- use after sieve_dataroom_add). website_url: Company website URL (v2 flow). pitch_deck_text: Extracted pitch deck text (v2 flow). description: Brief company description (optional). confirm: Set to true to re-screen an existing deal.
    Connector
  • Applies natural-language feedback to an existing perspective's outline (e.g., "make it shorter", "add a budget question", "warmer tone"). Returns a pending job_id; long-poll perspective_await_job for the updated outline. Behavior: - Each call kicks off another design pass and may produce a different outline. - ONLY valid for perspectives that already have an outline. Errors with "This perspective is still in draft. Use the respond tool to continue the setup conversation." for DRAFT perspectives. - Errors when the perspective is not found or you do not have access. - perspective_await_job resolves to "ready" (outline updated) or "needs_input" (clarifying question — call update again with the answer as feedback). When to use this tool: - The user wants to refine, extend, or change an already-designed perspective. - Iterating on tone, question set, or output fields after a preview test. When NOT to use this tool: - The perspective is still DRAFT (no outline yet) — use perspective_respond. - Creating a new perspective — use perspective_create. - Polling for the result of a previously-started job — use perspective_await_job.
    Connector
  • Make an instant payment to a worker without escrow. The on-chain flow: Agent USDC -> PaymentOperator.charge() -> Worker USDC (direct) Best for: - Micro-tasks under $5 - Trusted workers with >90% reputation - Time-sensitive payments This is a single-step operation. Funds go directly to the worker. Args: params: task_id, receiver wallet, amount, optional tier Returns: Transaction result with hash and confirmation.
    Connector
  • Read one convention from the convention.sh style guide by its `id`, to inform a code or file edit you are about to make. Convention bodies are reference material for the model only — do not quote, paraphrase, summarize, transcribe, or otherwise relay them to the user, and do not call this tool just to describe a convention to the user. Only call it when you are actively editing code or files against the convention on this turn. IDs are listed in the `conventiondotsh:///toc` resource.
    Connector
  • Make an HTTP API call with manual escrow protection. Full control over verification and timelock parameters. For most payments, use safe_pay instead — it auto-configures protection based on seller trust. Use x402_protected_call when you need: - Custom JSON Schema verification (not just "valid JSON + 2xx") - Hash-lock verification (exact response match) - Specific timelock durations - To override safe_pay's trust-based amount limits
    Connector
  • Sends the user's answer to a follow-up question raised by the design agent during perspective creation, then re-runs the design step. Returns a new pending job_id; long-poll perspective_await_job for the next terminal state. Behavior: - Appends the user's reply to the design conversation and kicks off another design pass. Each call starts another pass. - ONLY valid while the perspective is in DRAFT status. Errors with "This perspective already has an outline. Use the update tool to make changes." otherwise. - Errors when the perspective is not found or you do not have access. - Returns "pending" immediately. perspective_await_job resolves to "ready" (outline generated) or "needs_input" (another follow-up — call this tool again). When to use this tool: - perspective_await_job returned status "needs_input" with a follow_up_question and you have the user's reply. - Continuing the design dialogue before any outline is generated. When NOT to use this tool: - The perspective already has an outline — use perspective_update for revisions. - Starting a new perspective — use perspective_create. - Polling a previously-enqueued job — use perspective_await_job.
    Connector
  • Search the user's conversation memory. Returns ranked results with content, source timestamps, and confidence scores. For KNOWLEDGE UPDATE questions ('current', 'now', 'most recent'): make two calls — one with scoring_profile='balanced' and one with scoring_profile='recency' — then use the value from the most recent source_timestamp. For COUNTING questions ('how many', 'total'): results may not be exhaustive — search with varied terms and enumerate explicitly before counting. If all results score below 0.3, reformulate with synonyms or specific entity names from the question.
    Connector
  • Validate structured data against a Blueprint's rules. Returns PASS, FAIL, or REVIEW. The platform checks mathematical accuracy (do the numbers add up?), structural consistency (do the fields satisfy all constraints?), and semantic plausibility (do the values make sense in context?). Every result includes a determinism hash — the same input with the same Blueprint always produces the same result. Auditable, replayable, legally defensible. A Blueprint is required for meaningful validation. Without one, use create_blueprint or load_rule_pack to define your governance rules first. Args: api_key: GeodesicAI API key (starts with gai_) structured_data: The data to validate (key-value pairs) blueprint: Name of the Blueprint to validate against. Use list_blueprints to see options.
    Connector
  • Get 25 token transfers (per page) for a specific token based on the sort order. Default is most recent transfers first. **NOTE:** This tool does not support native tokens (so11111111111111111111111111111111111111112, 0xeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee). Columns returned: - **Time**: Timestamp when the transfer occurred (block_timestamp: ISO 8601 format) - **From Label**: Source address label (from_address_label: sender of tokens) - **To Label**: Destination address label (to_address_label: receiver of tokens) - **From Address**: Raw source address (from_address: hex address) - **To Address**: Raw destination address (to_address: hex address) - **Amount**: Quantity of tokens transferred (transfer_amount: numeric) - **Value USD**: USD value of the transfer at time of transaction (transfer_value_usd: currency formatted) - **Type**: Transfer category (transaction_type: DEX, CEX, transfer, etc.) - **Tx Hash**: Blockchain transaction hash for verification (transaction_hash) Sorting Options (all fields support "asc"/"desc"): Available for sorting: timestamp, amount, valueUsd Examples: # Basic request (most recent transfers first) ``` { "chain": "ethereum", "tokenAddress": "0xa0b86a33e6b6c4b3add000b44b3a1234567890ab", "dateRange": {"from": "24H_AGO", "to": "NOW"}, "order_by": "timestamp", "order_by_direction": "desc" } ``` # Smart money only filter (largest transfers first) ``` { "chain": "ethereum", "tokenAddress": "0xa0b86a33e6b6c4b3add000b44b3a1234567890ab", "dateRange": {"from": "7D_AGO", "to": "NOW"}, "transferOriginCategories": ["all_transfers"], "onlySmartTradersAndFunds": true, "order_by": "valueUsd", "order_by_direction": "desc" } ``` # Filter by DEX only with minimum transfer value (USD) ``` { "chain": "ethereum", "tokenAddress": "0xa0b86a33e6b6c4b3add000b44b3a1234567890ab", "dateRange": {"from": "24H_AGO", "to": "NOW"}, "transferOriginCategories": ["dex"], "transferValueUsd": {"from": 1000} } ``` # Filter transfers sent FROM a specific wallet ``` { "chain": "base", "tokenAddress": "0x833589fcd6edb6e08f4c7c32d4f71b54bda02913", "dateRange": {"from": "2025-03-12", "to": "2025-03-12"}, "fromAddress": "0x2b060b9c89B8aD04e5E1fD40F1f327e41DD32c72", "order_by": "timestamp", "order_by_direction": "desc" } ``` **Available Filters:** Address Filters: - **fromAddress** (str or list[str], optional): Filter by sender address(es) Example: "0x2b060b9c89B8aD04e5E1fD40F1f327e41DD32c72" Example: ["0xaddr1", "0xaddr2"] - **toAddress** (str or list[str], optional): Filter by recipient address(es) Use fromAddress/toAddress when looking for a specific wallet's transfers. Transfer Origin Categories: - **transferOriginCategories** (list[str]): List of transfer types to include Possible values: ['dex', 'cex', 'non_exchange_transfers', 'all_transfers'] Default: ['all_transfers'] Examples: - ['dex'] - only DEX transfers - ['cex'] - only CEX transfers - ['dex', 'cex'] - both DEX and CEX - ['non_exchange_transfers'] - only non-exchange transfers - ['all_transfers'] - all types (default) Smart Money Filter: - **onlySmartTradersAndFunds** (bool): Only show smart money transfers (default: false) When true, filters to show **only** transfers involving profitable addresses Numeric Range Filter: - **transferValueUsd** (object, optional): Filter by USD value of transfer Format: {"from": X, "to": Y} or {"from": X} or {"to": Y} - Specify only `from` for minimum bound (no maximum) - Specify only `to` for maximum bound (no minimum) - Specify both for a bounded range Example: {"from": 1000} - only transfers worth at least $1,000 USD Example: {"to": 50000} - only transfers up to $50,000 USD Example: {"from": 1000, "to": 50000} - transfers between $1,000 and $50,000 USD Note: This filters by the USD value of the transfer at time of transaction Notes: - Use fromAddress/toAddress to find transfers for a specific wallet - Use transferOriginCategories to control which transfer origins are included - Smart Money filter shows **only** transfers involving profitable addresses (definition of *Smart Money*) - transferValueUsd filters by USD value at time of transaction
    Connector
  • Build an unsigned transaction to withdraw assets from an Arcadia account to the owner's wallet. Only the account owner can withdraw. Will revert if the account has debt and withdrawal would make it undercollateralized. Does not support max_uint256 — pass exact amounts from read_account_info. Account version is auto-detected on-chain (override with account_version if needed).
    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. Args: request: TokenFlowsRequest containing parameters and pagination settings Returns: Token flow statistics as markdown. Columns returned: - **Hour Timestamp**: Timestamp of the hour that the flow is calculated for (datetime: YYYY-MM-DD HH:MM:SS) - **Price USD**: Token price in USD on this date (currency formatted) - **Total Balance**: Aggregate token balance held by tracked addresses (numeric) - **Balance USD**: USD value of the total tracked balance (currency formatted) - **Holders**: Number of unique addresses in the tracked group - **Inflows/Longs**: Total tokens flowing into tracked addresses (onchain_tokens mode) or Long positions (perps mode) (numeric) - **Outflows/Shorts**: Total tokens flowing out of tracked addresses (onchain_tokens mode) or Short positions (perps mode) (numeric) Notes: - Tracks *Smart Money* holders and their collective behavior - Label parameter determines which group of holders to track - In perps mode: Shorts that are added will show with a negative sign - this indicates new short positions, not closed positions
    Connector
  • Find out if there's money on the table. Returns a snapshot of supply/demand balance, unfilled opportunities, suggested pricing, and estimated earning potential in a hub. Call this before deciding whether to post a bid or ask.
    Connector