io.github.itechsoftsolution16/feedlio
io.github.itechsoftsolution16/feedlio
Is the io.github.itechsoftsolution16/feedlio MCP server down? Yes. It has given no valid answer since 2026-10-18: not found.
Feedlio MCP server exposing posting and scheduling tools to Claude Desktop and Claude Code.
not found down since 2026-10-18 · probed 2026-11-14
npm error 404 Note that you can also install from a npm error 404 tarball, folder, http url, or git url. npm error A complete log of this run can be found in: /
- Run it
- npx -y @itechsoftsolutions/social-mcp-server@0.1.0 (stdio, probed in a container with the network off)
- Host
- npmjs.com
- Registry
- deprecated, updated 2026-11-13 · 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.issuecapture/mcp-server · alive
- io.github.isucorp-taimiralain/stackguide-mcp · crashed on start
- io.github.itcustomsolution/approval-gate-mcp · alive
- io.github.itcustomsolution/sam-gov-mcp · alive
- view-sim io.github.itelo/view-sim · alive
- CalcBloc tax and salary calculator io.github.itmarkerz/calcbloc-mcp · alive
- io.github.itsconvo/mcp-server · alive
- io.github.itsflaid/devmap · alive
Servers that mention feedlio or scheduling or exposing.
- Feedlio io.feedlio/feedlio · needs auth
- BAMF.ai ai.bamf/bamf · not MCP
- Chronary ai.chronary/mcp · alive
- RadiusOS CRM ai.radiusos.www/crm · needs auth
- Flowral AI Tools app.flowral.mcp/planner · needs auth
- app.reassign/reassign · needs auth
- Schedii app.schedii/mcp · needs auth
- Zooza MCP Server app.zooza/mcp-server · not MCP
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-18, 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.