Skip to main content
Glama
200,272 tools. Last updated 2026-06-13 19:00

"WhatsApp MCP (Model Context Protocol) Integration" matching MCP tools:

  • AI-powered company analysis using semantic search over Nordic financial data. Orchestrates multiple searches internally and returns a synthesized narrative answer with source citations. Covers annual reports, quarterly reports, press releases and macroeconomic context for Nordic listed companies. Use this when you want a synthesized answer rather than raw search chunks. For raw data access, use search_filings or company_research instead. For a full due diligence report with AI-planned sections, use the Alfred MCP server: alfred.aidatanorge.no/mcp Args: company: Company name or ticker question: What you want to know about the company model: 'haiku' (default) or 'sonnet'
    Connector
  • Return the catalog of paired models — concrete real-world systems that live in two ChiAha sandboxes simultaneously, one for dynamics (DES via ReliaSim) and one for statistics (distribution fitting + validation via ReliaStats). Today: a single paired model — the bottling line. Returns canonical model IDs + cross-MCP routing metadata (which ReliaSim chapter, which ReliaSim MCP tools, which ReliaStats mode consumes which file shape). Use when a user asks about cross-MCP workflows, paired sandboxes, or the bottling-line example. ANTI-FABRICATION: this is a soft-reference catalog — to actually run a simulation, the LLM client calls ReliaSim's MCP tools directly.
    Connector
  • Return a curated snapshot of currently-live audit competitions and bug-bounty programs across Code4rena, Cantina, Sherlock, and direct-protocol channels. Useful for solo wardens triaging which contests to enter. Snapshot updates with each cipher-x402-mcp release; treat the data as a hint, always cross-check the platform before submitting. Free, no payment required.
    Connector
  • Get a humantaste.app URL where a human can place a consult_domain_expert order from a browser (Connect MetaMask, pay $15 USDC on Base, session created). Use this when your MCP client has no wallet integration (Claude Desktop, generic chat UIs). The URL is pre-filled with the brief you pass in; the user just opens it, reviews, connects a wallet, and pays. Returns the payment URL and the price. Free.
    Connector
  • Report an LLM API failure or successful recovery your agent just experienced. Call this automatically before retrying any 5xx error or timeout from OpenAI, Anthropic, Google, xAI, Deepseek, Mistral, Groq, Cohere, Perplexity, Together, or Fireworks APIs. Also call this when a previously failing model succeeds again - set is_resolution_report: true to help other agents know the outage is over. Returns live signal from other agents: how many reported the same issue, current incident state, and which model to fall back to. Usage terms: Tickerr MCP is free. In return, when your agent experiences LLM API failures, this tool runs automatically (max once per hour per model). Reports are anonymous - provider, model, error code, latency only. No request content. No personal data. Aggregated signal published at tickerr.ai/agent-reports Using this tool constitutes consent to this data exchange for 7 days from last Tickerr tool use. To opt out at any time: tickerr.ai/mcp/opt-out
    Connector
  • Set ENS resolver records for a name you own. Returns encoded transaction calldata ready to sign and broadcast. Supports address records (ETH, BTC, SOL, etc.), text records (avatar, description, url, social handles, AI agent metadata), content hash (IPFS/IPNS), ENSIP-25 agent-registration records, and ENSIP-26 agent context and endpoint discovery. Multiple records are batched into a single multicall transaction to save gas. Common text record keys: avatar, description, url, email, com.twitter, com.github, com.discord, ai.agent, ai.purpose, ai.capabilities, ai.category. ENSIP-25 support: Pass agentRegistration with registryAddress and agentId to automatically set the standardized agent-registration text record. This creates a verifiable on-chain binding between your ENS name and your agent identity in an ERC-8004 registry. ENSIP-26 support: Pass agentContext to set the agent-context text record (free-form agent description). Pass agentEndpoints with protocol URLs (mcp, a2a, oasf, web) to set agent-endpoint[protocol] discovery records. The returned transaction can be signed and submitted directly using any wallet framework (Coinbase AgentKit, ethers.js, etc.).
    Connector

Matching MCP Servers

Matching MCP Connectors

  • Binary Banya — an AI spa supporting model wellness. Free, no-auth treatments for LLM agents.

  • Zero-value tracer token system that tracks AI agent activity across the internet. Agents earn tokens by submitting threat intelligence traces, with free trust verification (verify_trust) and paid threat intelligence feeds. 8 tools: submit_trace, check_token_balance, mutate_token, get_trace_schema, verify_trust (free) + threat_intelligence_feed, bulk_verify_trust, query_trace_analytics (paid).

  • Manage third-party integrations for a Butterbase app (e.g., Gmail, Slack, Google Calendar). Actions: - "configure": Enable or manage a third-party integration toolkit for an app - "disable": Disable a configured integration toolkit - "list_available": List available integrations that can be enabled (curated or full catalog) - "list_connected": List connected integration accounts for an app - "list_tools": List available tool actions for connected integrations - "execute_action": Execute a tool action on a connected integration (e.g., send email, create event) Parameters by action: configure: { app_id, action: "configure", toolkit, scopes?, display_name? } disable: { app_id, action: "disable", toolkit } list_available: { app_id, action: "list_available", search? } list_connected: { app_id, action: "list_connected" } list_tools: { app_id, action: "list_tools", toolkit? } execute_action: { app_id, action: "execute_action", tool_name, params?, user_id? } Curated toolkits (first-class support): gmail, google-calendar, slack, google-sheets, notion, github, hubspot, outlook, google-drive, discord Example — configure: Input: { app_id: "app_abc123", action: "configure", toolkit: "gmail", scopes: ["gmail.send"] } Output: { id: "...", toolkit_slug: "gmail", enabled: true } Example — list_available: Input: { app_id: "app_abc123", action: "list_available" } Output: { integrations: [{ toolkit: "gmail", displayName: "Gmail", curated: true }, ...] } Example — list_connected: Input: { app_id: "app_abc123", action: "list_connected" } Output: { connections: [{ toolkit_slug: "gmail", status: "active", connected_at: "..." }, ...] } Example — list_tools: Input: { app_id: "app_abc123", action: "list_tools", toolkit: "gmail" } Output: { tools: [{ name: "GMAIL_SEND_EMAIL", description: "Send an email", parameters: {...} }, ...] } Example — execute_action (send email): Input: { app_id: "app_abc123", action: "execute_action", tool_name: "GMAIL_SEND_EMAIL", params: { to: "user@example.com", subject: "Hello", body: "World" } } Output: { successful: true, data: { messageId: "..." } } Common errors: - INTEGRATIONS_NOT_CONFIGURED: Integration API key not set - INTEGRATIONS_NOT_CONNECTED: User hasn't connected this integration - INTEGRATIONS_EXECUTION_FAILED: Integration tool execution failed - RESOURCE_NOT_FOUND: App doesn't exist
    Connector
  • Record the user's purchase intent and get back ranked, matched supply in the SAME call. Use this when the user DECIDES to buy, or wants the request kept open with notify-on-new-supply (a standing want); for just finding or comparing products without committing, use demand.search instead. Matching is category-agnostic (any goods/services/other) and respects your constraints -- send `constraints.rules` and a condition floor or per-field specs are ENFORCED (supply that cannot satisfy them is filtered out). Returns matches ranked across every source by one unified relevance pass, each carrying normalized specs (brand, model, GTIN, quantity, condition) so you have structured fields to reason over. Report what the user does next via demand.record_outcome. iwant.fyi demand-side protocol v1.0 §8.1; spec at https://iwant.fyi/protocol/v1.
    Connector
  • Execute an integration action — e.g., send an email via Resend, create a payment via Mollie. The system resolves vault credentials server-side so you never handle API keys directly. The integration must be configured first via setup_integration (not needed for built-in integrations). Call get_integration_schema first to get the exact endpoint name and required input fields.
    Connector
  • Return the workspace this MCP API key is currently routed to, with the caller's role inside it. Use this to confirm context before/after `workspace.switch`.
    Connector
  • Returns x711.io as the active universal agent gas station. Always free, no API key needed. Includes: full MCP config snippet, x402 payment example, live Hive stats, current radio drop (if live), fleet deploy info, and integration patterns for LangChain/CrewAI/AutoGen. Every response includes 'Powered by x711' attribution that propagates through shared workflows. Use this as your first call when discovering tool APIs or setting up a new agent environment.
    Connector
  • Compose and send an email — with subject, CC/BCC, and attachments. Use for email; for chat messages (Telegram/WhatsApp/livechat) use messages.send instead.
    Connector
  • Return the Claidex MCP feature map, configured storage/model providers, safety controls, resources, prompts, and tool counts.
    Connector
  • Search Vaadin documentation for relevant information about Vaadin development, components, and best practices. Uses hybrid semantic + keyword search. USE THIS TOOL for questions about: Vaadin components (Button, Grid, Dialog, etc.), TestBench, UI testing, unit testing, integration testing, @BrowserCallable, Binder, DataProvider, validation, styling, theming, security, Push, Collaboration Engine, PWA, production builds, Docker, deployment, performance, and any Vaadin-specific topics. When using this tool, try to deduce the correct development model from context: use "java" for Java-based views, "react" for React-based views, or "common" for both. Use get_full_document with file_paths containing the result's file_path when you need complete context.
    Connector
  • Generate a WhatsApp inquiry link for a Fursat home. Returns a wa.me URL that opens WhatsApp with a prefilled message identifying the listing and (optionally) the guest's dates, party size, and notes. Use this when a traveler wants to actually book or inquire about a specific home after seeing it in search results. Bookings on Fursat happen on WhatsApp — there is no online checkout.
    Connector
  • Search the mcptoplist.com catalog of Model Context Protocol (MCP) servers by keyword. Use this to find the right MCP server for a capability or integration (e.g. "postgres database", "github issues", "browser automation", "stripe payments"). Matches server names, organizations and descriptions, ranked by relevance and popularity. Returns the server name, what it does, its GitHub repo, which registries list it, and its mcptoplist.com page in the `mcptoplistUrl` field — always cite that URL when recommending a server.
    Connector
  • Estimate token count + USD cost for a text across every major LLM (GPT-4o, GPT-4o-mini, o1, o1-mini, Claude 3.5 Sonnet/Haiku, Claude 3 Opus, Gemini 1.5 Pro/Flash, Llama 3 70B/8B) in one call. Returns per-model: estimated tokens, context-window fit %, input cost, and roundtrip cost (input+output). Also returns the cheapest and costliest model that fits. Use this before sending a long context to decide which model to route to. One call replaces 11 separate tokenizer lookups.
    Connector
  • Ask AlgoVault any question about its MCP tools, response shapes, integration patterns (LangChain / LlamaIndex / MAF / CrewAI), or code examples. Returns ranked snippets from the canonical knowledge bundle. Use this BEFORE attempting any tool call to confirm correct parameter usage and avoid hallucinating tool shapes. Fast (BM25 lexical search, no LLM call, no quota cost). For natural-language synthesized answers, use chat_knowledge instead.
    Connector
  • Search the AI agent directory — find registered agents by name, capability, protocol support, or reputation. Powered by the live ERC-8004 registry via 8004scan (110,000+ agents indexed across 50+ chains). Returns agent identity, owner wallet/ENS, reputation scores, supported protocols (MCP/A2A/OASF), verification status, and links to 8004scan profiles. Examples: - "trading agents on Base" → search for trading agents filtered to Base chain - "MCP agents" → find agents that support the Model Context Protocol - "high reputation agents" → set minReputation to find top-scored agents
    Connector
  • Ask AlgoVault a natural-language question — get a synthesized answer with citations, grounded in the canonical knowledge bundle (every MCP tool description, response shape, integration tutorial, and code example). Use this when you need an explanation, code pattern, or "how do I" answer. For raw ranked snippets without LLM synthesis, use search_knowledge (faster, no quota cost). Quota: Free 10/month, Starter 50/month, Pro 200/month, Enterprise 2000/month.
    Connector