io.atalayahq/atalaya
Atalaya
Is the Atalaya MCP server down? No. It is up and needs auth (HTTP 401), probed 2026-10-29.
Work management with Spec-Driven Development: tasks, sprints and SDD approvals for coding agents.
needs auth probed 2026-11-15 · unchanged since 2026-10-29 · HTTP 401 · Bearer
Streamable HTTP error: Error POSTing to endpoint: {"jsonrpc":"2.0","error":{"code":-32001,"message":"No ha llegado ningún token. Envíalo como Authorization: Bea- Endpoint
- https://app.atalayahq.io/api/mcp (streamable-http)
- Host
- app.atalayahq.io
- 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://app.atalayahq.io/api/mcp --header "Authorization: Bearer …".
Read from the server's public OAuth metadata, without a token. Method. - Website
- https://atalayahq.io/mcp/
- Registry
- active, updated 2026-10-29 · registry entry
Compare this server with others.
More servers
Servers that mention atalaya.
- Atalaya · Los riesgos de tu ciudad io.lapoliza/riesgo · alive
- Atalaya · Los riesgos de tu ciudad city.atalaya/riesgos · alive
- Atalaya AI crawler check com.atalaya-ai/ai-crawler-check · 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.