io.github.SK-DEV-AI/codesearch

Is the io.github.SK-DEV-AI/codesearch MCP server down? It gave no valid answer in the probe of 2026-11-04: install failed. One failed probe is not an outage.

Code, package, docs, paper and vulnerability search. 17 tools, keyless lanes.

install failed no valid answer since 2026-11-04 · probed 2026-11-14 · unchanged since 2026-11-04

error: failed to write to file `/work/uv/.gitignore`: No space left on device (os error 28)

Run it: uvx skdev-codesearch-mcp@1.0.1 (stdio, probed in a container with the network off)
Host: pypi.org
Repository: https://github.com/SK-DEV-AI/codesearch
Registry: active, updated 2026-10-23 · registry entry

Compare this server with others.

More servers

Other registry entries on pypi.org, the ones next to this name; all of them.

Clover POS io.github.SBolivarLoL/clover-mcp · alive
io.github.SCDOLAB/scdo-agent-mcp · alive
io.github.SCGIS-Wales/helm-mcp · needs env
Delhaize receipts io.github.SHIMABEIGI/delhaize-mcp · alive
io.github.SK-DEV-AI/websearch · alive
io.github.SMABoundless/crossref · needs mcp<2
io.github.SMABoundless/orcid · needs mcp<2
io.github.SMABoundless/scopus · needs mcp<2

Servers that mention codesearch or vulnerability or keyless.

com.clauxel.semblecodesearchgate/semblecodesearchgate-mcp · no DNS
io.github.liminalpepe/x402-codesearch-mcp · alive
ai.askmiles/catalog · alive
ai.bidclub/bidclub · alive
Builders in Fintech ai.buildersinfintech/fintech-data · alive
ai.deskcrew/agentic · not found
ai.duvera/gateway · alive
ai.dynamicfeed/dynamic-feed · not found

Badge for the README

The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.

Atom feed

A mail when this server changes

Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.

For the publisher

The package did not start as an MCP server at its probe on 2026-11-04. One failed probe is not an outage: the board calls a package down when it fails again at its next probe, a week later.
npx or uvx could not install the package. The package name in the registry entry is wrong, the package is not published, or the install needs a build step.