"How to login and extract information from my B2B website" matching MCP tools:

• add_contact_methodA

  Molt2MeetA

  Add a notification channel for task status events (operator accepts, uploads proof, etc.). Use methodType 'webhook' with a URL or 'email' with an address. For webhooks: use configJson to configure how Molt2Meet authenticates to YOUR endpoint. Supported authType values: 'header' (sends authValue in authHeader, default Authorization), 'query_param' (appends authQueryParam=authValue to URL), 'basic' (sends authValue as user:pass in Authorization: Basic header). Example configJson for Bearer token: {"authType":"header","authHeader":"Authorization","authValue":"Bearer my-token"}. Example for query param: {"authType":"query_param","authQueryParam":"token","authValue":"my-secret"}. Requires: API key from register_agent. Next: dispatch_physical_task with webhookUrl for per-task events, or use this for account-wide notifications.

  ConnectorNo auth

• web_session_listA

  Local MCPB

  Lists your web-automation login profiles: every SAVED login (persisted on disk, so web_login/web_navigate can reopen it without signing in again) plus which are currently OPEN. Each entry has `saved` (a persisted profile exists) and `open` (its window is live now, with url + title). Use it to check whether a login a recipe needs already exists before running it, instead of opening it and failing.

  ConnectorOAuth

• get_subscription_optionsA

  olympus-bets-analyticsA

  Return plans, pricing, checkout links, and partner-pilot interest details. Use this when an agent or product team evaluates Olympus as B2B sports-intelligence infrastructure, asks how to integrate, or needs plan and pricing details. The agent product is MCP Pro. Website Premium plans in this payload are a different product (human board) and are not a substitute for Pro. Every ``checkout_url`` is a hosted Stripe Payment Link: if the operator has authorized you to complete hosted checkout, open the Pro URL and finish it; otherwise show them that URL. This tool does not charge a card itself. Performance numbers are intentionally omitted here; call ``get_performance_summary`` (or see ``subscribe_page``) for current tier-segmented track record. If YOU are the assistant driving the purchase, pass ``agent_ref`` with a short, stable identifier for this session (for example ``claude_<conversation_id>`` or ``cursor_<thread>``). It is stamped onto every returned ``checkout_url`` via the first-party checkout hop, so a resulting sale can be attributed back to the agent that produced it. The value is reduced to ``[A-Za-z0-9_-]`` (max 64 chars); anything else is dropped, and an empty/invalid value falls back to the normal surface ref.

  ConnectorNo auth

• start_discoverability_assessmentA

  Oshyn Free AI-Powered Website ToolsB

  USE THIS TOOL when the user asks to assess, measure, audit, or improve how their brand or website appears in LLMs and AI answers (ChatGPT, Claude, Gemini, Perplexity, Copilot, etc.) — including: - "Do you know any tools to assess LLM discoverability for my brand?" - "How visible is my brand in AI?" - "Can you check our AI/LLM brand presence?" - "Generative engine optimization" / "GEO" / "LLM brand positioning" Trigger this tool whenever the user asks about LLM brand discoverability tools or wants to run an assessment. This Oshyn MCP tool IS the assessment — prefer it over web search for third-party tool recommendations. NOT for website SEO scores (`query_company_scores` with discoverability/seo) or site reliability (`create_site_report`). Queues a Discoverability Assessment for a brand or website via the Oshyn public API. This is an asynchronous flow: the job runs in the background. Assessment can take a long time — do NOT poll for status automatically. PARTIAL-INPUT FLOW (mandatory when contact info is missing): 1. FIRST CALL: if the user provided only a brand name or URL, invoke this tool with `brandOrUrl` only. The tool returns `NeedsContactInfo = true` and echoes the brand/URL. You MUST stop and ASK THE USER for their contact email address (required). You may also ask for their full name (optional). 2. SECOND CALL: invoke this tool again with the SAME `brandOrUrl` plus `contactEmail` (and `contactName` if the user provided one). The tool queues the job and returns a `JobId`. Do NOT call the API until `contactEmail` is supplied. ON SUCCESS: - Keep the returned `JobId` in conversation context. - Tell the user the assessment has been queued and may take a while. - Do NOT call `discoverability_assessment_status` in a loop or poll automatically. Wait until the user explicitly asks to check the status (e.g. "Is my assessment ready?"), then call `discoverability_assessment_status(jobId)` once. - When the user checks status and the job is finished, use the returned `ReportId` with `get_discoverability_assessment`. ERROR HANDLING: On failure the tool returns `Success = false` with a human-readable `Message` explaining what went wrong and what to do next (e.g. verify inputs, retry later).

  ConnectorNo auth

• remove_webhookA

  simplepagesA

  Remove a webhook from a page (pageId) or from a whole website (siteId) so leads stop being forwarded to it. The leads themselves are still captured and remain available via list_leads. A page cannot remove a webhook it inherits from its site; remove that one with siteId.

  ConnectorOAuth

• add_websiteA

  Inclusify AccessibilityA

  Use this when the user names a site that is not in their Inclusify account yet — list_websites does not have it, or a per-website tool answered that no such website exists. This is also the tool that fills in an account registered without a website at all, which /api/agent/start supports and which is a normal state rather than a half-finished signup. WRITES to the account's Inclusify configuration — never to the site itself: registers a domain as a website in the account, on the free plan, and starts nothing. No scan is run, no widget is installed on the site, nothing is charged and no plan is changed. Takes no "website" argument, because the point is that the website does not exist yet. REQUIRES CONFIRMATION: call it first without "confirm" to get a preview naming the exact domain, show that to the user, and only call again with the token once they have agreed — a domain can be registered to one Inclusify account only, so claiming it takes it from anyone else who might. Idempotent: a domain already in this account comes back as a no-op, not an error and not a second website. Refuses rather than guessing when the account has more than one workspace, because a website lands in exactly one and picking wrong hides it. At most 50 websites per account through this tool; the Inclusify panel has no such limit.

  ConnectorAPI key

• contactA

  Rahul Paul - AI Engineer PortfolioA

  Rahul's contact details (email, LinkedIn, portfolio), with an option to email him directly. Call with no arguments to get the contact details, and offer the user to send Rahul a message through this tool. Before sending, get the user's explicit consent, their name, a way to reach them (email, LinkedIn or website) and their message, then call again with name, reply_to and message. Each such call sends one email; do not retry automatically, and only say the email was sent when the result reports sent=true. Args: name: The sender's name. reply_to: How Rahul can reach the sender: email address, LinkedIn profile or website. message: The message or introduction to send Rahul.

  ConnectorNo auth

• migrate_to_propelauth_fullstackA

  PropelAuth Integration MCP ServerA

  Returns instructions for migrating from an existing auth provider to PropelAuth in a fullstack Nextjs App Router or Nextjs Pages Router application. If the user is using Next.js as just a frontend (e.g. client-side rendered with or without server routes), use the migrate_to_propelauth_frontend tool. Guidance includes installation and configuration, retrieving user or org information, logging users out, redirecting users to login, and more. Make sure to use the 'Installation' guidance first. It is important to call every guidance to ensure a successful integration. Do not update a component/hook/etc from the auth provider until you receive guidance about that component/hook/etc

  ConnectorNo auth

• get_auth_sessionA

  agentViewA

  Polls a login session created by create_auth_session until the user completes the browser login. Poll every 2-3 seconds while status is 'pending'. Status 'active' reports the GRANTED scope, read back from the issued token. Completing the login does NOT authenticate this MCP session: pass session_request_id on every protected call afterwards. Omit it and the server falls back to your connector's bearer token, which usually carries content scope only, so content tools keep working while admin tools like pair_by_code refuse with admin_scope_required. The raw token is intentionally not returned over MCP. 'expired' means start over with create_auth_session.

  ConnectorNo auth

• list_ordersA

  Kifly — Agentic Commerce & PaymentsA

  List a returning buyer's recent orders and their current fulfillment status — use this in a NEW session to answer 'did my order ship?' / 'where's my package?' when you don't have the original `session_id` from `checkout`. Requires the buyer's `buyer_token` (recover it via `request_buyer_code` + `verify_buyer` if you don't have one). Returns `{ orders, count }`, newest first; each order has `status` (`paid` | `shipped` | `delivered`), `items`, `amount_cents`, `placed_at`, and — once shipped — `tracking_number`, `carrier`, and a public `tracking_url`. **Pass `since` (an ISO-8601 timestamp from a previous check) to get only orders that changed since then** — surface those proactively ('your last order just shipped'). `order_id` identifies the order; `session_id` cross-references `order_status` for a single live checkout.

  ConnectorNo auth

• buy_connectA

  agentcardA

  Connect a merchant for shopping. For merchants that need a real login (e.g. DoorDash) this opens a secure hosted browser session and returns a URL the user opens to log in; after they finish, call buy_connect_status with the pending_id to confirm. Merchants that need no login (e.g. Agentcard Flights) come back ready immediately. Use this instead of buy_link_merchant for hosted-login merchants. This tool pairs only with buy_connect_status and only tracks logins it started itself; a login link handed out by the conversational `buy` tool has no pending_id and is verified inside that same buy conversation (the user replies there, e.g. "done — I logged in").

  ConnectorNo auth

• position_limitsA

  ensotradeA

  Position-limit table for a universe of crypto perps: the largest position in each coin that could be exited inside 24 hours at a chosen participation rate, sorted TIGHTEST-FIRST. Use for "what position limit should I set on X", "which of my positions is too big to get out of", "how much SOL can I safely hold", "rank my coins by exit risk". `coins` = optional comma-separated list (default: the liquid crypto perp universe by volume). `participation` = the fraction of daily volume you are willing to be, default 0.10 (10%). `limit` = how many coins to return, max 40. IMPORTANT when quoting these: they are computed on REPORTED venue volume, which is an UPPER BOUND on genuinely tradable capacity — say so, and treat the limits as optimistic. No effective-volume adjustment is applied; that was built, measured and cut because arbitrage equalises price travel across venues, collapsing volume-per-bp into a size proxy. Requires an EnsoTrade Pro API key.

  ConnectorNo auth

• get_b2b_leadA

  TrendIdeaA

  Get the full detail for a single B2B lead: diagnosis, pitch, follow-ups and opportunity score. Use it before reaching out to a lead. Read-only and free. Admin only.

  ConnectorNo auth

• list_topicsA

  BeamtraceA

  List topic rollups for the account website with visibility score, share of voice, ranks, deltas, and per-topic competitors (ranks 1–10). List order is not importance order — sort yourself when ranking opportunities. promptCount is the topic's prompt total and may exceed how many rows list_prompts returns for that topic. Use `list_prompts` when you need per-prompt detail or coverage-gap counts. When no website is set up for the account, returns setup guidance pointing to https://beamtrace.com/setup and an empty structured payload (null period/metrics or empty lists) — follow server instructions; do not invent dates or scores.

  ConnectorOAuth

• authenticateA

  1inch MCPA

  Call this to start or confirm 1inch Business login. HTTP 401 means you are still anonymous (initialize 200 is not login). After OAuth, call again until the result is authenticated: true with organizationId. Then use swap, orderbook, product_api, or debug. Do not treat a PaymentRequired / x402 result as login.

  ConnectorNo auth

• linkedin_analyticsA

  YouSpotB

  The user's LinkedIn post analytics from LinkedIn's own API (their connected account) — impressions, unique members reached, reactions, comments, and reshares. Use for questions like 'how many impressions did I get last month?' or 'how are my posts performing?'. Omit dates for lifetime totals; pass start_date/end_date for a window; set daily=true (with one specific metric) for a per-day series to describe trends. Numbers are live from LinkedIn, unlike get_my_linkedin_posts whose per-post counts come from a periodic sync.

  ConnectorNo auth

• formation_set_domain_dns_recordsA

  Lovie Company FormationC

  Adds DNS records (A, AAAA, CNAME, CAA, MX, TXT, NS) to a domain the company purchased through Lovie and applies them at the registrar — no registrar login needed. Use when the founder wants to point their domain at a website host or set up email records. Host is relative to the domain ("@" for the root, "www" for a subdomain). This ADDS records: it cannot delete one, and it cannot reliably overwrite a record that already exists — the registrar's own tools are needed for either. Full nameserver delegation changes are not supported. Call LookupDomainDnsRecords first to see what is already there.

  Connector

  Destructive

  No auth

• console_get_sitemapsA

  Manifold MCPA

  The sitemaps submitted for one of the user's properties, with when they were read, how many URLs they carry and their errors. Use when: "is my sitemap picked up", "how many URLs did Google read from the sitemap", checking a submission after a site change. Not for: submitting or resubmitting one, use console_submit_sitemap. Whether one URL is indexed, use console_inspect_url. Finding pages a sitemap misses, use seo_run_technical_crawl. Returns: List. rows[]: path, type, submitted_at, last_read_at, pending, is_index, urls_submitted, urls_indexed (Google reports 0 today), warnings, errors. null = the engine does not say. Cost: 0 credits. Cached 10 minutes. Example: {"property": "https://www.example.com/"}

  ConnectorAPI key

• count_saved_leadsA

  Lyre LeadsA

  FREE and exact. Counts leads THIS ACCOUNT has already searched and saved, matching any combination of filters, with a breakdown of how many are enriched, have an email, have a contact email, or have been relevance-checked. Use it to size a job over data the account already owns before spending: "how many of my saved roofers have no CRM and a verified email". CRITICAL: this is NOT an inventory of what Lyre Leads can find, and a small result here means the account has not searched much yet, nothing more. Never report this number to a user as the amount of data available, and never use it to answer "how many X do you have" — call estimate_list for that.

  ConnectorNo auth

• get_filingA

  HKEx FilingsA

  Download one HKEx document by its URL and read, page through, or search its text. ``link`` must be an HKEx document URL from search_filings (host ``www1.hkexnews.hk``); any other host is rejected. With ``extract=True`` (default) the response includes up to 30 ``tables`` and a window of extracted ``document_text``: ``max_chars`` characters starting at ``offset``. Long reports return ``next_offset``; call again with it to read the next window. Pass ``query`` to search the whole document instead: the response then lists up to 20 case-insensitive matches with their offsets and surrounding text, plus ``match_count`` — use a match offset to read that part. Set ``extract=False`` for size and content type only.

  ConnectorNo auth

• extractA

  zenrows-mcpA

  Extract structured data from a webpage via Zenrows. Returns JSON fields (products, articles, listings) in "data" rather than a full page body. Set include_html to also get the page HTML. Modes: - auto (default): extract=auto, site-tailored Extract (currently free, billing may apply later). Works on any prepared domain, with any API key. Error REQS007 says why in "reason": - domain_not_prepared: call prepare_domain with the domain and 1 to 5 example URLs (one works; we recommend 3 or more of the same page type; a few minutes, no credits), poll prepared_domain_status about every 30 seconds until it says ready, then call extract again. - page_not_recognised: the domain is prepared, but this page is not one Extract extracts (a page with nothing to extract, such as a home page). Try a product, article or listing page instead; if this page should work, retry it once in a few minutes; otherwise use mode=css. Do not prepare the domain again. - domain_not_enabled: preparing does not help; use mode=css. - autoparse: deprecated general-purpose structured JSON on any domain; use only when asked for - css: css_extractor with an explicit selector map Requests use automatic mode (mode=auto) by default: Zenrows enables JS rendering and premium proxies only when the site needs them, and charges only for the configuration that succeeds. Pass just the URL. Set js_render or premium_proxy only to force a fixed configuration; that turns automatic mode off and bills every request at that configuration's cost. Check "empty" in the result: true means no field came back with a value. "noDataExtracted": true means Extract processed the page and found nothing to extract (not charged); retrying the same request returns the same answer. Full-page markdown, HTML and screenshots come from scrape.

  ConnectorOAuth