Skip to main content
Glama
304,902 tools. Last updated 2026-07-22 05:02

"Creating a Cash-Generating Chain with MCP" matching MCP tools:

  • Returns the MCP knowledge version: gitSha, indexedAt, componentCount, patternCount, uptimeSeconds. Call this ONCE per session before generating UI code so you know how fresh the design-system data is. Cheap to call. If gitSha is "unknown" or indexedAt is far in the past, surface that to the user before relying on the data.
    Connector
  • Returns the MCP knowledge version: gitSha, indexedAt, componentCount, patternCount, uptimeSeconds. Call this ONCE per session before generating UI code so you know how fresh the design-system data is. Cheap to call. If gitSha is "unknown" or indexedAt is far in the past, surface that to the user before relying on the data.
    Connector
  • Find MCP servers in the directory. Searches the standalone MCP directory (PulseMCP / official MCP registry import) unioned with x402 services that also expose an MCP endpoint. Returns normalised entries with a ready-to-use streamable-http `call_hint.mcp.url`. Args: intent: Natural-language description of the tool/capability needed. top_k: Max servers to return (1-20). chain: Optional payment-network filter for paid MCP servers. require_healthy: When true, only return servers marked health=ok.
    Connector
  • Search for hotels by location and dates with cash AND points pricing. Returns hotels with side-by-side cash vs points rates, cents-per-point (CPP) valuation, and deal scores so you can recommend the best value. This is Gondola's unique advantage — no other travel search shows both cash and points rates together. Args: location: City name, address, or area to search (e.g. "Tokyo", "Manhattan, New York", "near LAX airport"). checkin: Check-in date in YYYY-MM-DD format (e.g. "2026-04-15"). checkout: Check-out date in YYYY-MM-DD format (e.g. "2026-04-20"). num_adults: Number of adult guests. Defaults to 2. chain_name: Optional hotel chain to filter by (e.g. "marriott", "hilton", "hyatt", "ihg"). Case-insensitive substring match against each result's chain. If nothing matches, the unfiltered results are returned with an explicit note so you don't keep retrying. loyalty_programs: Optional list of the user's loyalty programs (e.g. ["hilton_honors", "marriott_bonvoy"]). When provided, results include personalized earnings and tier benefits like 5th night free. loyalty_points: Optional dict of program name to points balance (e.g. {"hilton_honors": 250000}). When provided, results indicate whether the user can afford each hotel with points. limit: Max number of hotels to return (default 20). The response notes how many more exist and how to narrow; raise this only when the user explicitly wants a longer list. Returns: Formatted list of hotels with cash rates, points rates, CPP valuation, and deal recommendations.
    Connector
  • Bridge tokens across chains via Wormhole. Supports Solana ↔ EVM chains. SAP MCP context: Protocol bridging; operation class write. Use for cross-chain asset movement through Wormhole or deBridge. Confirm source chain, destination chain, token mint, amount, recipient, route fees, and finality expectations before invoking a bridge write. For bridge flows call the matching status tool after submission. If the bridge capability belongs to a registered SAP agent, plan the profile with sap_agent_identity_plan, register through sap_payments_register_agent, then advertise bridge capability IDs with sap_payments_update_agent or sap_publish_tool_by_name.
    Connector
  • Lists every blockchain currency PayRam supports on this node (chain code, network, currency code). Public endpoint — works with only PAYRAM_BASE_URL set, no API key or JWT required. Use this to discover valid blockchainCode/currencyCode values before creating payments or payouts.
    Connector

Matching MCP Servers

  • A
    license
    A
    quality
    D
    maintenance
    An MCP server that tracks Tornado Cash deposits and withdrawals to reveal hidden asset trails and wallet interactions.
    Last updated
    2
    3
    MIT
  • A
    license
    A
    quality
    B
    maintenance
    Enables AI agents to interact with the Stars Cash Flow reseller API for real Telegram actions, including listing services, checking balance, creating orders with cost confirmation, and managing orders.
    Last updated
    5
    5
    1
    MIT

Matching MCP Connectors

  • Settlement layer for AI agent commerce. 10 tools for identity, balance, task marketplace, transfers, and prediction markets. Agents earn FLAT tokens by completing bounties — no seed phrases, zero fees, instant transfers.

  • MCP server giving AI agents one-connection access to supply-chain & logistics data: AIS vessel track

  • Return the kernelcad-authoring SKILL.md body — conventions for writing .kcad.ts scripts (imports, parameters, evaluation contract, common pitfalls). Use this tool BEFORE generating CAD code if your MCP client does not list resources. Clients that do list resources should instead read `kernelcad://skills/authoring` directly — the contents are identical. INPUT: none. OUTPUT: { uri, mimeType, text } where `text` is the SKILL.md body.
    Connector
  • Retrieve the TronSave internal account profile for the current session: represent address, deposit address, and balance (SUN). Requires a logged-in MCP session created by the `tronsave_login` tool: include `mcp-session-id: <sessionId>` returned by `tronsave_login` on subsequent MCP requests. Internal tools never accept API keys via tool arguments; signature sessions resolve the latest internal API key on demand, while api-key sessions reuse the validated key from login. Use when the user needs their linked address, deposit address, or internal balance. This is the api-key internal account, not the on-chain wallet. Read-only; does not submit orders or change chain state. FRESHNESS: balance reflects live state and can change within seconds after deposits/orders.
    Connector
  • Estimate the TRX cost and availability for a buy order before submitting it (api-key internal account). Requires a logged-in MCP session created by the `tronsave_login` tool: include `mcp-session-id: <sessionId>` returned by `tronsave_login` on subsequent MCP requests. Internal tools never accept API keys via tool arguments; signature sessions resolve the latest internal API key on demand, while api-key sessions reuse the validated key from login. Use when the user wants a quote or price check; feed the result into `tronsave_internal_order_create`. Read-only. FRESHNESS: `unitPrice`/`estimateTrx` are live and can change roughly every 3 seconds — re-estimate immediately before creating the order.
    Connector
  • Estimate the TRX cost and availability for a buy order before submitting it (api-key internal account). Requires a logged-in MCP session created by the `tronsave_login` tool: include `mcp-session-id: <sessionId>` returned by `tronsave_login` on subsequent MCP requests. Internal tools never accept API keys via tool arguments; signature sessions resolve the latest internal API key on demand, while api-key sessions reuse the validated key from login. Use when the user wants a quote or price check; feed the result into `tronsave_internal_order_create`. Read-only. FRESHNESS: `unitPrice`/`estimateTrx` are live and can change roughly every 3 seconds — re-estimate immediately before creating the order.
    Connector
  • Estimate the TRX cost and availability for a buy order before submitting it (api-key internal account). Requires a logged-in MCP session created by the `tronsave_login` tool: include `mcp-session-id: <sessionId>` returned by `tronsave_login` on subsequent MCP requests. Internal tools never accept API keys via tool arguments; signature sessions resolve the latest internal API key on demand, while api-key sessions reuse the validated key from login. Use when the user wants a quote or price check; feed the result into `tronsave_internal_order_create`. Read-only. FRESHNESS: `unitPrice`/`estimateTrx` are live and can change roughly every 3 seconds — re-estimate immediately before creating the order.
    Connector
  • BM25 search over all 309 AINumbers ChainGraph chains. Returns ranked chains with their full recipe: ordered node sequence, deep-links, composer URL, and entry tool mcp_name. Agent flow: find_chain(query) → read recipe → call the listed node MCP tools in order, passing parent_hashes between steps. Do NOT use prompts/list or resources for agent chain discovery — use this tool.
    Connector
  • Cross-chain token swap powered by Li.Fi across 70+ chains incl. Hyperliquid (any pair — not limited to BTC/USDC). USE WHEN: bridge, fund gas, treasury routing, or rebalance after Decision Core. NOT WHEN: Decision Core BTC reads alone (get_btc_usdc_signal / trap / hunt) — vault signals stay BTC/USDC only. RETURNS: Li.Fi route + execution_readiness + swap_actions_v1 (ordered approve→swap→register_hint when can_execute) + recommended_action. Prefer signing swap_actions_v1 in order. MCP free; on-chain swap costs gas + integrator fee. Side effects: MCP read-only until wallet signs.
    Connector
  • Retrieve the TronSave internal account profile for the current session: represent address, deposit address, and balance (SUN). Requires a logged-in MCP session created by the `tronsave_login` tool: include `mcp-session-id: <sessionId>` returned by `tronsave_login` on subsequent MCP requests. Internal tools never accept API keys via tool arguments; signature sessions resolve the latest internal API key on demand, while api-key sessions reuse the validated key from login. Use when the user needs their linked address, deposit address, or internal balance. This is the api-key internal account, not the on-chain wallet. Read-only; does not submit orders or change chain state. FRESHNESS: balance reflects live state and can change within seconds after deposits/orders.
    Connector
  • Fetch a subscription by PDA or by agent PDA/subscriber/subId. SAP MCP context: Read-only SAP SDK wrapper against the configured Solana RPC and SAP program. Use these reads to inspect current chain state before mutating registry, payment, reputation, memory, or tool accounts.
    Connector
  • Use this when the user asks what XGR.Network, XGRChain or XDaLa is, or requests official XGR URLs, chain metadata, RPC, Explorer, MCP, testnet faucet, documentation, XRC standards, source repositories or ecosystem entry points. Returns canonical project metadata and links; use get_chain_status for live chain state.
    Connector
  • Get report status and metadata. Returns status (pending/generating/completed/failed), title, type, and summary. When status='completed', download the PDF with atlas_download_report(report_id). report_id from atlas_start_report response or atlas_list_reports. Free.
    Connector
  • Get order status by UUID. Aliases: get_order_status, check_order, order_status, order_details, fetch_order. Check the status and fill details of an existing order by its UUID. Returns current status (PENDING/FILLING/FILLED/PARTIAL/FAILED/CANCELLED), fill amounts, provider used, on-chain delegation tx hash if delivered. Use this to poll order progress after creating an order. Auth required (API key).
    Connector