API 키가 필요 없이 Google 검색 결과를 사용하여 무료 웹 검색을 구현하는 MCP(Model Context Protocol) 서버입니다.
Google 검색 결과를 사용하여 웹 검색
API 키나 인증이 필요하지 않습니다
제목, URL 및 설명이 포함된 구조화된 결과를 반환합니다.
검색당 구성 가능한 결과 수
Related MCP server: search-mcp
이 저장소를 복제하거나 다운로드하세요
종속성 설치:
지엑스피1
서버를 빌드하세요:
npm run buildMCP 구성에 서버를 추가합니다.
VSCode(Claude Dev Extension)의 경우:
{
"mcpServers": {
"web-search": {
"command": "node",
"args": ["/path/to/web-search/build/index.js"]
}
}
}Claude Desktop의 경우:
{
"mcpServers": {
"web-search": {
"command": "node",
"args": ["/path/to/web-search/build/index.js"]
}
}
}서버는 다음 매개변수를 허용하는 search 이라는 단일 도구를 제공합니다.
{
"query": string, // The search query
"limit": number // Optional: Number of results to return (default: 5, max: 10)
}사용 예:
use_mcp_tool({
server_name: "web-search",
tool_name: "search",
arguments: {
query: "your search query",
limit: 3 // optional
}
})응답 예시:
[
{
"title": "Example Search Result",
"url": "https://example.com",
"description": "Description of the search result..."
}
]이 도구는 Google 검색 결과의 웹 스크래핑을 사용하므로 알아야 할 몇 가지 중요한 제한 사항이 있습니다.
속도 제한 : Google은 짧은 시간 내에 너무 많은 검색이 수행될 경우 요청을 일시적으로 차단할 수 있습니다. 이를 방지하려면 다음을 수행하세요.
검색 빈도를 적정 수준으로 유지하세요
제한 매개변수를 신중하게 사용하세요
필요한 경우 검색 사이에 지연을 구현하는 것을 고려하세요.
결과 정확도 :
이 도구는 Google의 HTML 구조에 의존하며 이는 변경될 수 있습니다.
일부 결과에는 설명이나 기타 메타데이터가 누락되었을 수 있습니다.
복잡한 검색 연산자는 예상대로 작동하지 않을 수 있습니다.
법적 고려 사항 :
이 도구는 개인용으로 사용됩니다.
Google 서비스 약관을 준수하세요
사용 사례에 적합한 속도 제한을 구현하는 것을 고려하세요.
문제점과 개선 요청을 자유롭게 제출하세요!
Search the web using Google (no API key required)
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes | Search query | |
| limit | No | Maximum number of results to return (default: 5) |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions 'no API key required,' which adds some context about authentication, but fails to describe other critical behaviors such as rate limits, response format, error handling, or any constraints beyond the input schema. This leaves significant gaps for an agent to understand how the tool behaves.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is extremely concise and front-loaded, consisting of a single sentence that directly states the tool's function and a key feature ('no API key required'). There is no wasted language, making it efficient and easy to parse for an agent.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's complexity as a web search function with no annotations and no output schema, the description is incomplete. It lacks details on behavioral traits, response format, and operational constraints, which are crucial for an agent to use the tool effectively. The high schema coverage helps with inputs, but overall context is insufficient.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema has 100% description coverage, clearly documenting both parameters ('query' and 'limit') with details like default values and constraints. The description does not add any additional meaning beyond what the schema provides, so it meets the baseline score of 3 for high schema coverage without compensating with extra insights.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool's purpose with specific verb ('search') and resource ('the web using Google'), making it immediately understandable. However, since there are no sibling tools mentioned, it cannot demonstrate differentiation from alternatives, which prevents a perfect score.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides minimal guidance by mentioning 'no API key required,' which implies ease of use but lacks explicit instructions on when to use this tool versus alternatives or any context about limitations. No sibling tools exist, so no comparison is possible, but the description still lacks usage context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
searchWith only one tool, there is no possibility of ambiguity or overlap between tools. The tool's purpose is singular and clear, so an agent cannot misselect between multiple options.
A single tool inherently has perfect naming consistency, as there are no other tools to compare it against for patterns. The name 'search' is straightforward and appropriate for its function.
One tool is too few for a server named 'Web Search MCP Server', which suggests a broader scope like searching, filtering, or managing search results. A single search tool feels thin and limits functionality, making it borderline inappropriate for the implied domain.
The tool surface is severely incomplete for web search functionality. It only provides a basic search tool, missing obvious operations like filtering results, getting details, saving searches, or handling pagination, which are common in search domains and could lead to agent failures in complex tasks.
Unclaimed servers have limited discoverability.
If you are the server author, to access and configure the admin panel.
Search Google straight from your AI agent. Web results, images, videos, news, products, scholarly ar
GoogleSearch API: Fetch real-time Google Search results including title, links Ideal for serp api.
Provides AI assistants with access to Seltz's powerful Web Search capabilities.
Scrape Google search results with SERP data, ads, and knowledge panels
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/williamvd4/web-search'
If you have feedback or need assistance with the MCP directory API, please join our Discord server
