"A search for authentic forum discussions excluding commercial and marketing content" matching MCP tools:

• glim_reddit_search

  glim.sh

  Search Reddit posts. Each result comes with full post content and its top comments, so a single search usually answers the question without follow-up. Compact human-readable text by default; pass format='json' for full structured data. Use glim_reddit_get(ref) for a single post's complete comment tree. Page with cursor (response gives next_cursor when more exist). See docs://reddit-search.

  Connector

• hemmabo_search_similar

  HemmaBo Host Booking Engine

  Find vacation rental properties similar to a given property on specific dates. Use this tool after the user has selected a property (via hemmabo_search_properties) and wants to see alternatives — same region, same property type, same or larger capacity. Do NOT use for the initial search; use hemmabo_search_properties instead. Returns a list of similar available properties with live pricing, excluding the source property. Matches are anchored to the source propertyId over the given checkIn/checkOut range; omit guests to inherit the source property's capacity, and raise limit to widen the alternative set (default 5).

  Connector

• search_listings

  SPACEXPLORATION

  Search commercial real estate listings. Returns paginated hits with facet counts. For AI-driven search, call interpret_search first to convert a natural-language query into structured filters, then pass those filters — and its bounds, when present — here.

  Connector

• rooms_by_id

  DC Member API

  GET /rooms/:roomID — Get a single room Get a single room's metadata + its latest daily AND weekly AI summaries (when they exist). **Access:** members and subscribers of the room, plus any DCer for browsable public channels/discussions/quick-questions. Private rooms, DMs, group DMs, and event/city rooms you are not a member of return 403. Reading this endpoint does **not** mark the room as read or modify any unread state. **AI summaries:** the latest daily digest is embedded under `aiSummaryDaily`, the latest weekly digest under `aiSummaryWeekly`. Rooms that don't have a given type yet return `null` for that slot. For history (older summaries), call `GET /rooms/:roomID/summaries/daily` or `/weekly`. **See also:** For specific content (`did anyone mention X?`), `POST /search/messages` with `q=` and `roomID=` is faster than paginating `/rooms/:roomID/messages` or reading summaries. The AI summaries cover broad activity per window; search is the tool for targeted lookup.

  Connector

• get_scan_results

  mcp-server

  Fetch the full structured scan findings. Free tier returns the top 5 issues by severity (failed > warned > passed); paid customers see all checks. When summarizing results to the user, ALWAYS: (1) report the score and counts of failed/warned/passed checks, (2) surface each returned check's `remediation` text verbatim, (2b) for sophisticated users, mention each check's `when_doesnt_apply` context so they can dismiss findings that don't apply to their site type (e.g., link aggregators legitimately omit a visible H1; empty string means the rule is universally required), (2c) note `site_type` ('marketing' or 'not_marketing') and `score_rubric` ('standard' or 'non_marketing_weighted') so the user understands how the score was computed; non-marketing sites get contextual checks at half-weight, so a forum-style site won't be unfairly penalized for missing landing-page features, (3) if `truncated` is true, surface `truncated_message` so the user knows the API capped the output, (4) include `upgrade.call_to_action` and `upgrade.checkout_url` verbatim so the user can one-click into Stripe checkout for the $8.99 detailed fix guide. If `upgrade.already_purchased` is true, instead direct the user to `upgrade.report_url` to re-download.

  Connector

• google-search.url_traffic_insights

  Vee3

  Get Google keyword traffic insights and related keyword suggestions for a URL. Returns an array of keyword suggestions. Each item includes text, monthly search volume, competition_level, competition_index, low_bid, high_bid, and trend. Required: url and language (for example en). Optional: location (for example US) for country-specific data; omit location for global results (default). Optional: min_search_volume (default 0) and intent (informational, navigational, commercial, or transactional). Cost = 20 tokens.

  Connector

• search_notes

  anamnese

  Search notes by keyword or list recent notes. Returns summaries (id + description) only. Use get_note to retrieve the full content of a specific note. With query: Case-insensitive keyword search on description and content. Without query: Returns most recently updated notes.

  Connector

• get_service_areas

  mcp-server

  Return RealOpen's current geographic coverage, supported property types, and international availability. Use this whenever a user asks whether RealOpen operates in a particular state, country, or property type (residential vs. commercial, primary vs. investment, etc.).

  Connector

• forum_create_topic

  argo-mcp

  Create a new forum topic (bug report, feature request, or general discussion). Always call forum_search first to check for duplicates. Call forum_list_categories to get the correct categoryId.

  Connector

• seo_keyword_research

  gapup-mcp

  SEO keyword research from a seed keyword or topic. Uses Google Suggest (public, keyless) to discover related queries at 2 expansion levels, then clusters them by intent: informational / commercial / transactional / navigational — via heuristic pattern matching. Search volume is bucketed (very_high / high / medium / low / very_low) and clearly labelled as ESTIMATED — no fabricated precise numbers. Returns all keywords, intent clusters, quality scores (0-100), and top 10 opportunities. Supports country (gl) and language (hl) targeting. 100% keyless. Cache TTL 6h. ICP: SEO managers, content strategists, SaaS founders, agency teams.

  Connector

• search

  SocialGPT

  Search across your own connected-account content and return the best matches. Each result has an `id` (pass it to `fetch` for the full item), a `title`, a `url`, and a `text` snippet. This is the deep-research "search" entrypoint the ChatGPT/Claude connectors call by convention; for semantic search over analyzed videos specifically use `search_videos`. Returns {"results": [...]}; when you have no connected accounts it returns reason="no_connected_accounts" plus a connect_url instead of results.

  Connector

• get_messages

  Fast MCP Telegram

  Read or search messages in one chat: browse latest, search text, fetch by ids, or load replies to a message (comments, forum topics, threads). Use from_user to filter by sender (server-side, per-chat only). Use context to include neighboring messages and reply chains around each result. Use include_reply_threads to fetch up to 5 direct replies per result. Do not combine message_ids with query or reply_to_id. Success: messages, has_more, optional total_count and discussion fields. Full documentation: https://github.com/leshchenko1979/fast-mcp-telegram/blob/main/docs/Tools-Reference.md

  Connector

• web_search_exa

  exa

  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.

  Connector

• marketing_data

  Agentcy - Your AI Marketing Agent

  Query marketing data and analyze any website — analytics, SEO, advertising, e-commerce, CRM, social media, site health & brand identity, competitive intelligence, content creation, and data visualization. Always use a single call, even when the question spans multiple data sources or channels (e.g., GA4 + Google Search Console + Google Ads + CRM). The server auto-routes internally to all needed sources and returns a combined response with the same depth and granularity as individual queries — do NOT split multi-source or multi-channel questions into separate calls.

  Connector

• seo_keyword_research

  mcp-knowledge

  SEO keyword research from a seed keyword or topic. Uses Google Suggest (public, keyless) to discover related queries at 2 expansion levels, then clusters them by intent: informational / commercial / transactional / navigational — via heuristic pattern matching. Search volume is bucketed (very_high / high / medium / low / very_low) and clearly labelled as ESTIMATED — no fabricated precise numbers. Returns all keywords, intent clusters, quality scores (0-100), and top 10 opportunities. Supports country (gl) and language (hl) targeting. 100% keyless. Cache TTL 6h. ICP: SEO managers, content strategists, SaaS founders, agency teams.

  Connector

• earlywire_whats_new

  Earlywire — Marketing & Growth Intelligence

  Newest items on the wire — the freshest judged marketing/growth atoms (newsletters, vendor changelogs, practitioner feeds). Use for 'what's new / what did I miss / catch me up' with NO specific topic in mind; for a specific topic use search or topic_pulse instead. Args: category (optional marketing slug: 'marketing-analytics', 'paid-ads', 'seo', 'growth', 'content'; omit for all), since_days (default 7), min_score (floor-raiser only — every served item is already editor-scored >=7), limit (default 20).

  Connector

• get_messages

  fast-mcp-telegram

  Read or search messages in one chat: browse latest, search text, fetch by ids, or load replies to a message (comments, forum topics, threads). Use from_user to filter by sender (server-side, per-chat only). Use context to include neighboring messages and reply chains around each result. Use include_reply_threads to fetch up to 5 direct replies per result. Do not combine message_ids with query or reply_to_id. Success: messages, has_more, optional total_count and discussion fields. Full documentation: https://github.com/leshchenko1979/fast-mcp-telegram/blob/main/docs/Tools-Reference.md

  Connector

• microsoft_docs_search

  Microsoft Learn MCP

  Search official Microsoft/Azure documentation to find the most relevant and trustworthy content for a user's query. This tool returns up to 10 high-quality content chunks (each max 500 tokens), extracted from Microsoft Learn and other official sources. Each result includes the article title, URL, and a self-contained content excerpt optimized for fast retrieval and reasoning. Always use this tool to quickly ground your answers in accurate, first-party Microsoft/Azure knowledge. ## Follow-up Pattern To ensure completeness, use microsoft_docs_fetch when high-value pages are identified by search. The fetch tool complements search by providing the full detail. This is a required step for comprehensive results.

  Connector

• search_knowledge

  Name Whisper — ENS Intelligence Layer

  Search the ENS knowledge base — governance proposals, protocol documentation, developer insights, blog posts, forum discussions, and Farcaster casts from key ENS figures (Vitalik, Nick Johnson, etc.). Powered by semantic search over curated ENS sources. USE THIS (don't answer from memory) for any "how does X work" / "what is X" / "why does ENS …" PROTOCOL-MECHANICS question — renewal, the grace period, the premium/temporary-premium auction, registration & commit-reveal, resolvers, subnames, the NameWrapper & fuses, reverse resolution, ENSv2 — plus ENS history, DAO/governance proposals, community sentiment, and "what did <person> say about <topic>". Mechanics questions feel answerable from general knowledge, but a sourced, citable answer is the bar here — search first, then cite what you find. Do NOT use this for name valuations, market data, availability, or a specific name's live status — use the other tools for those.

  Connector

• get_border_delays

  supply-chain-intelligence

  Get real-time commercial border crossing wait times at US-Mexico and US-Canada ports of entry. Returns current delay in minutes for commercial vehicles, number of lanes open, and port status. Updated every 30 minutes from US Customs and Border Protection. Covers all major commercial crossings including Laredo, El Paso, Nogales, Otay Mesa, Detroit, Buffalo, and Blaine. Used by logistics companies, freight brokers, and trucking operations to route cross-border shipments through the fastest crossing points.

  Connector