CubicJ MCP Search
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | HTTP port used when --port is absent | |
| GITHUB_TOKEN | No | Optional token for higher GitHub API limits in fetch | |
| BRAVE_API_KEY | Yes | Brave Search API key (Search plan) for 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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| web_searchA | Search the web and get relevance-ranked page excerpts for each result, ready to read and cite. First tool for any research, fact lookup, or URL discovery; most questions need one call and no follow-up fetch. Operators use a colon: site:example.com, "exact phrase", -excluded. count sets how many source URLs (1-20, default 8); max_tokens caps the total excerpt size (1024-32768, default 8192); freshness limits results by date (pd, pw, pm, py, or YYYY-MM-DDtoYYYY-MM-DD); country and search_lang scope the market. Returns JSON: query, result_count, results[{title, url, site, age, snippets[]}]. |
| fetchA | Fetch one URL and return its readable content as markdown with a title and metadata. Use it to read a page in full after web_search, or any URL the user gives: articles, docs, forums, news. Site-specific extractors return post body plus comments for gall.dcinside.com, Clien, Ruliweb, and FMKorea; body only for blog.naver.com and namu.wiki; threads with replies and profiles with recent posts for bsky.app; raw content or REST data for github.com files, repos, issues, pull requests, and gists. Non-HTML text (JSON, XML, RSS, plain text) is returned as-is; PDFs as page-separated text with page_count; image-only PDFs return a notice; other binaries are errors. raw=true skips extraction and returns the decoded response text. Long content is paginated: content is sliced from start_index (default 0) for max_length characters (default 50000); to continue, call again with start_index advanced by the previous max_length and stop when start_index + max_length >= total_length. Bot-protection pages return an error; empty pages that need JavaScript or a login return a notice. |
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
web_search handles discovery with ranked excerpts, while fetch retrieves and extracts full content from a single URL. Their roles are clearly distinct and the descriptions reinforce when to use each.
fetch is a bare verb and web_search is a compound noun/verb form, so there is no shared verb_noun pattern. Both are readable and common, but the conventions are mixed.
Two tools cover the core search-and-retrieve workflow without redundancy, but the count is slightly below the typical 3–15 range. Each tool earns its place for the server's narrow purpose.
The surface covers discovery via web_search and retrieval via fetch, including pagination and many site-specific extractors. Minor gaps like batch fetching or search pagination exist, but there are no major dead ends.