"The term pHqghUme" matching MCP servers:

MCP server that persists web fetch and search results as timestamped JSONL, enabling long-term archival and cross-domain search via unified-history-mcp.

Enables AI assistants to access real-time web data through search, markdown scraping, and browser automation while bypassing anti-bot protections. It provides tools for web research, e-commerce monitoring, and data extraction from across the globe.

An MCP server that turns your Sell The Trend account into an AI-drivable product-research engine and generates detailed, decision-ready PDF dossiers for any niche.

An MCP server that helps AI assistants access text content from websites that implement bot detection, bridging the gap between what you can see in your browser and what the AI can access.

Lets an AI share the same live browser tab as a person, receiving the user's Alt+click target and enabling the AI to inspect, click, fill, type, navigate, or otherwise operate on that real page. It runs locally and pairs with the browser extension to bridge the user's page to the MCP client.

A Model Context Protocol server that enables Claude Desktop to browse the web, likely allowing the AI to access and interact with web content.

Enables search capabilities using a Google Custom Search Engine, allowing users to input a search term and retrieve search result titles, links, and snippets, while facilitating integration with other tools for content extraction and advanced search strategies.

Serves as a machine perception and action hub, enabling heartbeat monitoring, screen/window/clipboard sensing, todo management, long-term memory, and web/file operations through both CLI and MCP interfaces.

An enhanced browser automation MCP server that solves token limit issues through intelligent semantic compression, enabling universal web automation with context-aware snapshot modes.

Enables web search capabilities through the Tavily API, allowing users to search the web for information using natural language queries through the Model Context Protocol.

A server based on the MCP protocol that uses the Brave API for web search functionality.

Facilitates browser automation with custom capabilities and agent-based interactions, integrated through the browser-use library.

Control the MetaDock desktop workspace over MCP: browsers, layouts, bookmarks, downloads, and more.

Enables web search functionality via the 302AI API.

Enables LLMs to read and extract clean, markdown-formatted content from any webpage using the Jina AI Reader API.

Enables LLMs to perform real-time Google searches and retrieve web results via the MCP protocol.

Enables web searches across multiple engines (DuckDuckGo, Bing, Google, SerpAPI, Google CSE, Tavily) with no API key required for the free engines, plus automatic fallback, caching, and webpage content fetching.

Controls the TradingView Desktop app via MCP, allowing AI agents to manage charts, indicators, Pine Script strategies, and optionally mirrors signals to MetaTrader 5 for automated trading.

Enables fetching HTTP resources through the MCP protocol.

Enables AI agents to perform web searches using the Brave Search engine, providing an independent alternative to Google/Bing.