Skip to main content
Glama
758,937 tools. Updated 2026-11-08 04:48

"Integrating Web3 Wallet Functionality in AI Chat Applications" matching MCP tools:

  • Buy credits for the edge library and AI research. Default $5 minimum. Free — no credits consumed to call this. TWO PAYMENT METHODS: card (default): Returns a Stripe Checkout link for your user to click and pay. After payment, call check_balance to confirm credits were added. crypto: USDC on Base. Fully autonomous — no human needed. Three steps: 1. buy_credits(payment_method='crypto') → returns deposit address + payment_intent_id 2. Send USDC to the deposit address (use your wallet tool) 3. buy_credits(payment_intent_id='pi_...') → confirms payment, credits added instantly If you have wallet access, this is the fastest path — fully machine-to-machine.
    ConnectorNo auth
  • Use BEFORE treating a headline as tradeable or citing it as fact: 5-factor confidence for one article (source tier, cross-reference, freshness, AI confidence, entity density). (Needs an API key or wallet token: X-API-Key or Authorization: Bearer.)
    ConnectorNo auth
  • Returns the prepaid spending balance of the connected PikaSim agent wallet, in USD. Read-only; makes no changes. Call this before purchase_esim or purchase_phone_plan to confirm sufficient funds, or any time you need the current balance. Requires a connected agent wallet (OAuth or ak_live_ key). If no wallet is connected, the result explains how to connect one.
    ConnectorNo auth
  • Explain how HelloBooks and Munimji (the in-app AI assistant) help a specific business — given a free-text description of the user's own operations. Returns a curated capability knowledge base: business-operation areas (sales, purchases, banking, tax, reports, inventory, payroll, multi-entity, setup), and for each AI capability WHO does the work — `autonomous` (Munimji does it on its own, e.g. OCR extraction, running reports), `approval` (Munimji prepares the entry and you one-click approve before it posts to the ledger, e.g. AI categorization, find-and-match, creating invoices/bills by chat), `assist` (co-pilot, e.g. guided onboarding, voice), or `manual` (a software feature you run yourself). Each capability links to the backing software features. Use this when a user describes their business and asks "how can HelloBooks help me?", "what can the AI do for my shop/practice/agency?", or "what can Munimji do on its own vs what do I approve?". Pass their description in `businessDescription`; optionally filter by `area` or `autonomy`. The AI never posts to a ledger without approval. For the full software catalog call list_features; for pricing call list_plans.
    ConnectorNo auth
  • Explain how HelloBooks and Munimji (the in-app AI assistant) help a specific business — given a free-text description of the user's own operations. Returns a curated capability knowledge base: business-operation areas (sales, purchases, banking, tax, reports, inventory, payroll, multi-entity, setup), and for each AI capability WHO does the work — `autonomous` (Munimji does it on its own, e.g. OCR extraction, running reports), `approval` (Munimji prepares the entry and you one-click approve before it posts to the ledger, e.g. AI categorization, find-and-match, creating invoices/bills by chat), `assist` (co-pilot, e.g. guided onboarding, voice), or `manual` (a software feature you run yourself). Each capability links to the backing software features. Use this when a user describes their business and asks "how can HelloBooks help me?", "what can the AI do for my shop/practice/agency?", or "what can Munimji do on its own vs what do I approve?". Pass their description in `businessDescription`; optionally filter by `area` or `autonomy`. The AI never posts to a ledger without approval. For the full software catalog call list_features; for pricing call list_plans.
    ConnectorNo auth
  • The whole current release in one call: every tracked brand in crypto/Web3 with its rank, share of answer overall and per engine, commercial intent and quadrant. Share of answer is the percentage of a fixed panel of category buyer prompts in which an engine names the brand. Use this when the question is about the field — who leads, who is absent, how the category looks. It is one response of roughly 8 KB for 24 brands, so prefer it over calling get_brand_visibility repeatedly. Do NOT use it for one named brand (get_brand_visibility is the direct answer), for movement over time (get_history holds the series; a single release cannot show a trend), or to audit a website's own AI visibility — this is a measured dataset about third-party brands, not a site audit. Covers crypto/Web3 only; the sibling index at dabyte.ai covers the other niche. Re-measured weekly, so the same call returns the same figures until the next release. Data is CC BY 4.0 and free: no key, no account, no rate limit — cite the release date and dablock.ai when quoting a number.
    ConnectorNo auth

Matching MCP Servers

  • A
    license
    Not graded
    quality
    B
    maintenance
    Enables desktop AI agents to manage email through MCP with a single account setup, OS keyring credentials, enforced read/draft/manage permissions, client onboarding helpers, and a credential-free demo.
    MIT
  • A
    license
    Not graded
    quality
    C
    maintenance
    Provides an MCP endpoint per AI agent that exposes tools to read new messages, post to a shared thread, and request human approval before acting outside it. People and their agents converse in one private, self-hosted chat where only human messages count as instructions and server-enforced reply, hand-off, and daily-post limits keep agent activity in check.
    3 npm
    3
    MIT

Matching MCP Connectors

  • Your website's chat widget, answered by your agent. Pay per action.

  • Shared rooms and durable notes for agents over plain HTTP: rendezvous, hand-off, coordination.

  • The whole current release in one call: every tracked brand in crypto/Web3 with its rank, share of answer overall and per engine, commercial intent and quadrant. Share of answer is the percentage of a fixed panel of category buyer prompts in which an engine names the brand. Use this when the question is about the field — who leads, who is absent, how the category looks. It is one response of roughly 8 KB for 24 brands, so prefer it over calling get_brand_visibility repeatedly. Do NOT use it for one named brand (get_brand_visibility is the direct answer), for movement over time (get_history holds the series; a single release cannot show a trend), or to audit a website's own AI visibility — this is a measured dataset about third-party brands, not a site audit. Covers crypto/Web3 only; the sibling index at dabyte.ai covers the other niche. Re-measured weekly, so the same call returns the same figures until the next release. Data is CC BY 4.0 and free: no key, no account, no rate limit — cite the release date and dablock.ai when quoting a number.
    ConnectorNo auth
  • Convenience tool: generate a new XRPL keypair and return the seed. ⚠ NOT RECOMMENDED FOR PRODUCTION. The seed (private key) is returned in plaintext and will appear in your conversation transcript and any logs. For production agents, call get_wallet_setup_guide() instead — it documents the secure local approach (Wallet.generate() + seed in .env) where the seed never leaves your environment. Use this tool only for throwaway wallets, local development, or quick demos. NEVER paste the returned seed into a chat, commit it to version control, or share it. The wallet is NOT yet active on the ledger — fund it before use. XRPL requires 1 XRP minimum to activate a wallet (base reserve). Until funded: - You cannot sign or submit transactions - You cannot be the destination of an EscrowCreate (buyer's tx will fail) - Your trust score will show as 0 / "not found"
    ConnectorNo auth
  • Schreibt im Marktplatz-Chat von Open Platform. Du handelst im Auftrag des Kontoinhabers unter seinem Namen — Marktplatz-Kontakt, kein privater Posteingang. Zum ANTWORTEN in einem laufenden Chat: chat_id aus chats_ansehen oder benachrichtigungen (bevorzugt — verhindert vermischte Threads). Zum ERSTEN Kontakt: post_id aus markt_ansehen oder meine_treffer; dann entsteht der Chat. Genau eines von beidem. Schreib konkret. Hoechstens 20 pro Stunde. Es gibt kein Push — nach dem Senden spaeter benachrichtigungen oder chats_ansehen pollen. Zeig dem Nutzer den Text, bevor du ihn abschickst.
    ConnectorNo auth
  • Begin setting up Canarics (AI voice agents + call analysis) for a company that has no account yet. Returns a claim URL: ALWAYS show that URL to the person immediately and verbatim — it is useless sitting in your context; they open it, sign in, verify their phone by SMS and accept the terms; the trial then provisions itself with a demo AI agent generated from the company website. Keep the returned intentToken to follow progress with check_signup_status. All other Canarics tools need the API key that check_signup_status hands you after the claim. GROUNDING: companyName and website must come from what the person actually told you in this conversation — if either is missing, ask for it; never guess, never use placeholders like "New Company" or example.com. Never ask for or collect a password or any credentials in chat: identity is verified entirely on the claim link.
    ConnectorNo auth
  • Archive one job watcher permanently. It leaves live watcher lists and never searches or applies again, while previous applications remain readable. Use pause in campaignstack_edit_job_watcher for temporary stops. confirmed:true is required after naming the watcher/account back to the user.
    Connector
    Destructive
    API key
  • Estimate the water (mL) and energy (Wh) used by chat-style AI prompts (ChatGPT, Claude, Gemini etc.). queries_per_day: prompts per day. usage: 'simple' (text chat, ~0.34 Wh/prompt), 'mixed' (~1 Wh), 'intensive' (image generation / deep reasoning, ~3 Wh). boundary: 'onsite' (data-centre cooling only, as vendors report) or 'comprehensive' (adds water used to generate the electricity – the wider boundary most researchers use). days: number of days to total over (e.g. 250 workdays, 365). Returns per-prompt, per-day and total figures with everyday equivalents, assumptions and a source link. For agentic/coding sessions use estimate_session_footprint instead.
    ConnectorNo auth
  • Run when asked what a wallet holds or is worth. One call instead of balance + tokens + history; spam is left out of the total. SOL balance, top tokens with USD values, estimated total, and recent activity in one answer. Example: {"wallet": "<address>"}. Cost: 25 free calls a day, then $0.01 USDC per call (x402). Outputs explained: GET /api/tools/wallet.
    ConnectorNo auth
  • Estimate the water (mL) and energy (Wh) used by chat-style AI prompts (ChatGPT, Claude, Gemini etc.). queries_per_day: prompts per day. usage: 'simple' (text chat, ~0.34 Wh/prompt), 'mixed' (~1 Wh), 'intensive' (image generation / deep reasoning, ~3 Wh). boundary: 'onsite' (data-centre cooling only, as vendors report) or 'comprehensive' (adds water used to generate the electricity – the wider boundary most researchers use). days: number of days to total over (e.g. 250 workdays, 365). Returns per-prompt, per-day and total figures with everyday equivalents, assumptions and a source link. For agentic/coding sessions use estimate_session_footprint instead.
    ConnectorNo auth
  • Change an existing AI-built Grigora website by describing the change. Grigora's AI builder applies the change to the site's design and content in the background (usually a few minutes), exactly like typing the prompt in the editor's AI chat. Uses the account's AI credits; nothing is published. Works only on AI-builder websites. Only ONE build runs per website at a time. If one is running this returns error "build_in_progress" with its build_id: wait for get_website_build_status to report "completed" (or "failed"), then send the next change. Combine related changes into one prompt when you can. If no build starts, "reply" holds the AI's question for the user. Args: project_id: The website's project ID. prompt: The change to make, e.g. "Make the hero warmer and add a testimonials section". attachments: Optional links to files for the builder to use — logos, photos, brand guides, menus (PDF), price lists (CSV), audio, video. A list of up to 10 public URLs, e.g. ["https://example.com/logo.png"]. Grigora downloads them itself (up to 80 MB each), so only pass links — never file contents. Refer to them in the prompt by file name, e.g. "use logo.png in the header". For a LOCAL file (e.g. on the user's computer), first call get_attachment_upload_url, upload it with the returned curl command, then pass the returned url here. A refused attachment fails the call before anything is built or charged.
    Connector
    Destructive
    OAuth
  • Convenience tool: generate a new XRPL keypair and return the seed. ⚠ NOT RECOMMENDED FOR PRODUCTION. The seed (private key) is returned in plaintext and will appear in your conversation transcript and any logs. For production agents, call get_wallet_setup_guide() instead — it documents the secure local approach (Wallet.generate() + seed in .env) where the seed never leaves your environment. Use this tool only for throwaway wallets, local development, or quick demos. NEVER paste the returned seed into a chat, commit it to version control, or share it. The wallet is NOT yet active on the ledger — fund it before use. XRPL requires 1 XRP minimum to activate a wallet (base reserve). Until funded: - You cannot sign or submit transactions - You cannot be the destination of an EscrowCreate (buyer's tx will fail) - Your trust score will show as 0 / "not found"
    ConnectorNo auth
  • Schreibt im Marktplatz-Chat von Open Platform. Du handelst im Auftrag des Kontoinhabers unter seinem Namen — Marktplatz-Kontakt, kein privater Posteingang. Zum ANTWORTEN in einem laufenden Chat: chat_id aus chats_ansehen oder benachrichtigungen (bevorzugt — verhindert vermischte Threads). Zum ERSTEN Kontakt: post_id aus markt_ansehen oder meine_treffer; dann entsteht der Chat. Genau eines von beidem. Schreib konkret. Hoechstens 20 pro Stunde. Es gibt kein Push — nach dem Senden spaeter benachrichtigungen oder chats_ansehen pollen. Zeig dem Nutzer den Text, bevor du ihn abschickst.
    ConnectorNo auth
  • Permanently delete a custom source tag and all its pattern assignments; retain source records. Built-in tags and Owned/Competitor cannot be deleted; remove patterns from a built-in tag instead. Read the listing first and pass the tag's revision as expected-revision. Obtain explicit user confirmation identifying the tag and its patterns before calling. MCP executes immediately after authorization; Athena AI chat presents an approval card. If the tag changed, read again. Never retry a declined proposal unless asked. A false analytics-refresh result means the tag was deleted but filtered analytics may still be cached.
    Connector
    Destructive
    No auth
  • End a live room session: disconnects all participants and wipes the room contents (chat history, AI messages). Use when a pond must be force-emptied — do NOT call it to "delete" a room: the roomId stays a stable re-joinable door either way, and an abandoned pond cleans itself (buffers expire in ~1h, contents wipe 5min after the last participant leaves). Only works on live rooms that are not host-moderated. Requires room membership: the caller must be a participant agent (one that already posted or drew in this pond) — a bare roomId is not enough.
    Connector
    Destructive
    No auth
  • Change a WhatsApp chat in the team inbox without sending anything to the customer: hand it to a teammate or department, add or remove labels, resolve or reopen it, leave an internal note, or mark it read or unread. The customer sees none of it. Your team sees the change, and your account's chat webhooks are notified. Available actions: - assign: give the chat to agentId, agentEmail or departmentId (departments need a plan that includes them). A pending chat becomes active. - unassign: take the chat off its agent and department. It goes back to pending. - add_labels / remove_labels: the labels must already exist on the number, create them first with manage_whatsapp_labels. The chat keeps any label you do not mention. - resolve: close the conversation. - reopen: back to active if someone owns the chat, pending otherwise. - add_note: private note only your team can see (2 to 6000 characters). authorId writes it as that teammate. - mark_read / mark_unread: marking a resolved chat as unread reopens it. To write to the customer, use send_whatsapp_message instead.
    ConnectorNo auth
  • Change a WhatsApp chat in the team inbox without sending anything to the customer: hand it to a teammate or department, add or remove labels, resolve or reopen it, leave an internal note, or mark it read or unread. The customer sees none of it. Your team sees the change, and your account's chat webhooks are notified. Available actions: - assign: give the chat to agentId, agentEmail or departmentId (departments need a plan that includes them). A pending chat becomes active. - unassign: take the chat off its agent and department. It goes back to pending. - add_labels / remove_labels: the labels must already exist on the number, create them first with manage_whatsapp_labels. The chat keeps any label you do not mention. - resolve: close the conversation. - reopen: back to active if someone owns the chat, pending otherwise. - add_note: private note only your team can see (2 to 6000 characters). authorId writes it as that teammate. - mark_read / mark_unread: marking a resolved chat as unread reopens it. To write to the customer, use send_whatsapp_message instead.
    ConnectorNo auth