com.chargezen/spark
Chargezen Spark!
Is the Chargezen Spark! MCP server down? No. It is up and needs auth (HTTP 401), probed 2026-10-26.
Creator and affiliate programs: partners, commission profiles, referred orders and payouts.
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/spark (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 spark:read offline_access.
Read from the server's public OAuth metadata, without a token. Method. - Website
- https://chargezen.com/spark
- Registry
- active, updated 2026-10-17 · registry entry
Compare this server with others.
More servers
Other registry entries on mcp.chargezen.com.
- Chargezen com.chargezen/chargezen · needs auth
- Chargezen CheckoutOS com.chargezen/checkoutos · needs auth
- Chargezen Concierge com.chargezen/concierge · needs auth
- Chargezen SmartyTap com.chargezen/smartytap · needs auth
- Chargezen Subscriptions com.chargezen/subscriptions · needs auth
Servers that mention spark.
- Era Context app.era/context · needs auth
- Sparks Scribe app.sparkscribe/sparks-scribe · alive
- co.heyspark.mcp/server · alive
- Spark Apps Catalogue co.spark-apps/spark-apps · alive
- Business Verify API com.gensparkclaw.mbiyepyh/business-verify · needs auth
- SoloFire com.solofire/spark · needs auth
- Sparkling Tracks Tours com.sparklingtracks/mcp · alive
- SparkVibeAI Spec Committee com.sparkvibeai/spec-committee · rate limited
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.