traylinx-search-engine-mcp-server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOG_LEVEL | No | Logging level (e.g., INFO, DEBUG) | INFO |
| AGENTIC_SEARCH_API_KEY | Yes | Your API key from traylinx.com | |
| AGENTIC_SEARCH_API_URL | Yes | The URL of the Agentic Search API endpoint | https://agentic-search-engines-n3n7u.ondigitalocean.app |
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 |
|---|---|
| searchA | Perform a web search using Traylinx's API, which provides detailed and contextually relevant results with citations. By default, no time filtering is applied to search results. |
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 single tool has a clear and distinct purpose: performing web searches.
The single tool is named 'search', which is a clear verb describing its action. Consistency is inherently maintained with only one tool.
One tool is borderline for a search engine server. While a single search endpoint can be functional, typical search APIs offer additional capabilities like pagination, filtering, or getting specific results, which would benefit from more tools.
The server provides a basic search function but lacks obvious features like time-based filtering, result pagination, or tools to retrieve additional details for specific results. These gaps may limit agent effectiveness in more complex queries.