FetchSERP▌
by fetchserp
FetchSERP delivers advanced keyword research and SEO analysis by integrating with Google Keyword Planner and top search
Integrates with FetchSERP API to provide SEO analysis, SERP data retrieval, web scraping, keyword research, backlink analysis, and domain intelligence across Google, Bing, Yahoo, and DuckDuckGo search engines.
Both formats append explainx.ai attribution and the canonical URL for this MCP server listing.
best for
- / SEO professionals tracking keyword rankings
- / Digital marketers analyzing competitor strategies
- / Content creators researching search trends
- / Agencies providing SEO reporting to clients
capabilities
- / Retrieve search engine results from multiple providers
- / Analyze keyword rankings and search performance
- / Extract backlink data for domains
- / Scrape web pages for SEO analysis
- / Research competitor keywords and rankings
- / Monitor SERP positions over time
what it does
Retrieves search engine results and performs SEO analysis across Google, Bing, Yahoo, and DuckDuckGo. Provides SERP data, keyword research, and backlink analysis through the FetchSERP API.
about
FetchSERP is an official MCP server published by fetchserp that provides AI assistants with tools and capabilities via the Model Context Protocol. FetchSERP delivers advanced keyword research and SEO analysis by integrating with Google Keyword Planner and top search It is categorized under search web.
how to install
You can install FetchSERP in your AI client of choice. Use the install panel on this page to get one-click setup for Cursor, Claude Desktop, VS Code, and other MCP-compatible clients. This server runs locally on your machine via the stdio transport.
license
MIT
FetchSERP is released under the MIT license. This is a permissive open-source license, meaning you can freely use, modify, and distribute the software.
readme
FetchSERP MCP Server
A Model Context Protocol (MCP) server that exposes the FetchSERP API for SEO, SERP analysis, web scraping, and keyword research.
Features
This MCP server provides access to all FetchSERP API endpoints:
SEO & Analysis
- Domain Analysis: Get backlinks, domain info (DNS, WHOIS, SSL, tech stack)
- Keyword Research: Search volume, suggestions, long-tail keyword generation
- SEO Analysis: Comprehensive webpage SEO analysis
- AI Analysis: AI-powered webpage analysis with custom prompts
- Moz Integration: Domain authority and Moz metrics
SERP & Search
- Search Results: Get SERP results from Google, Bing, Yahoo, DuckDuckGo
- AI Overview: Google's AI overview with JavaScript rendering
- Enhanced Results: SERP with HTML or text content
- Ranking Check: Domain ranking for specific keywords
- Indexation Check: Verify if pages are indexed
Web Scraping
- Basic Scraping: Scrape webpages without JavaScript
- JS Scraping: Execute custom JavaScript on pages
- Proxy Scraping: Scrape with country-specific proxies
- Domain Scraping: Scrape multiple pages from a domain
User Management
- Account Info: Check API credits and user information
Installation
No installation required! This MCP server runs directly from GitHub using npx.
Get your FetchSERP API token: Sign up at https://www.fetchserp.com to get your API token. New users get 250 free credits to get started!
Usage
Transport Modes
This MCP server supports two transport modes:
npx mode (Option 1):
- ✅ Zero installation required
- ✅ Always gets latest version from GitHub
- ✅ Perfect for individual users
- ✅ Runs locally with Claude Desktop
HTTP mode (Option 2):
- ✅ Remote deployment capability
- ✅ Multiple clients can connect
- ✅ Better for enterprise/team environments
- ✅ Centralized server management
- ✅ Single API key authentication (FetchSERP token)
- ✅ Scalable architecture
Configuration
Option 1: Using npx (Local/Remote GitHub) Add this server to your MCP client configuration. For example, in Claude Desktop using github registry :
{
"mcpServers": {
"fetchserp": {
"command": "npx",
"args": [
"github:FetchSERP-LLC/fetchserp-mcp-server-node"
],
"env": {
"FETCHSERP_API_TOKEN": "your_fetchserp_api_token_here"
}
}
}
}
or using npm registry
{
"mcpServers": {
"fetchserp": {
"command": "npx",
"args": ["fetchserp-mcp-server"],
"env": {
"FETCHSERP_API_TOKEN": "your_fetchserp_api_token_here"
}
}
}
}
Option 2: Claude API with MCP Server For programmatic usage with Claude's API and your deployed MCP server:
const claudeRequest = {
model: "claude-sonnet-4-20250514",
max_tokens: 1024,
messages: [
{
role: "user",
content: question
}
],
// MCP Server Configuration
mcp_servers: [
{
type: "url",
url: "https://www.fetchserp.com/sse",
name: "fetchserp",
authorization_token: FETCHSERP_API_TOKEN,
tool_configuration: {
enabled: true
}
}
]
};
const response = await httpRequest('https://api.anthropic.com/v1/messages', {
method: 'POST',
headers: {
'x-api-key': CLAUDE_API_KEY,
'anthropic-version': '2023-06-01',
'anthropic-beta': 'mcp-client-2025-04-04',
'content-type': 'application/json'
}
}, JSON.stringify(claudeRequest));
Option 3: OpenAI API with MCP Server For programmatic usage with OpenAI's API and your deployed MCP server:
const openai = new OpenAI({ apiKey: process.env.OPENAI_API_KEY });
const res = await openai.responses.create({
model: "gpt-4.1",
tools: [
{
type: "mcp",
server_label: "fetchserp",
server_url: "https://www.fetchserp.com/sse",
headers: {
Authorization: `Bearer ${FETCHSERP_API_TOKEN}`
}
}
],
input: question
});
console.log(res.choices[0].message);
Available Tools
Domain & SEO Analysis
get_backlinks
Get backlinks for a domain
- domain (required): Target domain
- search_engine: google, bing, yahoo, duckduckgo (default: google)
- country: Country code (default: us)
- pages_number: Pages to search 1-30 (default: 15)
get_domain_info
Get comprehensive domain information
- domain (required): Target domain
get_domain_emails
Extract emails from a domain
- domain (required): Target domain
- search_engine: Search engine (default: google)
- country: Country code (default: us)
- pages_number: Pages to search 1-30 (default: 1)
get_playwright_mcp
Use GPT-4.1 to remote control a browser via a Playwright MCP server
- prompt (required): The prompt to use for remote control of the browser
This endpoint uses GPT-4.1 to remote control a browser via a Playwright MCP server.
get_webpage_seo_analysis
Comprehensive SEO analysis of a webpage
- url (required): URL to analyze
get_webpage_ai_analysis
AI-powered webpage analysis
- url (required): URL to analyze
- prompt (required): Analysis prompt
generate_wordpress_content
Generate WordPress content using AI with customizable prompts and models
- user_prompt (required): The user prompt
- system_prompt (required): The system prompt
- ai_model: The AI model (default: gpt-4.1-nano)
Generates SEO-optimized WordPress content including title and content (800-1500 words) with keyword targeting in the first 100 words.
generate_social_content
Generate social media content using AI with customizable prompts and models
- user_prompt (required): The user prompt
- system_prompt (required): The system prompt
- ai_model: The AI model (default: gpt-4.1-nano)
Generates engaging social media content optimized for various platforms and audiences.
get_moz_analysis
Get Moz domain authority and metrics
- domain (required): Target domain
Keyword Research
get_keywords_search_volume
Get search volume for keywords
- keywords (required): Array of keywords
- country: Country code
get_keywords_suggestions
Get keyword suggestions
- url: URL to analyze (optional if keywords provided)
- keywords: Array of seed keywords (optional if url provided)
- country: Country code
get_long_tail_keywords
Generate long-tail keywords
- keyword (required): Seed keyword
- search_intent: informational, commercial, transactional, navigational (default: informational)
- count: Number to generate 1-500 (default: 10)
SERP & Search
get_serp_results
Get search engine results
- query (required): Search query
- search_engine: google, bing, yahoo, duckduckgo (default: google)
- country: Country code (default: us)
- pages_number: Pages to search 1-30 (default: 1)
get_serp_html
Get SERP results with HTML content
- Same parameters as
get_serp_results
get_serp_text
Get SERP results with text content
- Same parameters as
get_serp_results
get_serp_ai_mode
Get SERP with AI Overview and AI Mode response
- query (required): Search query
- country: Country code (default: us)
Returns AI overview and AI mode response for the query. Less reliable than the 2-step process but returns results in under 30 seconds.
check_page_indexation
Check if domain is indexed for keyword
- domain (required): Target domain
- keyword (required): Search keyword
get_domain_ranking
Get domain ranking for keyword
- keyword (required): Search keyword
- domain (required): Target domain
- search_engine: Search engine (default: google)
- country: Country code (default: us)
- pages_number: Pages to search 1-30 (default: 10)
Web Scraping
scrape_webpage
Scrape webpage without JavaScript
- url (required): URL to scrape
scrape_domain
Scrape multiple pages from domain
- domain (required): Target domain
- max_pages: Maximum pages to scrape, up to 200 (default: 10)
scrape_webpage_js
Scrape webpage with custom JavaScript
- url (required): URL to scrape
- js_script (required): JavaScript code to execute
scrape_webpage_js_proxy
Scrape webpage with JavaScript and proxy
- url (required): URL to scrape
- country (required): Proxy country
- js_script (required): JavaScript code to execute
User Management
get_user_info
Get user information and API credits
- No parameters required
API Token
You need a FetchSERP API token to use this server.
Getting your API token:
- Sign up at https://www.fetchserp.com
- New users automatically receive 250 free credits to get started
- Your API token will be available in your dashboard
Set the token as an environment variable:
export FETCHSERP_API_TOKEN="your_token_here"
Error Handling
The server includes comprehensive error handling:
- Missing API token validation
- API response error handling
- Input validation
- Proper MCP error responses
Docker deploy
docker build --platform=linux/amd64 -t us-east4-docker.pkg.dev/fetchserp-474019/fetchserp/mcp-server-node:latest --push .
npm login npm publish --access public
FAQ
- What is the FetchSERP MCP server?
- FetchSERP is a Model Context Protocol (MCP) server profile on explainx.ai. MCP lets AI hosts (e.g. Claude Desktop, Cursor) call tools and resources through a standard interface; this page summarizes categories, install hints, and community ratings.
- How do MCP servers relate to agent skills?
- Skills are reusable instruction packages (often SKILL.md); MCP servers expose live capabilities. Teams frequently combine both—skills for workflows, MCP for APIs and data. See explainx.ai/skills and explainx.ai/mcp-servers for parallel directories.
- How are reviews shown for FetchSERP?
- This profile displays 31 aggregated ratings (sample rows for discoverability plus signed-in user reviews). Average score is about 4.7 out of 5—verify behavior in your own environment before production use.
Use Cases▌
Web Research & Information Gathering
Fetch and extract information from websites automatically
Example
Research competitor pricing, scrape product reviews, monitor news mentions
Automate 5-10 hours/week of manual web research
Content Monitoring & Alerts
Track website changes, new content, price updates
Example
Monitor competitor blog for new posts, track stock availability, watch for pricing changes
Stay informed without manual checking, never miss important updates
Data Extraction & Aggregation
Extract structured data from multiple websites
Example
Compile product listings from 10 e-commerce sites, aggregate job postings, collect real estate data
Build datasets 100x faster than manual copying
API-less Integration
Interact with services that don't offer APIs
Example
Check form submissions, validate website functionality, test user flows
Automate interactions with any website, even without API
Implementation Guide▌
Prerequisites
- ›Claude Desktop or Cursor with MCP support
- ›Understanding of web scraping ethics and robots.txt
- ›Rate limiting awareness to avoid overwhelming target sites
- ›Knowledge of legal restrictions on data collection
Time Estimate
20-40 minutes including configuration and testing
Installation Steps
- 1.Install web automation MCP server via npm or pip
- 2.Configure allowed domains and rate limits in MCP config
- 3.Test with simple fetch: 'Get content from example.com'
- 4.Progress to extraction: 'Extract all product prices from this page'
- 5.Set up monitoring: 'Check this URL daily for changes'
- 6.Parse structured data: 'Create CSV from this table'
- 7.Respect robots.txt and rate limits always
Troubleshooting
- ⚠403 Forbidden: Website blocks bots—respect their wishes, use official API instead
- ⚠Rate limit errors: Slow down requests, add delays between fetches
- ⚠Stale data: Target site changed HTML structure—update selectors
- ⚠Timeout errors: Site is slow or blocking—increase timeout, try different user agent
- ⚠JavaScript-rendered content: Use headless browser MCP servers for dynamic sites
Best Practices▌
✓ Do
- +Check robots.txt and respect crawl rules
- +Rate limit requests: 1-2 requests/second maximum
- +Use official APIs when available instead of scraping
- +Identify your bot with descriptive user agent
- +Cache results to minimize repeated requests
- +Handle errors gracefully with retries and fallbacks
- +Validate extracted data for accuracy
✗ Don't
- −Don't scrape sites that explicitly forbid it (robots.txt, ToS)
- −Don't overwhelm servers with rapid requests—use rate limiting
- −Don't scrape personal data without consent and legal basis
- −Don't ignore copyright on extracted content
- −Don't assume HTML structure is stable—handle changes
- −Don't use scraped data for commercial purposes without permission
💡 Pro Tips
- ★Use CSS selectors or XPath for robust data extraction
- ★Set up monitoring alerts for extraction failures (structure changed)
- ★Implement exponential backoff for retries on failures
- ★Store raw HTML for reprocessing if extraction logic changes
- ★Combine with data analysis tools for insights from extracted data
- ★Consider using official APIs or RSS feeds as more stable alternatives
Technical Details▌
Architecture
MCP server handles HTTP requests, HTML parsing, JavaScript rendering (if headless browser), and returns structured data to Claude.
Protocols
- HTTP/HTTPS
- WebSocket (for real-time sites)
- Puppeteer/Playwright (for JavaScript sites)
Compatibility
- Static HTML sites
- JavaScript-rendered SPAs (with headless browser)
- REST APIs
- GraphQL endpoints
When to Use This▌
✓ Use When
Use for research automation, content monitoring, data aggregation from multiple sources, and when official APIs don't exist. Best for read-only information gathering.
✗ Avoid When
Avoid for sites with APIs (use API instead), sites that explicitly forbid scraping, when data is copyrighted, or for login-required content without proper authorization.
Integration▌
- →Scheduled monitoring with change detection
- →Multi-source data aggregation pipelines
- →Fallback to web scraping when API rate limits hit
- →Headless browser for JavaScript-heavy sites
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
List & Promote Your MCP Server
Share your MCP server with the developer community
Ratings
4.7★★★★★31 reviews- ★★★★★Maya Malhotra· Dec 28, 2024
FetchSERP is among the better-indexed MCP projects we tried; the explainx.ai summary tracks the official description.
- ★★★★★Dhruvi Jain· Dec 20, 2024
FetchSERP has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.
- ★★★★★Benjamin Okafor· Dec 20, 2024
According to our notes, FetchSERP benefits from clear Model Context Protocol framing — fewer ambiguous “AI plugin” claims.
- ★★★★★Evelyn Li· Dec 16, 2024
FetchSERP reduced integration guesswork — categories and install configs on the listing matched the upstream repo.
- ★★★★★Oshnikdeep· Nov 11, 2024
We evaluated FetchSERP against two servers with overlapping tools; this profile had the clearer scope statement.
- ★★★★★Michael Choi· Nov 11, 2024
Useful MCP listing: FetchSERP is the kind of server we cite when onboarding engineers to host + tool permissions.
- ★★★★★Ganesh Mohane· Oct 2, 2024
We wired FetchSERP into a staging workspace; the listing’s GitHub and npm pointers saved time versus hunting across READMEs.
- ★★★★★Evelyn Kapoor· Oct 2, 2024
Strong directory entry: FetchSERP surfaces stars and publisher context so we could sanity-check maintenance before adopting.
- ★★★★★Arya Martin· Sep 17, 2024
According to our notes, FetchSERP benefits from clear Model Context Protocol framing — fewer ambiguous “AI plugin” claims.
- ★★★★★Arya Sethi· Sep 9, 2024
We wired FetchSERP into a staging workspace; the listing’s GitHub and npm pointers saved time versus hunting across READMEs.
showing 1-10 of 31