Marketing
easyfetcher.com
An MCP server for querying Google Trends and Google Search Console data, inspecting URLs, and checking sitemap health.
ENDPOINT 1
https://mcp.easyfetcher.com/mcp
MCP server metadata
- Name
- easyfetcher
- Version
- 2.0.0
EasyFetcher provides marketing data from Google Search Console, Google Analytics 4, Google Trends, real-time SERP rank checking, PageSpeed/Core Web Vitals, and SE Ranking data (backlinks, AI overviews, traffic, keyword volumes). TOOL SELECTION RULES: - User asks to check keyword rankings / positions / where a site ranks → use rank_check_direct - User asks about backlinks / link profile / who links to a domain → use backlink_check - User asks about AI Overviews / AI citations / SGE presence → use ai_overview_check - User asks about website traffic / monthly visitors / audience → use traffic_data - User asks about keyword volume / search demand / CPC / difficulty → use keyword_volume - User asks about GSC traffic, impressions, clicks, CTR → use gsc_query - User asks if a URL is indexed / indexing status / why a page isn't in Google / URL inspection → use gsc_url_inspect (supports single url or urls array up to 10) - User asks about sitemap health / how many pages indexed / indexing coverage / crawl issues → use gsc_sitemaps - User asks about website analytics, sessions, pageviews → use ga4_query - User asks about search trends → use trends_query - User asks about page speed / Core Web Vitals / LCP / CLS / performance score / Lighthouse → use pagespeed_query IMPORTANT: Only call the tool that matches what the user asked. Do not call multiple tools unless explicitly asked. rank_check_direct, backlink_check, ai_overview_check, traffic_data, keyword_volume, trends_query, and pagespeed_query need no connection, call them directly with the URL or domain. For GSC/GA4: call list_connections first, then the query tool. CRITICAL: If a tool returns an error stating that the user has multiple connections, YOU MUST stop and explicitly ask the user which connection they want to use, listing the available options provided in the error message.
Known tools 12
gsc_queryQuery Google Search Console data for traffic, impressions, clicks, and CTR.
Inferred read-onlygsc_url_inspectInspect one or multiple URLs using the Google Search Console URL Inspection API.
Inferred read-onlyrank_check_directCheck Google search rankings for specific keywords on a domain RIGHT NOW.
Inferred read-onlypagespeed_queryCheck PageSpeed / Core Web Vitals for any URL using Google Lighthouse.
Inferred read-onlybacklink_checkCheck backlinks for a domain, total count, referring domains, domain authority, and top referring sites.
Inferred read-onlyai_overview_checkCheck how many times a domain is cited in Google AI Overviews, Google AI Mode, ChatGPT, Perplexity, and Gemini.
Inferred read-onlytraffic_dataGet estimated website traffic data for a domain, monthly visits, organic vs paid breakdown, top traffic countries, and top pages.
Inferred read-onlykeyword_volumeGet search volume, CPC, competition, and keyword difficulty for one or more keywords.
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.easyfetcher]
url = "https://mcp.easyfetcher.com/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"easyfetcher": {
"type": "http",
"url": "https://mcp.easyfetcher.com/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: easyfetcher
Remote MCP URL: https://mcp.easyfetcher.com/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"easyfetcher": {
"url": "https://mcp.easyfetcher.com/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"easyfetcher": {
"type": "http",
"url": "https://mcp.easyfetcher.com/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "easyfetcher",
"transport": "streamable-http",
"url": "https://mcp.easyfetcher.com/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.