icu.steeped.registry/nodejsmcp
icu.steeped.registry/nodejsmcp
A Forgejo MCP Server
not probed in the official registry, not probed
- Run it
- npx -y nodejsmcp@1.0.3 (stdio, probed in a container with the network off)
- Host
- npmjs.com
- Registry
- active, updated 2025-11-18 · registry entry
Compare this server with others.
More servers
Other registry entries on npmjs.com, the ones next to this name; all of them.
- Slingshot brand kit fyi.slingshot/brand-kit · alive
- Miniant Games games.miniant/miniantgames-mcp · alive
- RightSide host.rightside/mcp · alive
- Snapy.host host.snapy/snapy · alive
- Kundali Chart — Vedic Astrology MCP in.acerank.vedic-kundli/kundali-chart-mcp · timeout
- Koragraph in.koragraph/koragraph · alive
- MemoryLayer in.memorylayer/memorylayer · needs args
- io.allourthings/mcp-server · needs env
Servers that mention forgejo.
- gitea-mcp io.github.werebear73/gitea-mcp · alive
- Forgejo / Codeberg / Gitea io.github.brechanbech/forgejo-mcp-rs · not probed
- Skipper io.github.seuros/skipper · not probed
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
- The entry has only a package that serves streamable-http. The probe starts packages that talk over stdio only. The entry is on the board so that the list holds the whole registry and says what it does not check.