io.github.virgilvox/furlow-mcp

Is the io.github.virgilvox/furlow-mcp MCP server down? Yes. It has given no valid answer since 2026-10-16: install failed.

Author FURLOW Discord bot YAML: validate specs, list actions/events/builtins, scaffold bots.

install failed down since 2026-10-16 · probed 2026-11-15 · unchanged since 2026-10-30

npm error code EUNSUPPORTEDPROTOCOL npm error Unsupported URL Type "workspace:": workspace:* npm error A complete log of this run can be found in: /root/.npm/_l

Run it: npx -y @furlow/mcp@1.0.1 (stdio, probed in a container with the network off)
Host: npmjs.com
Repository: https://github.com/virgilvox/discord-furlow
Registry: active, updated 2026-04-20 · 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.vince-gonzalez/cvdsafe · alive
Devloop io.github.vincentvella/devloop · alive
io.github.vineethwilson15/semamerge · alive
Apiverket io.github.vinvuk/apiverket-mcp · alive
io.github.virgilvox/vue-harvest · install failed
io.github.vishalguptax/media-context-mcp · alive
PDF Triage io.github.vishalmeena2211/pdf-triage-mcp · needs args
io.github.vishvick/dealhub-admin · needs env

Servers that mention builtins or scaffold.

AdCritter for Builders com.adcritter/mcp-dev · alive
RepoFuse com.repofuse/repofuse · needs auth
com.scaffoldingcostcalculator/site · alive
webforJ MCP Server com.webforj/mcp · alive
Fillo io.github.jacobfunch/usefillo · needs auth
@imqueue org.imqueue/mcp · alive
dev.avakit/avalanche · alive
Archiet io.github.aniekanasuquookono-web/archiet · crashed on start

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

No valid answer since 2026-10-16, in every probe since then.
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.