deep-search-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LINKUP_API_KEY | Yes | Your LinkUp API key for deep web search |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| deep_searchB | Perform a deep web search using LinkUp API |
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
With only one tool, there is no possibility of confusion between tools. The tool's purpose is clearly stated as performing a deep web search.
The single tool name 'deep_search' follows a clear verb_noun convention. There are no other tools to introduce naming inconsistencies.
A single tool is borderline thin for a search server, which might benefit from additional operations like result filtering or history. However, for a very narrow scope, it could be acceptable.
The tool covers the core search action but lacks ancillary capabilities that users might expect, such as pagination, saved searches, or multi-phase queries. This leaves the surface minimal and somewhat incomplete for complex workflows.