ds-websearch-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CACHE_TTL_MS | No | Fixed snapshot lifetime: 12 hours. | 43200000 |
| CACHE_MAX_BYTES | No | Retained text capacity: 256 MiB. | 268435456 |
| DEEPSEEK_API_KEY | Yes | DeepSeek bearer token. | |
| CACHE_MAX_ENTRIES | No | Maximum retained snapshots. | 256 |
| DEEPSEEK_BASE_URL | No | API origin, useful for gateways or local testing. Requests use /v1/tools/search and /v1/tools/fetch. | https://api.deepseek.com/ |
| HTTP_MAX_SESSIONS | No | Maximum concurrent legacy HTTP sessions. | 64 |
| REQUEST_TIMEOUT_MS | No | Total deadline per API call, including retries and response reading. Maximum: 2147483647 ms. | 30000 |
| HTTP_SESSION_IDLE_MS | No | Idle lifetime for legacy HTTP sessions: 30 minutes. Sessions with active requests are not expired. | 1800000 |
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 using DeepSeek. Supports site:, -site:, quoted phrases, lang:, after:, and before:. The API currently documents a 128-character query limit. Page content is optional and paginated; read more with fetch(cursor). |
| fetchA | Read a web page as Markdown, or continue a cached page using next_cursor from search or fetch. Supply exactly one of url or cursor. Cursors read the same saved snapshot without another API request; they can expire or be evicted. |
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
Search is for discovering web results via a query with operators, while fetch is for reading a specific URL or continuing a cached snapshot via cursor. The two tools have clearly distinct roles and no overlapping functionality.
Both names are single lowercase verbs (search, fetch), following a consistent verb-only convention. There are no mixed styles or inconsistent patterns.
Two tools is slightly below the typical 3–15 range, but each earns its place for this narrow search-and-fetch domain. The minimal surface is reasonable rather than thin, given the focused purpose.
Search plus fetch covers the full lifecycle: query the web, then retrieve full page content with pagination via cursors. No obvious gaps exist, and cursor expiry can be handled by re-searching.