io.github.MIt9/silpo-mcp
Silpo MCP Server
Is the Silpo MCP server down? Yes. It has given no valid answer since 2026-10-17: not found.
MCP server for Silpo online supermarket: products, cart, delivery, recipes.
not found down since 2026-10-17 · probed 2026-11-15 · unchanged since 2026-10-31
npm error notarget In most cases you or one of your dependencies are requesting npm error notarget a package version that doesn't exist. npm error A complete lo
- Run it
- npx -y silpo-mcp@1.1.0 (stdio, probed in a container with the network off)
- Host
- npmjs.com
- Repository
- https://github.com/MIt9/silpo-mcp
- Registry
- active, updated 2026-02-06 · registry entry
Compare this server with others.
More servers
Other registry entries on npmjs.com, the ones next to this name; all of them.
- io.github.MCPShield-Dev/mcpshield · needs env
- Turnback io.github.MFaizR77/turnback · alive
- Security Detections io.github.MHaggis/security-detections-mcp · crashed on start
- ComfyUI Builder io.github.MIt9/comfy-ui-builder · no executable
- io.github.MK3Core/flickr-mcp · needs env
- Scribefy io.github.MKirovBG/scribefy-mcp · alive
- io.github.MMasey/atag-mcp · alive
- io.github.MNKIAgentOS/mnki-mcp · needs args
Servers that mention supermarket or delivery.
- FairMind Project Context ai.fairmind/project-context · needs auth
- offerhopper.ai — AI Supermarket & Drugstore Shopping Assistant for Germany ai.offerhopper.mcp/german-grocery-assistant · alive
- Picsha AI ai.picsha/picsha · needs auth
- Pocket Drives ai.pocketdrives/pocket-drives · alive
- Routing24 ai.routing24/mcp · needs auth
- ai.robomart/robomart · alive
- ai.uxbert/cms · needs auth
- ai.waiter24/mcp · 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.
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
- No valid answer since 2026-10-17, in every probe since then.
- The endpoint answers HTTP 404. The registry entry points to a URL that is not an MCP endpoint any more. Publish a new version of the registry entry with the current URL.