com.chargezen/chargezen
Chargezen
Is the Chargezen MCP server down? No. It is up and needs auth (HTTP 401), probed 2026-10-26.
Concierge AI agents, Subscriptions, CheckoutOS, SmartyTap and Spark! on one revenue platform.
needs auth probed 2026-11-15 · unchanged since 2026-10-26 · HTTP 401 · Bearer
Streamable HTTP error: Error POSTing to endpoint: {"error":"invalid_token"}- Endpoint
- https://mcp.chargezen.com/mcp (streamable-http)
- Host
- mcp.chargezen.com
- 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 mcp.chargezen.com, PKCE S256, grants authorization_code, refresh_token.
Scopes workspace:read subscriptions:write subscriptions:create customers:create products:create selling_plans:create rewards:read rewards:write rewards:adjust rewards:redeem checkoutos:read checkoutos:write notifications:read notifications:write notifications:send conversations:read conversations:write media:read invoices:read invoices:send.
Read from the server's public OAuth metadata, without a token. Method. - Website
- https://chargezen.com/developers/mcp
- Registry
- active, updated 2026-10-17 · registry entry
Compare this server with others.
More servers
Other registry entries on mcp.chargezen.com.
- Chargezen CheckoutOS com.chargezen/checkoutos · needs auth
- Chargezen Concierge com.chargezen/concierge · needs auth
- Chargezen SmartyTap com.chargezen/smartytap · needs auth
- Chargezen Spark! com.chargezen/spark · needs auth
Servers that mention chargezen or subscriptions or checkoutos.
- Chargezen Subscriptions com.chargezen/subscriptions · needs auth
- Dynt ai.dynt.api/dynt · needs auth
- Banking Assistant (Metabind demo) ai.metabind/banking-assistant · alive
- Gro co.usegro/gro · needs auth
- Bunny com.bunny/bunny · needs your URL
- Checkout Page com.checkoutpage/checkout-page · needs auth
- Dhanvrit Finance com.dhanvrit/dhanvrit · needs auth
- GoCardless MCP Server com.gocardless/gc-mcp · needs auth
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.