CubicJ MCP Search
OfficialRelated Servers
Alternatives to CubicJ MCP Search
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceFacilitates integration of Brave Search functionalities with AI assistants through the Model Context Protocol, enabling web and local searches using the Brave Search API.215MIT
- AlicenseNot gradedqualityDmaintenanceExposes a standardized web search tool via Brave Search for MCP clients like Codex, Claude, and Cursor, returning stable JSON.MIT
- FlicenseNot gradedqualityDmaintenanceEnables web and local business searches through the Brave Search API. Provides general web search with pagination and filtering, plus local business search with automatic fallback to web results.-
- AlicenseNot gradedqualityBmaintenanceEnables LLM hosts to run DuckDuckGo searches, scrape JavaScript-rendered and cookie-consent-gated pages with a hardened headless browser, and launch non-blocking same-domain BFS crawls whose progress and extracted content can be polled.Apache 2.0
- AlicenseAqualityDmaintenanceProvides web access capabilities for LLMs including search, fetching, content extraction, PDF reading, image viewing, and screenshots.346MIT
- AlicenseNot gradedqualityDmaintenanceIntegrates the Brave Search API into AI assistants to enable web and local business search capabilities. This allows models to perform real-time information retrieval and locate places using the Model Context Protocol.1MIT
TDQS
Scored across 2 tools
web_search handles discovery with ranked excerpts, while fetch retrieves and extracts full content from a single URL. Their roles are clearly distinct and the descriptions reinforce when to use each.
fetch is a bare verb and web_search is a compound noun/verb form, so there is no shared verb_noun pattern. Both are readable and common, but the conventions are mixed.
Two tools cover the core search-and-retrieve workflow without redundancy, but the count is slightly below the typical 3–15 range. Each tool earns its place for the server's narrow purpose.
The surface covers discovery via web_search and retrieval via fetch, including pagination and many site-specific extractors. Minor gaps like batch fetching or search pagination exist, but there are no major dead ends.