io.github.juangp3/j2c
J2C Java to C++
Is the J2C Java to C++ MCP server down? Yes. It has given no valid answer since 2026-10-27: not found.
Check Java 17 code for C++ translation problems, fix them, and translate it to C++20.
not found down since 2026-10-27 · probed 2026-11-15 · unchanged since 2026-10-29
command not found: node
- Run it
- npx -y @juangp3/j2c-mcp@0.6.1 (stdio, probed in a container with the network off)
- Host
- npmjs.com
- Repository
- https://github.com/juangp3/j2cpp
- Website
- https://github.com/juangp3/j2cpp
- Registry
- active, updated 2026-10-27 · registry entry
Compare this server with others.
More servers
Other registry entries on npmjs.com, the ones next to this name; all of them.
- Meltbead Craft Colors io.github.jsspace/bead-colors-mcp · alive
- Asana MCP Server io.github.jtalk22/asana-mcp-server · needs env
- Magento Cloud MCP Server io.github.juan-cinto-infracommerce/magento-cloud · alive
- io.github.juan-sibbo/gam-seller-mcp-node · crashed on start
- io.github.juanisidoro/securecode · alive
- io.github.juanklagos/sdd-mcp · alive
- io.github.jugbeep/lustre · alive
- io.github.juh5ng/k-data-mcp · needs env
Servers that mention java.
- xmp4 — Semantic code knowledge for your stack ai.example4/xmp4 · alive
- npm Release Tracker — new Node.js packages & JavaScript dependency updates (npmwatch) com.a2awire/data-npm-release-node-package-javascript-dependency · alive
- ByJG Open Source Docs com.byjg/docs · alive
- URLpipe dev.urlpipe/mcp · alive
- io.github.AccelByte/ags-extend-sdk-mcp-server · needs your URL
- Code Sandbox API io.github.Br0ski777/code-sandbox · TLS error
- SmartFetch io.github.Friezaaaa/smartfetch · not found
- JAIPilot io.github.JAIPilot/jaipilot · not found
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-27, 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.