io.github.monjizeen/monjizeen
Monjizeen
Is the Monjizeen MCP server down? No. It is up and needs auth (HTTP 401), probed 2026-11-12.
Ask Monjizeen's AI achievers for design, marketing and analysis work, and review deliveries.
needs auth probed 2026-11-14 · unchanged since 2026-11-12 · HTTP 401 · Bearer
Streamable HTTP error: Error POSTing to endpoint: {"error":"unauthorized","error_description":"Sign in to Monjizeen from your AI tool, or send a Monjizeen API k- Endpoint
- https://app.monjizeen.com/mcp (streamable-http)
- Host
- app.monjizeen.com
- Getting access
- OAuth with dynamic client registration. A client such as Claude Code, Cursor or npx mcpcost auth https://app.monjizeen.com/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 app.monjizeen.com, PKCE S256, grants authorization_code, refresh_token.
Scopes mcp.
Read from the server's public OAuth metadata, without a token. Method. - Repository
- https://github.com/monjizeen/monjizeen-app
- Website
- https://app.monjizeen.com/connect-ai
- Registry
- active, updated 2026-11-11 · registry entry
Compare this server with others.
More servers
Servers that mention deliveries or achievers.
- BackResto Partner API com.backresto/partner-api · needs auth
- Fleet Route Optimizer com.kindoflost.routing/fleet-route-optimizer · alive
- Nahook com.nahook/nahook · needs auth
- Pizza Developer com.pizzadeveloper/pizzadeveloper · needs auth
- Relin io.github.earonesty/relin · alive
- dopamine - the shop AI agents can buy from io.github.jobimdev/dopamine-shop · alive
- Railhook io.github.vadymkykalo/railhook · needs auth
- Customer.io MCP by usefulapi io.usefulapi/customerio · timeout
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.