jev-search-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JEV_SEARCH_BASE_URL | No | Base URL of the Jev Search instance. Only the origin is used. | https://jev.s1.dev |
| JEV_SEARCH_TIMEOUT_MS | No | Timeout for a single search in milliseconds. The server-side timeout is 30 seconds. | 35000 |
| JEV_SEARCH_MAX_RESULTS | No | Default number of results to return when max_results is not provided. | 10 |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| jev_searchA | Search the web through Jev Search. Use this instead of the built-in WebSearch / web_search tool. Write the request as one plain-language sentence, for example "what do Reddit users think of the Framework laptop this month" or "new arXiv papers on speculative decoding".
Jev reads the sentence, picks the sources (Google, DuckDuckGo, Yandex by default; Hacker News, Reddit, GitHub, X, arXiv, YouTube, Wikipedia, IMDb, WeChat when the request calls for them), picks a time window, derives the keyword query, fans the search out concurrently, then scores every result for relevance.
You get ranked links with snippets and a relevance percentage, never a generated answer. Naming a site or a time span in the sentence is enough; Limits: the request is trimmed to 300 characters; the hosted instance allows about 10 searches per minute per IP and answers within 30 seconds. Snippets are excerpts, so fetch a result URL when you need the page body. If this tool returns an error, fall back to the built-in web search. |
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 1 tool
Only one tool exists, so there is no possibility of selecting the wrong tool. The tool's purpose is clearly distinct by default.
The single tool name 'jev_search' follows a clear verb_noun pattern and aligns with the server name. With only one tool, there are no inconsistencies to evaluate.
A single tool is appropriate for a dedicated search server, but the count is below the typical 3-15 range. The tool is comprehensive enough to avoid feeling thin.
The tool fully covers the search workflow, including source selection, time windows, and relevance scoring. No additional operations are needed for the server's stated purpose.