io.github.makar52nn2016-jpg/money-reactor
Money Reactor
Is the Money Reactor MCP server down? Yes. It has given no valid answer since 2026-10-27: not found.
x402 APIs for AI agents: bounty radar, honeypot scoring, verdicts. USDC on Base. Stable origin.
not found down since 2026-10-27 · probed 2026-11-15 · unchanged since 2026-11-03
download answered HTTP 404
- Bundle
- https://github.com/makar52nn2016-jpg/money-reactor/releases/download/mcp-v1.0.3/money-reactor-1.0.3.mcpb (MCPB, for a client that installs bundles; probed in a container with the network off)
- Host
- github.com
- Repository
- https://github.com/makar52nn2016-jpg/money-reactor
- Website
- https://makar52nn2016-jpg.github.io/money-reactor/
- Registry
- active, updated 2026-10-16 · registry entry
Compare this server with others.
More servers
Other registry entries on github.com, the ones next to this name; all of them.
- Onchain Data MCP io.github.madlabs-tech/onchain-data-mcp · crashed on start
- Magpie Capital io.github.magpiecapital/magpie · alive
- io.github.mahach666/pilotmcp · error
- memalyze io.github.mahaoboy/memalyze · crashed on start
- X Archive RAG io.github.mameshivaa/x-archive-rag · not found
- Kato io.github.manduks/kato · alive
- LLM Provider MCP io.github.manishiitg/llm-provider-mcp · crashed on start
- Base L2 Agent Kit io.github.manteclaw/base-agent-kit · not found
Servers that mention reactor.
- RankReactor io.github.flagman5/rankreactor · needs auth
- Money Reactor io.github.makar52nn-crypto/x402-money-reactor · alive
- Money Reactor dev.workers.makar52nn2016.money-reactor/x402-money-reactor · alive
- Money Reactor io.github.makar-aibot/money-reactor-mcp · alive
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.