litescrape-mcp-server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LITESCRAPE_API_KEY | No | Bearer key for the Litescrape API; unset means the free keyless allowance. | |
| LITESCRAPE_API_URL | No | API origin, for self-hosted or staging deployments. | https://api.litescrape.com |
| LITESCRAPE_TIMEOUT_MS | No | Per-request timeout in milliseconds. | 120000 |
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| searchA | Search the web through Google and return ranked organic results (title, link, snippet) as JSON. Fast mode: no Knowledge Graph, ads or AI modules; use google_search for the full results page. Free without an API key (shares the google_search allowance). |
| google_searchA | Fetch a first-party Google Search results page as JSON: organic_results plus whichever modules Google served (knowledge_graph, answer_box, ai_overview, ads, related_questions, related_searches, local_results, top_stories, inline_videos and more). Supports localization, verticals (news, videos, local, shopping, patents), date filters and site restriction. Free without an API key: 25 calls per network per day. |
| bing_searchA | Fetch a Bing web search results page as JSON: organic_results plus the modules Bing served (answer_box, knowledge_graph, copilot_answer, ads, related_questions, inline_videos, top_stories and more). Free without an API key: 50 calls per network per day. |
| duckduckgo_searchA | Fetch ranked DuckDuckGo web results (organic_results with title, link, snippet) with region, safety and date controls. Free without an API key: 50 calls per network per day. |
| google_mapsA | Search Google Maps for places (local_results with name, address, rating, reviews, hours, phone, website, coordinates) or fetch one exact place (place_results) by place_id, data_cid or data sequence. Filter by price, rating and opening hours. Free without an API key: 50 calls per network per day. |
| google_ai_overviewA | Return only the AI Overview Google generates for a search (ai_overview with ordered text_blocks and cited references), or null when Google shows none. Accepts the google_search parameters. Requires an API key. |
| google_ai_modeA | Ask Google AI Mode a question and return its generated answer (ordered text_blocks: paragraphs, headings, lists, tables, code) with the sources it cited (references). Set continuable to get a token for follow-up questions; image_url adds a picture to the prompt. Slow: answers are generated per request. Requires an API key. |
| google_shoppingA | Search Google Shopping and return the product grid (shopping_results with title, price, source, rating, thumbnail), category blocks, sponsored listings and the refinement chips Google renders (filters). Price bounds, sale, shipping and small business refinements are mutually exclusive; sort_by combines with one of them. Requires an API key. |
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 8 tools
Most tools are distinguishable by engine or domain, but 'search' and 'google_search' both return Google organic results (differing only by modules), and 'google_ai_overview' vs 'google_ai_mode' both produce AI-generated text with references, creating potential misselection. Bing and DuckDuckGo are clearly distinct, but the AI and Google search siblings blur boundaries.
The pattern is partially consistent with google_search, bing_search, and duckduckgo_search following an engine_search convention. However, the bare 'search' tool breaks the pattern, and google_maps, google_shopping, google_ai_overview, and google_ai_mode use a mixed domain/feature style rather than a uniform verb_noun structure.
Eight tools is a well-scoped set for a web research and scraping server, covering multiple search engines, maps, shopping, and AI-assisted search. Each tool adds a meaningful capability without bloat or redundancy.
The server covers core research needs: multiple engines, maps, shopping, and AI summaries. Minor gaps exist (e.g., no general URL fetcher, no dedicated news tool), but google_search's verticals and filters mitigate these, and no obvious dead-end workflow is present.