FetchSERP MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_backlinksC | Get backlinks for a given domain |
| get_domain_emailsC | Retrieve emails from a given domain |
| get_domain_infoC | Get domain info including DNS records, WHOIS data, SSL certificates, and technology stack |
| get_keywords_search_volumeC | Get search volume for given keywords |
| get_keywords_suggestionsB | Get keyword suggestions based on a url or a list of keywords |
| get_long_tail_keywordsC | Generate long-tail keywords for a given keyword |
| get_moz_analysisC | Get Moz domain analysis data |
| check_page_indexationC | Check if a domain is indexed for a given keyword |
| get_domain_rankingC | Get domain ranking for a given keyword |
| scrape_webpageB | Scrape a web page without JS |
| scrape_domainD | Scrape a domain |
| scrape_webpage_jsC | Scrape a web page with custom JS |
| scrape_webpage_js_proxyC | Scrape a web page with JS and proxy |
| get_serp_resultsC | Get search engine results |
| get_serp_htmlC | Get search engine results with HTML content |
| get_serp_ai_modeA | Get SERP with AI Overview and AI Mode response. Returns AI overview and AI mode response for the query. Less reliable than the 2-step process but returns results in under 30 seconds. |
| get_serp_textC | Get search engine results with text content |
| get_user_infoB | Get user information including API credit |
| get_webpage_ai_analysisC | Analyze a web page with AI |
| generate_wordpress_contentC | Generate WordPress content using AI with customizable prompts and models |
| generate_social_contentC | Generate social media content using AI with customizable prompts and models |
| get_playwright_mcpC | Use GPT-4.1 to remote control a browser via a Playwright MCP server |
| get_webpage_seo_analysisC | Get SEO analysis for a given url |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 23 tools
The tool set has clear distinctions in many areas, such as separate SERP retrieval methods (get_serp_results, get_serp_html, get_serp_text) and different scraping options (scrape_webpage, scrape_webpage_js, scrape_webpage_js_proxy). However, there is significant overlap between tools like get_serp_ai_mode and the other SERP tools, and between generate_social_content and generate_wordpress_content, which could cause confusion in selection despite descriptive names.
Most tools follow a consistent verb_noun pattern with 'get_', 'check_', 'generate_', or 'scrape_' prefixes, making them predictable and readable. There are minor deviations, such as 'get_playwright_mcp' which includes an acronym and 'get_serp_ai_mode' that is more descriptive, but overall the naming is largely uniform and follows a clear convention.
With 23 tools, the count is on the higher side for an SEO/SERP-focused server, bordering on heavy. While many tools serve distinct purposes, the overlap in SERP and scraping functionalities suggests some redundancy. This number is reasonable given the broad scope but could be streamlined for better coherence.
The tool set covers a wide range of SEO and web analysis tasks, including keyword research, domain analysis, content generation, and scraping. There are minor gaps, such as no explicit tools for updating or deleting data, but the surface is largely complete for the domain, allowing agents to perform comprehensive workflows without major dead ends.