ai.kojen/kojen
Kojen
Is the Kojen MCP server down? No. It is up and needs auth (HTTP 401), probed 2026-11-09.
Train, evaluate, red-team and deploy AI agents: prompt tuning, LLM-judged evals, katas.
needs auth probed 2026-11-15 · unchanged since 2026-11-09 · HTTP 401 · Bearer
Streamable HTTP error: Error POSTing to endpoint: {"error":"invalid_token","error_description":"No authorization provided"}- Endpoint
- https://kojen.ai/api/mcp (streamable-http)
- Host
- kojen.ai
- Getting access
- A key or token from the publisher, sent in the Authorization header (Bearer). The server publishes no OAuth metadata. Store the key once: npx mcpcost auth https://kojen.ai/api/mcp --header "Authorization: Bearer …".
Read from the server's public OAuth metadata, without a token. Method. - Website
- https://kojen.ai/developers
- Registry
- active, updated 2026-11-08 · registry entry
Compare this server with others.
More servers
Servers that mention evaluate or deploy.
- Alpic ai.alpic.mcp/alpic-mcp · needs auth
- AppDeploy ai.appdeploy/deploy-app · needs auth
- Auxen ai.auxen/auxen · needs auth
- BorealHost ai.borealhost/mcp · alive
- Orbit ai.buildwithorbit/orbit · alive
- Alchemist Cloud Tickets ai.chipp/alchemist-cloud-tickets · needs auth
- ai.canaryusers/canaryusers · alive
- Cerebrium Docs ai.cerebrium/docs · alive
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.