io.github.szarl/payments-ai-mcp
io.github.szarl/payments-ai-mcp
Is the io.github.szarl/payments-ai-mcp MCP server down? Yes. It has given no valid answer since 2026-10-17: install failed.
Launch products and branded checkouts on Payments AI, the Merchant of Record for AI-built apps.
install failed down since 2026-10-17 · probed 2026-11-15 · unchanged since 2026-10-31
npm error A complete log of this run can be found in: /root/.npm/_logs/2026-11-14T08_11_48_036Z-debug-0.log
- Run it
- npx -y @payments-ai/mcp@1.1.3 (stdio, probed in a container with the network off)
- Host
- npmjs.com
- Repository
- https://github.com/paymentsai/pai-managed
- Registry
- active, updated 2026-07-09 · registry entry
Compare this server with others.
More servers
Other registry entries on npmjs.com, the ones next to this name; all of them.
- io.github.sypherin/sgdata-mcp · crashed on start
- TokenMark io.github.sypherin/tokenmark-mcp · alive
- Algeria io.github.syscli/algeria-mcp · alive
- SkeptOpus io.github.systasys/skeptopus · alive
- Recon Crypto MCP io.github.szhygulin/recon-crypto-mcp · alive
- VaultPilot MCP io.github.szhygulin/vaultpilot-mcp · alive
- io.github.sznt2010/agentresources-mcp · needs env
- io.github.szp2005/remove-ac · crashed on start
Servers that mention payments.
- Agentic Terminal Directory ai.agenticterminal/directory · alive
- Cabrini Market Data ai.cabrini/market-data · TLS error
- Doklad.ai ai.doklad/mcp · needs auth
- Kifly — Agentic Commerce & Payments ai.kifly/mcp · alive
- Lattiq x402 Trading Signals ai.lattiq/x402-trading-signals · no DNS
- ai.payments.managed/payments-ai-mcp · no DNS
- SAP MCP Server ai.oobeprotocol.sap.mcp/sap-mcp · alive
- Pyrimid Protocol ai.pyrimid/pyrimid · paid (402)
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-17, in every probe since then.
- npx or uvx could not install the package. The package name in the registry entry is wrong, the package is not published, or the install needs a build step.