io.github.kiycoh/silica-core
Silica Core
Is the Silica Core MCP server down? No. It is up and needs args, probed 2026-11-08.
Retrieval over the folder the session opened: files, search, read, code_pack, write_note.
needs args probed 2026-11-15 · unchanged since 2026-11-08
MCP error -32000: Connection closed
usage: silica-core [-h] [--vault DIR] [--version]
{files,search,read,code-pack,write-note,index,repl,mcp,- Run it
- uvx silica-core@0.13.0 (stdio, probed in a container with the network off)
- Host
- pypi.org
- Repository
- https://github.com/kiycoh/silica-core
- Website
- https://github.com/kiycoh/silica-core#readme
- Registry
- active, updated 2026-11-08 · registry entry
- Changes
- 2 recorded, reachable in 0 of them. A row is added when the result, the tool count or the cost changes.
Compare this server with others.
More servers
Other registry entries on pypi.org, the ones next to this name; all of them.
- Provenza io.github.kironovlaziz-del/provenza · crashed on start
- Pyxel MCP io.github.kitao/pyxel-mcp · alive
- Proof of Work io.github.kivtxs/pow · alive
- io.github.kiwoongeom/gmc-mcp · needs env
- io.github.klein-business/legal-text-mcp-de · crashed on start
- 3D Visualizer io.github.kleinicke/3d-visualizer · needs args
- Data Olympus io.github.knaisoma/data-olympus · not probed
- pyxsd io.github.knorby/pyxsd · needs args
Servers that mention silica.
- com.silicann/spektralwerk-docs · error
- ExtractEdge io.github.vasilicasijarvis/extractedge · not found
- FlowSentry io.github.vasilicasijarvis/flowsentry · not found
- Silica io.github.simaanc/silica-eda · alive
History
We add a row when the result changes. A server with no change keeps its last row.
| Probed | Result | Init | Tools | Claude | o200k |
|---|---|---|---|---|---|
| 2026-10-31 07:35 | needs args | ||||
| 2026-10-17 06:21 | install failed |
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.
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 server needs command line arguments that the registry entry does not list. Add them to the package arguments in the registry entry.