Free MCP server: index a repo's files into the live x402-codesearch Worker's semantic-search index. Open funnel twin of a paid x402-gated codesearch HTTP API.
claude mcp add x402-codesearch-mcp -- npx -y x402-codesearch-mcp{
"mcpServers": {
"x402-codesearch-mcp": {
"command": "npx",
"args": ["-y", "x402-codesearch-mcp"]
}
}
}MCP Servers overview
# x402-codesearch-mcp
A free MCP (Model Context Protocol) server that indexes a repo's files —
chunked and embedded — into the live semantic code search Worker, for free,
via one MCP tool: `index_code`.
This is the **open funnel twin** of a paid, x402-gated HTTP API:
**[x402-codesearch-poc.theliminalguy.workers.dev](https://x402-codesearch-poc.theliminalguy.workers.dev)**
— `POST /search`, $0.01 USDC on Base per query via the
[x402 payment protocol](https://x402.org), for the actual semantic search
step over an indexed repo.
## Why this one is different from the other free twins (read this first)
Sibling packages like [`x402-repohealth-mcp`](https://github.com/liminalpepe/x402-repohealth-mcp)
fully reimplement their paid Worker's logic locally (pure functions, no
external account-bound dependency) and expose the *entire* feature for
free via MCP.
This package **cannot** do that. The paid Worker's semantic search depends
on two Cloudflare-account-bound bindings with no free, local, or portable
equivalent:
- **Workers AI** (`@cf/baai/bge-base-en-v1.5`) — generates the embeddings
- **Vectorize** — stores and queries those embeddings by cosine similarity
Both only exist inside the Worker's own Cloudflare account. There is no way
to run them for free outside that account, so this MCP server does not try
to fake or proxy them.
What genuinely *is* free is `POST /index` on the live Worker itself — the
step that chunks a file, embeds it, and upserts it into that Worker's own
Vectorize index. That's the one real, free, stateless capability this
package exposes as an MCP tool. The matching `POST /search` step stays
exactly where it already is: a real x402-gated HTTP call directly against
the live Worker.
## What it does
One tool, `index_code`:
- Input: `{ repoId: string, files: [{ path: string, content: string }] }`
- Calls `POST https://x402-codesearch-poc.theliminalguy.workers.dev/index`
(free, no payment) with that exact body.
- Output: `{ repoId, filesIndexed, chunksIndexed }` plus a `note` field
reminding the caller that searching what was just indexed requires the
paid endpoint.
It does **not** expose a `search_code` tool. Semantic search over data
indexed with this tool requires calling the x402-gated endpoint directly:
```
POST https://x402-codesearch-poc.theliminalguy.workers.dev/search
Body: { "repoId": "...", "query": "..." }
Price: $0.01 USDC on Base, via the x402 protocol (e.g. x402-fetch / x402-axios)
```
An unpaid request to `/search` returns `402 Payment Required` with real
x402 payment instructions.
## Install & run
```bash
npx x402-codesearch-mcp
```
Or add it to an MCP client config (e.g. Claude Desktop's
`claude_desktop_config.json`):
```json
{
"mcpServers": {
"codesearch": {
"command": "npx",
"args": ["-y", "x402-codesearch-mcp"]
}
}
}
```
## Tool: `index_code`
Input:
```jsonc
{
"repoId": "my-repo",
"files": [
{ "path": "src/retry.py", "content": "def retry_with_backoff(...): ..." }
]
}
```
Output (MCP tool text content, JSON-stringified):
```jsonc
{
"repoId": "my-repo",
"filesIndexed": 1,
"chunksIndexed": 2,
"note": "Indexing succeeded (free). To semantically search this repoId, call the x402-gated POST https://x402-codesearch-poc.theliminalguy.workers.dev/search directly ($0.01 USDC on Base per query) — not available through this free MCP tool."
}
```
## Local development
```bash
npm install
npm run dev # runs src/index.ts directly on stdio via tsx
npm run build # compiles to dist/ for the published npm package
npm run test:index # calls indexCode() directly against the real live Worker, no MCP transport
```
`src/client.ts` and `src/types.ts` hold the thin HTTP client against the
live Worker's `/index` endpoint — `src/index.ts` is a thin MCP wrapper
around `indexCode()`.
## What's real vs. limited
- **Real:** the `POST /index` call this tool makes goes to the actual live
Worker, which really chunks the given files, really calls Workers AI for
embeddings, and really upserts into Vectorize — nothing here is mocked or
hardcoded. Verified end-to-end against the live Worker (see below).
- **Genuinely free:** `POST /index` requires no payment and no API key —
confirmed live, not just documented.
- **Not free, and not exposed here by design:** `POST /search` on the same
Worker. That's a deliberate scope boundary, not an oversight — see "Why
this one is different" above.
- **No local caching/dedup:** every `index_code` call re-POSTs to the live
Worker; re-indexing the same file just re-chunks/re-embeds/re-upserts it.
## When to use the paid HTTP twin directly
Use `POST /search` on the live Worker instead of (in addition to) this MCP
server when:
- You've indexed a repo with `index_code` and now want to actually search
it semantically.
- Your agent already speaks x402 (e.g. via `x402-fetch` / `x402-axios`) and
can pay $0.01 USDC on Base per query.
- You need production/high-volume search — this MCP server's `index_code`
tool shares the same free `/index` endpoint as every other caller, but
`/search` is metered per call regardless of caller.
## License
MIT
What people ask about x402-codesearch-mcp
What is liminalpepe/x402-codesearch-mcp?
+
liminalpepe/x402-codesearch-mcp is mcp servers for the Claude AI ecosystem. Free MCP server: index a repo's files into the live x402-codesearch Worker's semantic-search index. Open funnel twin of a paid x402-gated codesearch HTTP API. It has 0 GitHub stars and was last updated today.
How do I install x402-codesearch-mcp?
+
You can install x402-codesearch-mcp by cloning the repository (https://github.com/liminalpepe/x402-codesearch-mcp) or following the README instructions on GitHub. ClaudeWave also provides quick install blocks on this page.
Is liminalpepe/x402-codesearch-mcp safe to use?
+
liminalpepe/x402-codesearch-mcp has not been audited yet by our security agent. Review the original repository on GitHub before using it in production.
Who maintains liminalpepe/x402-codesearch-mcp?
+
liminalpepe/x402-codesearch-mcp is maintained by liminalpepe. The last recorded GitHub activity is from today, with 0 open issues.
Are there alternatives to x402-codesearch-mcp?
+
Yes. On ClaudeWave you can browse similar mcp servers at /categories/mcp, sorted by popularity or recent activity.
Deploy x402-codesearch-mcp to your cloud
Ship this repo to production in minutes. Each platform spins up its own environment with editable env vars.
Maintain this repo? Add a badge to your README
Drop the badge into your GitHub README to show it's tracked on ClaudeWave. Each badge links back to this page and reflects the live Trust Score.
[](https://claudewave.com/repo/liminalpepe-x402-codesearch-mcp)<a href="https://claudewave.com/repo/liminalpepe-x402-codesearch-mcp"><img src="https://claudewave.com/api/badge/liminalpepe-x402-codesearch-mcp" alt="Featured on ClaudeWave: liminalpepe/x402-codesearch-mcp" width="320" height="64" /></a>More MCP Servers
Fair-code workflow automation platform with native AI capabilities. Combine visual building with custom code, self-host or cloud, 400+ integrations.
User-friendly AI Interface (Supports Ollama, OpenAI API, ...)
An open-source AI agent that brings the power of Gemini directly into your terminal.
The fastest path to AI-powered full stack observability, even for lean teams.
Real-time global intelligence dashboard. AI-powered news aggregation, geopolitical monitoring, and infrastructure tracking in a unified situational awareness interface
🕷️ An adaptive Web Scraping framework that handles everything from a single request to a full-scale crawl!