A
licenseA
qualityF
maintenanceA Model Context Protocol server that integrates with Microsoft Bing Search API, allowing AI assistants to perform web, news, and image searches.
3
79
MIT
MCP-Bocha
by intounknown
mcp-bocha
Un servidor de Protocolo de Contexto de Modelo (MCP) que proporciona capacidades de búsqueda web a agentes de IA que utilizan la API de Bocha.
Introducción
MCP-Bocha es una herramienta que expone las capacidades de la API de búsqueda web de Bocha AI mediante el Protocolo de Contexto de Modelo. Permite a los asistentes de IA buscar en la web mediante programación, lo que facilita tareas como la recuperación de información, la investigación y la recopilación de datos actualizados.
Related MCP server: SearXNG MCP Server
Herramientas
Nombre de la herramienta | Descripción | Parámetros |
| Busque información en la web |
|
Uso
{
"mcpServers": {
"mcp-bocha": {
"command": "npx",
"args": ["-y", "@humansean/mcp-bocha"],
"env": {
"BOCHA_API_KEY": "YOUR_API_KEY"
}
}
}
}Licencia
Licencia Apache-2.0
Available Tools
1 toolmcp-bocha_searchC
Search the web for information
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| count | No | ||
| exclude | No | ||
| freshness | No | ||
| include | No | ||
| query | Yes | ||
| summary | No |
TDQS
C2.1/5.0
Behavior1/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states the action ('Search the web for information') without revealing any behavioral traits such as rate limits, authentication needs, output format, pagination, or error handling. This is inadequate for a tool with 6 parameters and no output schema.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is extremely concise at 4 words, with no wasted language. It's front-loaded and to the point, making it easy to parse quickly. Every word earns its place by conveying the core action, though it sacrifices detail for brevity.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness1/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the complexity (6 parameters, 0% schema coverage, no annotations, no output schema), the description is incomplete. It doesn't explain what the tool returns, how results are structured, or any behavioral aspects. For a search tool with multiple filtering options, this minimal description leaves critical gaps in understanding how to effectively use it.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters1/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema description coverage is 0%, meaning none of the 6 parameters are documented in the schema. The description adds no meaning beyond the schema—it doesn't explain what parameters like 'count', 'freshness', or 'summary' do, nor does it clarify the purpose of arrays like 'include' and 'exclude'. With 0% coverage, the description fails to compensate for the lack of schema documentation.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose3/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description 'Search the web for information' clearly states the verb ('Search') and resource ('the web'), making the purpose understandable. However, it's vague about what kind of information is searched (e.g., general web pages, specific content types) and doesn't differentiate from siblings (though none exist). It's not tautological but lacks specificity beyond basic action.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines2/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides no guidance on when to use this tool versus alternatives, prerequisites, or constraints. It simply states what it does without context for application. Since there are no sibling tools, this is less critical, but it still lacks any usage context or exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
1 tool update
v1.0.0- First observed
mcp-bocha_search
TDQS
C2.5/5.0
Scored across 1 tool
Disambiguation5/5
With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool 'mcp-bocha_search' has a clear and distinct purpose of searching the web for information, leaving no room for confusion or misselection.
Naming Consistency5/5
The naming is perfectly consistent as there is only one tool. It follows a clear verb_noun pattern ('search' as the verb and implied 'web' as the noun), and with no other tools to compare against, there is no inconsistency in naming conventions.
Tool Count2/5
A single tool is too few for most server purposes, as it typically feels thin and limits functionality. While a search tool can be useful, the server's scope appears narrow with only one operation, which may not cover the full domain of web search or related tasks adequately.
Completeness2/5
The tool surface is severely incomplete for a web search domain. It only provides a search function without any complementary tools for refining results, accessing cached pages, or handling different search types (e.g., images, news). This creates significant gaps that could lead to agent failures in more complex tasks.
Maintenance
ActivityInactive
ResponsivenessNo issues
Related MCP Connectors
Free web search for AI agents. No API key required. Hosted MCP in active development.
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…
Provides AI assistants with access to Seltz's powerful Web Search capabilities.
Live AI-native web search with citations. One tool for every MCP client. Flat per-request pricing.
Related MCP Servers
- AlicenseBqualityDmaintenanceA Model Context Protocol server that enables AI assistants to perform web searches using SearXNG, a privacy-respecting metasearch engine.143MIT
- AlicenseBqualityCmaintenanceA Model Context Protocol server that enables AI assistants to perform real-time web searches, retrieving up-to-date information from the internet via a Crawler API.1103 npm41ISC
- AlicenseAqualityCmaintenanceA Model Context Protocol server that provides real-time web search capabilities to AI assistants through pluggable search providers, currently integrated with the Brave Search API.516MIT