Heventure Search MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| web_searchA | Search the web using multiple search engines. Use this tool when you need to find current information, articles, or references from the internet. Supports DuckDuckGo, Google, and Bing as free engines, with optional SerpAPI (requires SERPAPI_KEY env var) and Tavily (requires TAVILY_API_KEY env var) for higher-quality, more stable results. By default ('both'), queries DuckDuckGo and Bing concurrently and merges results, providing good coverage without any API keys. Each result includes title, URL, and description snippet. Rate limiting and caching are applied automatically. |
| get_webpage_contentA | Extract readable text content from a specific webpage URL. Use this tool after web_search when you need the full text of a page found in search results. The tool strips scripts, styles, and navigation elements, returning only the meaningful text content. Output is truncated to 2000 characters to stay within context limits. Returns an empty string if the page cannot be fetched or parsed. |
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 2 tools
The two tools have clearly distinct purposes: one searches the web, the other retrieves content from a specific URL. There is no overlap in functionality, and their descriptions make the differentiation explicit.
Both tool names follow a consistent verb_noun pattern: 'web_search' and 'get_webpage_content'. The naming is clear, predictable, and uses underscores consistently.
With only two tools, the server is minimal but well-scoped for a search-and-retrieve workflow. While more tools could be added (e.g., for advanced filtering or caching), the current count fits the server's stated purpose without being too thin.
The tool set covers the basic search workflow: find pages via web_search, then extract content via get_webpage_content. There are no obvious gaps for the intended use case of retrieving text from web pages.