io.github.ramaris-app/mcp-server
io.github.ramaris-app/mcp-server
Is the io.github.ramaris-app/mcp-server MCP server down? Yes. It has given no valid answer since 2026-10-18: not found.
On-chain wallet analytics and trading strategies on Base for AI assistants
not found down since 2026-10-18 · probed 2026-11-14 · unchanged since 2026-11-01
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 @ramaris/mcp-server@0.1.4 (stdio, probed in a container with the network off)
- Host
- npmjs.com
- Repository
- https://github.com/ramaris-app/mcp-server
- Registry
- active, updated 2026-02-15 · registry entry
Compare this server with others.
More servers
Other registry entries on npmjs.com, the ones next to this name; all of them.
- isitdone io.github.raimondasl/isitdone · alive
- HIG Doctor io.github.raintree-technology/hig-doctor · alive
- io.github.rajanrengasamy/vidlens-mcp · alive
- io.github.rajat79suri/visa-info · alive
- Project Consulting: Index io.github.ramirkoz/project-consulting · alive
- io.github.randomblocker/supercolony · alive
- Pi-hole MCP Server io.github.ranklancer/pihole-mcp · needs env
- io.github.raphysicst-create/korean-secondary-learning-map-mcp · alive
Servers that mention assistants or strategies.
- Adako: ad ops for AI assistants ai.adako/ads · needs auth
- Bindry ai.bindry/bindry · needs auth
- ai.beket/audit · needs auth
- ai.butlerbrain/mcp · needs auth
- HAPI MCP Server ai.com.mcp/hapi-mcp · needs your URL
- Divinci AI ai.divinci/divinci · needs auth
- fenbs ai.fenbs/fenbs · needs auth
- ai.izap/whatsapp · 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.