x402-codesearch-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 |
|---|---|
| index_codeA | Index a repo's files into the live x402-codesearch Worker (https://x402-codesearch-poc.theliminalguy.workers.dev) so they become semantically searchable: each file is chunked, embedded via Workers AI, and upserted into that repoId's Vectorize index. Free, unauthenticated MCP tool — no payment required to index. IMPORTANT: this tool only calls the free POST /index endpoint. The matching semantic search step (POST /search on the same Worker) is real but x402-gated at $0.01 USDC on Base per query, and depends on Cloudflare Vectorize + Workers AI bindings that have no free or local equivalent — so it is NOT exposed here. To actually search a repo you've indexed with this tool, call POST https://x402-codesearch-poc.theliminalguy.workers.dev/search directly with an x402-aware HTTP client (e.g. x402-fetch / x402-axios) and a funded Base wallet, passing { repoId, query }. |
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 or overlap. The tool's purpose (indexing code) is clearly distinct from any other, as there are no other tools.
The single tool follows a clear verb_noun pattern ('index_code'), which is consistent and descriptive. There are no other tools to introduce inconsistency.
Having only one tool for a 'codesearch' server is severely insufficient. The index tool is only half of the workflow; the search operation is intentionally not exposed, making the tool count a poor match for the apparent scope.
The core functionality of a codesearch server—searching—is completely missing from the MCP toolset. Only indexing is provided, and the description explicitly notes that search must be done via an external endpoint. This is a critical gap that prevents the tool from fulfilling its stated purpose.