click.myinfrastructure/payments
Payments
Is the Payments MCP server down? No. It is up and needs auth (HTTP 401), probed 2026-11-06.
Planos, assinaturas, links de pagamento e métricas
needs auth probed 2026-11-15 · unchanged since 2026-11-06 · HTTP 401 · Bearer
Streamable HTTP error: Error POSTing to endpoint: {"jsonrpc":"2.0","id":null,"error":{"code":-32001,"message":"Token de acesso necessário"}}- Endpoint
- https://payments.worker.myinfrastructure.click/mcp (streamable-http)
- Host
- payments.worker.myinfrastructure.click
- Getting access
- OAuth without dynamic client registration. Ask the publisher for a client id first; with it, a client can run the consent.
Authorization server auth.worker.myinfrastructure.click, PKCE S256, grants authorization_code, refresh_token.
Scopes auth:read auth:write.
Read from the server's public OAuth metadata, without a token. Method. - Website
- https://ciromaciel.click/mcp/payments
- Registry
- active, updated 2026-11-04 · registry entry
- Changes
- 5 recorded, reachable in 3 of them. A row is added when the result, the tool count or the cost changes.
Compare this server with others.
More servers
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)
History
We add a row when the result changes. A server with no change keeps its last row.
| Probed | Result | Init | Tools | Claude | o200k |
|---|---|---|---|---|---|
| 2026-11-06 11:00 | needs auth | ||||
| 2026-11-05 11:03 | needs auth | ||||
| 2026-10-26 08:58 | needs your URL | ||||
| 2026-10-25 08:32 | needs auth | ||||
| 2026-10-23 09:38 | error |
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
- The server answers HTTP 401 to an unauthenticated initialize, so the probe cannot list its tools. That is correct for a private server. Some public servers answer initialize and tools/list without credentials and ask for auth on tool calls only; those get a token count here.
Fixed something? Probe it now, with the same steps as the daily run. This page updates with the next daily run.