io.github.amirj4m/jamgate
io.github.amirj4m/jamgate
Is the io.github.amirj4m/jamgate MCP server down? Yes. It has given no valid answer since 2026-10-18: not found.
A neutral memory quality-gate MCP server: save_memory, recall_memory, forget_memory over stdio.
not found down since 2026-10-18 · probed 2026-11-14 · unchanged since 2026-11-01
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 jamgate@0.20.0 (stdio, probed in a container with the network off)
- Host
- npmjs.com
- Repository
- https://github.com/amirj4m/jamgate
- Registry
- active, updated 2026-08-11 · 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.amer-prog/gamma-mcp-server · crashed on start
- ohmyho.st io.github.amerged-org/ohmyhost-mcp · alive
- io.github.amidabuddha/jev-decision-mcp · needs env
- KVM/libvirt VMs and backups (Fedora) io.github.amineutron/fedora-agents · alive
- Parsi MCP io.github.amirjld/parsi-mcp · alive
- io.github.amitsha86/furlen-mcp · alive
- ENCODE Toolkit io.github.ammawla/encode-toolkit · crashed on start
- io.github.amol21p/interactive-terminal · alive
Servers that mention neutral or quality.
- ai.agentberg/agentberg · alive
- AgentPlaybooks ai.agentplaybooks/agentplaybooks · needs auth
- AnomalyArmor ai.anomalyarmor/armor-mcp · needs auth
- Aviado AI ai.aviado/health · alive
- i18n-agent ai.i18nagent/i18n-agent · needs auth
- ai.iturri/market-data · alive
- myplot.ai Property Intelligence ai.myplot/property-intelligence · not found
- Nimrod ai.orchis/nimrod · needs auth
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.