A
licenseB
qualityD
maintenanceA Model Context Protocol server that provides web search capabilities using Google Custom Search API and webpage content extraction functionality.
2
MIT
Search1API MCP Server
Related Servers
Alternatives to Search1API MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseAqualityCmaintenanceA Model Context Protocol server that provides web search capabilities using Google Custom Search API and webpage content extraction functionality.26 npm2-
- AlicenseBqualityDmaintenanceA Model Context Protocol server providing web search capabilities using Google Custom Search API and webpage content extraction functionality.2MIT
- AlicenseNot gradedqualityCmaintenanceA Model Context Protocol server that exposes powerful web search and scraping tools to AI agents and MCP-compatible clients.Apache 2.0
- AlicenseBqualityCmaintenanceA Model Context Protocol server that enables AI assistants to perform real-time web searches, retrieving up-to-date information from the internet via a Crawler API.151 npm42ISC
- AlicenseAqualityCmaintenanceA Model Context Protocol (MCP) server implementation that integrates with Firecrawl for advanced web scraping capabilities.26129,393 npm7,610MIT
TDQS
A3.8/5.0
Scored across 7 tools
Disambiguation4/5
Most tools have distinct roles: crawl extracts text, sitemap discovers links, render_results presents output, and trending surfaces popular content. However, search, news, and ask all overlap as retrieval operations, distinguished mainly by the descriptions (engine-specific vs. news-focused vs. multi-engine fallback) rather than by clearly separate purposes.
Naming Consistency3/5
Names mix conventions: verbs (crawl, search, ask), nouns (news, sitemap), a gerund (trending), and one verb_noun (render_results). The tools remain readable and mostly single-word, but there is no predictable pattern across the set.
Tool Count4/5
Seven tools is well within a reasonable range for a search/crawl service and each maps to a recognizable capability. It is slightly generous given the retrieval overlap, but nothing feels redundant or filler.
Completeness4/5
The surface covers the search lifecycle well: multi-source retrieval (search, news, ask, trending), full-text extraction (crawl), link discovery (sitemap), and result presentation (render_results). Minor gaps exist around explicit pagination or structured filtering, but core workflows are covered.
Maintenance
ActivityActive
ResponsivenessWithin a week