Fetch Serp

Created By
fetchSERPa year ago
All-in-One SEO & Web Intelligence Toolkit API - Monitor keywords, track domain rankings, analyze SERPs, and extract insights — all in one powerful API for competitive research, keyword intelligence, and content strategy.
Overview

What is Fetch Serp?

Fetch Serp is an all-in-one SEO and web intelligence toolkit API designed to monitor keywords, track domain rankings, analyze SERPs, and extract insights for competitive research, keyword intelligence, and content strategy.

How to use Fetch Serp?

To use Fetch Serp, sign up at fetchserp.com to obtain your API token. You can run the MCP server directly from GitHub using npx or deploy it remotely for enterprise use.

Key features of Fetch Serp?

  • Comprehensive domain analysis including backlinks and domain info.
  • Keyword research tools for search volume and long-tail keyword generation.
  • SERP analysis from multiple search engines.
  • Web scraping capabilities with JavaScript execution.
  • User management for API credits and account info.

Use cases of Fetch Serp?

  1. Conducting competitive analysis for SEO strategies.
  2. Tracking keyword rankings over time.
  3. Extracting insights from SERPs for content optimization.
  4. Scraping web data for market research.

FAQ from Fetch Serp?

  • How do I get started with Fetch Serp?

Sign up at fetchserp.com to get your API token and start using the toolkit.

  • Is there a free trial available?

Yes, new users receive 250 free credits to explore the features.

  • Can I scrape JavaScript-heavy websites?

Yes, Fetch Serp supports scraping with JavaScript execution.

Server Config

{
  "mcpServers": {
    "fetchserp": {
      "command": "npx",
      "args": [
        "github:fetchSERP/fetchserp-mcp-server-node"
      ],
      "env": {
        "FETCHSERP_API_TOKEN": "your_fetchserp_api_token_here"
      }
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
fetchSERP
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

4 hours ago
Gpt Scrambler

a day ago