OptimAI Search MCP
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OPTIMAI_API_KEY | Yes | Your OptimAI External API key (X-API-Key) |
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 |
|---|---|
| optimai_start_searchA | Start a Web3-focused AI search on the OptimAI decentralised network and return immediately with a search ID. Use this because searches commonly take 60-90 seconds or the MCP host has short tool-call timeouts. Call optimai_get_search with the returned ID to check progress and fetch the final answer. |
| optimai_searchA | Run a Web3-focused AI search on the OptimAI decentralised network. Waits briefly for results and returns a structured answer with citations when ready. If the search is still running, it returns the search ID so optimai_get_search can fetch it later. Use this when the user wants up-to-date information about crypto, DeFi, NFTs, blockchain projects, or any on-chain topic. |
| optimai_get_searchA | Retrieve the current status and result of a previously created search by its ID. Useful for checking on a search that was started earlier or is still in progress. |
| optimai_list_searchesA | List recent searches made with this API key. Supports filtering by status, date range, and pagination. |
| optimai_cancel_searchA | Cancel a running or pending search by its ID. Completed, failed, or already-cancelled searches cannot be cancelled. |
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 5 tools
The tools optimai_search and optimai_start_search are nearly identical in purpose: both initiate a search and return a search ID if the search is not complete. The only difference is that optimai_search waits briefly for results, but in typical long-running searches, they behave the same. This overlap creates significant ambiguity for an agent deciding which tool to use.
The naming pattern is mostly consistent with the optimai_ prefix and verb_noun structure: get_search, list_searches, cancel_search, start_search. However, optimai_search is a bare verb and does not follow the verb_noun pattern, standing out as a deviation. This is a minor inconsistency but does not severely hinder readability.
Five tools is well-scoped for a search API, covering initiation, retrieval, listing, and cancellation without unnecessary bloat. Each tool serves a distinct lifecycle function, and the count feels appropriate for the domain.
The tool set provides complete lifecycle coverage for asynchronous searches: start a search (start_search, or the combined optimai_search), check status/results (get_search), list past searches (list_searches), and cancel in-progress ones (cancel_search). No important operations are missing, and the composite optimai_search covers the synchronous wait case.