io.github.ZebpayRajesh/zebpay-mcp-server
ZebPay MCP Server
Is the ZebPay MCP server down? Yes. It has given no valid answer since 2026-10-16: not found.
MCP server for ZebPay crypto exchange — fetch prices, balances, and manage orders
not found down since 2026-10-16 · probed 2026-11-15 · unchanged since 2026-10-30
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 @zebpay_rajesh/zebpay-mcp-server@1.0.1 (stdio, probed in a container with the network off)
- Host
- npmjs.com
- Repository
- https://github.com/zebpay/zebpay-mcp-server
- Registry
- active, updated 2026-03-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.
- Agent API Gateway io.github.ZachDreamZ/agent-api-gateway · alive
- ChatCrystal io.github.ZengLiangYi/chatcrystal · crashed on start
- ZennoBrowser MCP Server io.github.ZennoLab/zennobrowser · needs network
- io.github.ZentricProtocol/zentric-protocol-mcp · alive
- PlayGuard io.github.ZenyaDAR/playguard · crashed on start
- Salesforce Marketing io.github.ZLeventer/salesforce-marketing-mcp · alive
- io.github.ZUHcYa/ai-validation · alive
- io.github.ZUHcYa/eu-food-regulatory · alive
Servers that mention balances or exchange.
- Inside Ads ad.inside/inside-ads · alive
- Agentgates Wallet ai.agentgates/mcp · needs auth
- AgenticBooks ai.agenticbooks/books · needs auth
- ai.agentberg/agentberg · alive
- Duami ai.duami/intent-exchange · alive
- ai.fincontext/fincontext · needs auth
- Lamdis Exchange ai.lamdis/exchange · no DNS
- ai.smithery/HARJAP-SINGH-3105-splitwise_mcp · 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-16, 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.