io.github.pdeloulay/flik-mcp
Flik
Is the Flik MCP server down? Yes. It has given no valid answer since 2026-10-26: not found.
Flik - Agentic Product Delivery Platform. Visit flik.nomadis.com for more information.
not found down since 2026-10-26 · probed 2026-11-15 · unchanged since 2026-11-02
command not found: server/flik-mcp
- Bundle
- https://github.com/pdeloulay/flik-mcp/releases/download/v0.3.15/flik-mcp.mcpb (MCPB, for a client that installs bundles; probed in a container with the network off)
- Host
- github.com
- Repository
- https://github.com/pdeloulay/flik-mcp
- Registry
- active, updated 2026-02-15 · registry entry
Compare this server with others.
More servers
Other registry entries on github.com, the ones next to this name; all of them.
- agentpc io.github.pawanpaudel93/agentpc · crashed on start
- RevRule by Payload io.github.payload-tools/revrule-mcp · alive
- Veyline by Payload io.github.payload-tools/veyline-mcp · alive
- Flik io.github.pdeloulay/flik · not found
- Fruit Forwarder MCP io.github.pdfowler/fruit-forwarder · crashed on start
- PhilForms io.github.philforms/philforms-mcp · alive
- io.github.piotrkowalczuk/zordon · needs env
- Rowlite MCP Server io.github.pipik-roman/rowlite · install failed
Servers that mention flik or information or delivery.
- Scout io.github.Flikah/scout-mcp · server error
- io.github.jackkatzman/genflik · needs auth
- FairMind Project Context ai.fairmind/project-context · needs auth
- Loci Labs Real-World Observations ai.loci-labs/real-world-observations · 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
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-26, 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.