mcpcost

xyz.paymentscan/paymentscan

Paymentscan

Is the Paymentscan MCP server down? No. It is up and needs auth (HTTP 401), probed 2026-11-14.

Crypto card spend by program, issuer, chain, payment network, and currency. Free, Google sign-in.

needs auth probed 2026-11-15 · unchanged since 2026-11-14 · HTTP 401 · Bearer

Streamable HTTP error: Error POSTing to endpoint: {"error":"invalid_token","error_description":"No authorization provided"}
Endpoint
https://paymentscan.xyz/mcp (streamable-http)
Host
paymentscan.xyz
Getting access
OAuth with dynamic client registration. A client such as Claude Code, Cursor or npx mcpcost auth https://paymentscan.xyz/mcp registers itself and opens the consent page; the publisher has nothing to set up for you.
Authorization server paymentscan.xyz, PKCE S256, grants authorization_code, refresh_token.
Scopes data.read.
Read from the server's public OAuth metadata, without a token. Method.
Website
https://paymentscan.xyz/mcp
Registry
active, updated 2026-11-13 · registry entry

Compare this server with others.

More servers

Servers that mention currency or network.

Badge for the README

mcpcost: needs auth

The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.

Atom feed

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

Fixed something? Probe it now, with the same steps as the daily run. This page updates with the next daily run.