Serper Search and Scrape MCP Server

Created By
MCP-Mirrora year ago
Mirror of
Overview

what is Serper Search and Scrape MCP Server?

Serper Search and Scrape MCP Server is a TypeScript-based server that provides web search and webpage scraping capabilities using the Serper API, integrated with Claude Desktop for enhanced content extraction.

how to use Serper Search and Scrape MCP Server?

To use the server, install it via Smithery or Docker, set up your environment variables, and configure it in your application settings. You can perform web searches and scrape content from web pages using the provided tools.

key features of Serper Search and Scrape MCP Server?

  • Perform web searches with rich results using the Serper API.
  • Extract content from web pages, including plain text and metadata.
  • Supports advanced search operators for refined search results.
  • Easy installation and configuration via Smithery or Docker.

use cases of Serper Search and Scrape MCP Server?

  1. Conducting research by scraping data from multiple web pages.
  2. Automating web searches for specific information.
  3. Integrating web search capabilities into applications for enhanced user experience.

FAQ from Serper Search and Scrape MCP Server?

  • What is required to run the server?

You need Node.js >= 18 and a Serper API key.

  • Can I run the server using Docker?

Yes, you can build and run the server using Docker with your Serper API key.

  • How do I configure the server for Claude Desktop?

You need to add the server configuration in the Claude Desktop config file.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
MCP-Mirror
Star
0
Language
TypeScript
License
MIT license

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

14 minutes ago