justserpapi-mcp
OfficialRelated Servers
Alternatives to justserpapi-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceIntegrates with SerpAPI and YouTube to provide comprehensive search capabilities across Google Search, News, Scholar, Trends, Finance, Maps, Images, YouTube, and transcript retrieval for AI assistants.2MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to perform real-time web searches, extract data from web pages, map website structures, and crawl websites using the Tavily API.72 npmMIT
- AlicenseNot gradedqualityCmaintenanceWraps SerpApi to enable AI agents to perform web searches via various search engines.5 npmMIT

georanker-seo-mcpofficial
FlicenseAqualityBmaintenanceEnables AI assistants to search Google SERPs, track rankings across locations, run Lighthouse SEO audits, find broken internal links, analyze backlinks, and get keyword volume data through a hosted service.13-- FlicenseNot gradedqualityNot gradedmaintenanceEnables searching across multiple search engines (Google, Bing, YouTube, DuckDuckGo, etc.) and retrieving parsed search results via SerpApi integration.-
- AlicenseCqualityNot gradedmaintenanceEnables AI assistants to interact with DataForSEO APIs and obtain SEO data including SERP results, keyword research, on-page metrics, backlink analysis, and domain analytics through a standardized interface.767,607 npm-
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose: list_services lists available services, search_endpoints finds endpoint candidates, get_endpoint_schema retrieves parameter details for a specific endpoint, call_endpoint executes the API call, and refresh_catalog updates the endpoint catalog. There is no ambiguity or overlap between tools.
All tool names follow a consistent verb_noun pattern using snake_case: list_services, search_endpoints, get_endpoint_schema, call_endpoint, refresh_catalog. The naming style is uniform and predictable.
With 5 tools, the server is lightweight but well-scoped for its purpose of interacting with JustSerpAPI endpoints. It covers the essential workflow of discovering services, searching for endpoints, getting schemas, making calls, and refreshing data. The count feels appropriate, though slightly on the smaller side.
The tool set covers the core lifecycle: discovery (list_services, search_endpoints), parameter retrieval (get_endpoint_schema), execution (call_endpoint), and maintenance (refresh_catalog). There are minor gaps such as missing error handling or status checking tools, but the surface is complete enough for typical usage.