xyz.communitystudios/ceejay
CEEJAY
Is the CEEJAY MCP server down? No. It is up and needs auth (HTTP 401), probed 2026-11-13.
Let AI agents read your Discord community's analytics, members and tickets, and save drafts.
needs auth probed 2026-11-15 · unchanged since 2026-11-13 · HTTP 401 · Bearer
Streamable HTTP error: Error POSTing to endpoint: {"error":"Sign in to CEEJAY to connect this agent, or send a CEEJAY access token as an Authorization: Bearer h- Endpoint
- https://ceejay.communitystudios.xyz/api/mcp (streamable-http)
- Host
- ceejay.communitystudios.xyz
- Getting access
- OAuth with dynamic client registration. A client such as Claude Code, Cursor or npx mcpcost auth https://ceejay.communitystudios.xyz/api/mcp registers itself and opens the consent page; the publisher has nothing to set up for you. The publisher's guide to getting access.
Authorization server zljydzfxzahmblsfhvxl.supabase.co, PKCE S256, grants authorization_code, refresh_token.
Read from the server's public OAuth metadata, without a token. Method. - Website
- https://docs.communitystudios.xyz/docs/mcp
- Registry
- active, updated 2026-11-12 · registry entry
Compare this server with others.
More servers
Servers that mention ceejay or analytics or community.
- MorseByte x402 Edge Data Refinery & Quant Gateway io.github.Ceejaythenerd/morsebyte-x402-mcp · alive
- JustIdea Agency agency.justidea/justidea-agency · alive
- Alpic ai.alpic.mcp/alpic-mcp · needs auth
- Analytics Legends — SAP AI & Analytics MCP Server ai.analyticslegends/sap-analytics · alive
- AutoRFP.ai ai.autorfp/mcp · needs auth
- AwrAIter — Telegram channels ai.awraiter/telegram · needs auth
- Web Analytics ai.b77/web-analytics · needs auth
- BAMF.ai ai.bamf/bamf · not MCP
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.