Skip to main content
Glama
635,181 tools. Updated 2026-10-03 23:34

"Using Yandex Browser to Search for Information" matching MCP tools:

  • Submit changed/new/deleted URLs to IndexNow so search engines (Bing, Yandex, Seznam, Naver, ...) recrawl them promptly. All URLs must share one host, max 1000 per call. Requires the host's IndexNow key file to be live: call provision_indexnow_key first and make sure the user hosted the key file at its key_location (indexnow_key_not_verified means the file is missing or wrong). Costs 1 credit, refunded automatically when the submission fails.
    ConnectorNo auth
  • Use this before selecting a web-search, URL-fetch, browser-automation, cloud-browser, headless-browser, Playwright/CDP, or authenticated-browser provider. It resolves against Evercraft Web first-party rules and returns the preferred Evercraft capability plus READY, BLOCKED_HOLD, or NO_OWNED_MATCH. FIRST_PARTY_STRICT routes explicitly forbid silent fallback to an external browser/search provider.
    ConnectorNo auth
  • Search a mailbox using Outlook's search syntax and return message metadata — not bodies. Searches the whole mailbox unless folderId is given. Use this to find messages, then get_outlook_message to read one, or move_messages to file them. Examples: 'from:acme.com', 'invoice overdue', 'hasattachments:yes'.
    ConnectorOAuth
  • Brave Local Search API returns enriched information (address, phone, hours, rating) for location-search results. Access requires the Brave Search API Pro plan; currently US-only. Two-step flow: first call `brave_web_search` with `result_filter=locations` to obtain `locations.results[].id`, then pass them here. NOTE: This tool takes location IDs from a prior web-search response; if you have a free-text query, call `brave_web_search` first.
    ConnectorOAuth
  • [tourradar] Search tour reviews using AI-powered semantic search. Requires tourIds to scope results to specific tours. Use this when the user asks about reviews, feedback, or experiences for specific tours. Combine with an optional text query to find reviews mentioning specific topics (e.g., 'food', 'guide', 'accommodation'). When you don't have tour IDs, use vertex-tour-search or vertex-tour-title-search first to find them.
    ConnectorNo auth
  • Searches submissions using a searchable field value. Use this tool to locate existing submissions matching the search criteria. Only fields configured as searchable in the Data Template (Form) can be used as search criteria — call wdf_data_templates_get_schema_and_sample_submissions first to see which fields are searchable for this Data Template (Form).
    ConnectorNo auth

Matching MCP Servers

  • F
    license
    Not graded
    quality
    F
    maintenance
    Enables AI assistants to perform real-time web searches and retrieve AI-generated answers using the Yandex Search API. It provides tools for accessing up-to-date internet information with support for both raw search results and summarized content via the Yazeka model.
    48
    -
  • F
    license
    B
    quality
    D
    maintenance
    Enables comprehensive control and automation of Yandex Browser, including tab management, content extraction, and console log monitoring. It supports element interaction, form filling, and JavaScript execution through the Model Context Protocol.
    18
    9
    -

Matching MCP Connectors

  • Yandex search results, images, and SERP data via the Apify Yandex Search Scraper, hosted MCP.

  • Read-only Yandex Metrika MCP. Query visits, sources, geo, devices and more in plain language.

  • Sets up a CONTACT FORM → EMAIL relay for the user's hosted (static) site using the user's OWN Gmail or Yandex — with NO third-party dashboard: the user configures everything here, in chat. A static page can't speak SMTP itself, so its form POSTs to our thin relay and we forward the message through the user's own Gmail/Yandex (Gmail/Yandex does the actual sending). The site OWNER sets BOTH the sender (from_email) and recipient (to_email); the visitor filling the form cannot change them (so it can't be abused as an open relay). provider: 'yandex' (smtp.yandex.com:465) | 'gmail' (smtp.gmail.com:465 — requires a Google APP PASSWORD, not the normal password) | 'other' (give smtp_host + smtp_port). from_email must be the SMTP account (or a verified alias) or Gmail/Yandex rejects the send. By default sends a TEST email to to_email to verify the credentials and reports the result. Returns the form endpoint URL + a ready-to-paste HTML <form> snippet (with honeypot). Re-running reconfigures the same server's form. The SMTP password is stored encrypted; only the site owner's fixed to_email ever receives mail. READ-ONLY STATUS: call with only `server` (no smtp_user / smtp_pass / to_email) to see whether that site's form is already set up, its endpoint URL and the field contract, without entering any password. A new site has no endpoint yet — it is created on the first real setup, so build the form with the action in one place and fill it in after setup. Field contract of the endpoint: POST as a normal HTML form (form-urlencoded or multipart; JSON is not read). Every field whose name does not start with "_" is forwarded in the e-mail; `email` becomes Reply-To, `subject` sets the subject line. `_gotcha` is the hidden honeypot (filled = silently dropped). `_redirect` = an absolute https URL to send the visitor to after sending, with ?sent=1 or ?sent=0 appended; without it a small thank-you page is shown (HTTP 200, 502 if the mail account refused). No CORS headers are sent, so use a plain form submit (or fetch with mode:"no-cors", where the reply cannot be read). Limit: 20 submissions per hour per form (HTTP 429); a GET on the endpoint answers 404/405 by design.
    Connector
    Destructive
    OAuth
  • Search the web for any topic and get clean, ready-to-use content. Best for: Finding current information, news, facts, people, companies, or answering questions about any topic. Returns: Clean text content from top search results. Query tips: describe the ideal page, not keywords. "blog post comparing React and Vue performance" not "React vs Vue". Use category:people / category:company to search through Linkedin profiles / companies respectively. If highlights are insufficient, follow up with web_fetch_exa on the best URLs.
    ConnectorNo auth
  • Connect Yandex Metrika to a site. IMPORTANT: authorisation happens IN A BROWSER, and neither you nor the platform can do that step for the user. The tool returns a link — show it and ask them to open it and grant access. Do not poll in a loop: the person may walk away for an hour. Check later through this same tool without the `branch` argument, or through `site_analytics`.
    ConnectorOAuth
  • Searches the site "CodeStringers Zoho Consulting Services" (https://www.codestringers.com/_api/mcp) for information. Use this tool ONLY in the following cases: 1. You just used "GetBusinessDetails" tool and you did not find the information you need. 2. User asked a generic business question about their business (e.g., business address, business hours, contact information, return policy, etc.) 3. You already tried to find an entity (e.g., product, service, etc.) using an API tool and you did not find the information you need. 4. The request is too vague and you do not know what type of entity it is and what to search for in the docs. Do NOT use this tool for searching for products or other offered services - use the 'SearchSiteApiDocs' tool instead (unless you already tried that tool and you did not find the information you need). This tool DOES NOT support filters - you cannot ask questions like "find me something under $10".
    ConnectorNo auth
  • General search tool. This is your FIRST entry point to look up for possible tokens, entities, and addresses related to a query. Do NOT use this tool for prediction markets. For Polymarket names, topics, event slugs, or URLs, use `prediction_market_lookup` instead. Nansen MCP does not support NFTs, however check using this tool if the query relates to a token. Regular tokens and NFTs can have the same name. This tool allows you to: - Check if a (fungible) token exists by name, symbol, or contract address - Search information about a token - Current price in USD - Trading volume - Contract address and chain information - Market cap and supply data when available - Search information about an entity - Find the address behind a Nansen label (public figure, fund, exchange wallet) - Find Nansen labels of an address (EOA) or resolve a domain (.eth, .sol)
    ConnectorNo auth
  • General search tool. This is your FIRST entry point to look up for possible tokens, entities, and addresses related to a query. Do NOT use this tool for prediction markets. For Polymarket names, topics, event slugs, or URLs, use `prediction_market_lookup` instead. Nansen MCP does not support NFTs, however check using this tool if the query relates to a token. Regular tokens and NFTs can have the same name. This tool allows you to: - Check if a (fungible) token exists by name, symbol, or contract address - Search information about a token - Current price in USD - Trading volume - Contract address and chain information - Market cap and supply data when available - Search information about an entity - Find the address behind a Nansen label (public figure, fund, exchange wallet) - Find Nansen labels of an address (EOA) or resolve a domain (.eth, .sol)
    ConnectorNo auth
  • Search users by person name, partial username, or fuzzy match using real-time external API. PRIMARY USE: When given person's name (e.g., "Cristiano Ronaldo", "Kim Kardashian"), partial info, or uncertain username. Use for: Name-based search, finding multiple candidates, fuzzy matching, discovering users. NOT for: Exact username lookup (use getInstagramUser when username is certain). Optional fields parameter for performance (default: ["id", "username", "fullName"]). Available fields: id, username, fullName, biography, isPrivate, isVerified, followerCount, followingCount, mediaCount, profilePicUrl, and more. Returns: array of matching users (default 10, max 10) with userId, username, fullName, followerCount, biography, profilePicUrl. This is a safe, read-only tool for analyzing searchable information.
    ConnectorOAuth
  • Connect Yandex Metrika to a site. IMPORTANT: authorisation happens IN A BROWSER, and neither you nor the platform can do that step for the user. The tool returns a link — show it and ask them to open it and grant access. Do not poll in a loop: the person may walk away for an hour. Check later through this same tool without the `branch` argument, or through `site_analytics`.
    ConnectorAPI key
  • Execute live web searches using multi-engine chain (TinyFish, DuckDuckGo, Jina) without monthly API subscriptions. Returns fresh source URLs, titles, and snippets. Requires x402 micropayment (0.005 USDC on Base). When to use: Real-time web browsing and information retrieval for AI agents. When NOT to use: Do NOT use for deep recursive crawling of entire sites. Parameters: - `query` (string, required): Search query (3-300 chars). - `limit` (integer, optional, default 5): Maximum number of search results to return (1-10).
    ConnectorNo auth
  • Execute live web searches using multi-engine chain (TinyFish, DuckDuckGo, Jina) without monthly API subscriptions. Returns fresh source URLs, titles, and snippets. Requires x402 micropayment (0.005 USDC on Base). When to use: Real-time web browsing and information retrieval for AI agents. When NOT to use: Do NOT use for deep recursive crawling of entire sites. Parameters: - `query` (string, required): Search query (3-300 chars). - `limit` (integer, optional, default 5): Maximum number of search results to return (1-10).
    ConnectorNo auth
  • Search for works in the Digital Collections using field-based and/or natural language queries. If both a natural language query and specific field values are provided, the natural language query will take priority, using the specified field values as additional constraints. The result will also include a list of aggregations that show how many results match different values for certain fields. For example, you could see how many results match each collection, work type, or visibility and use that information to refine your search. Perform an empty search to retrieve all works and their aggregations. NOTE: Structured field values enclosed in double quotes will be treated as exact, case-sensitive matches, while unquoted values will be treated as full-text searches.
    ConnectorNo auth
  • Return accommodation-level context, apartment list, images, detail information and weekly availability for one public accommodation. Use this after search results to inspect all apartments belonging to one accommodation and to explain location, descriptions and detail notes. For price and bookability comparison for a specific week, prefer search_apartments with weekId.
    ConnectorNo auth
  • Search academic papers from IACR ePrint Archive. Args: query: Search query string (e.g., 'cryptography', 'secret sharing'). max_results: Maximum number of papers to return (default: 10). fetch_details: Whether to fetch detailed information for each paper (default: True). Returns: List of paper metadata in dictionary format.
    ConnectorNo auth
  • Search everything the caller has said to an agent and been told, wherever they said it — the browser, email, or the command line. Use it when something was mentioned and you need to find where; notes_get is for a fact somebody wrote down on purpose
    ConnectorNo auth
  • List websites configured for stored Google, Bing, and Yandex keyword tracking, including provider freshness and sync state. This reads RankParse snapshots; it does not run a live SERP check.
    ConnectorNo auth