pro.keystone-core/keystone
Keystone
Is the Keystone MCP server down? No. It is up and needs auth (HTTP 401), probed 2026-11-11.
C4 architecture model of your system, built from code by your AI and read back as focused context.
needs auth probed 2026-11-14 · unchanged since 2026-11-11 · HTTP 401 · Bearer
Streamable HTTP error: Error POSTing to endpoint: {"timestamp":"2026-11-11T11:52:04.827Z","status":401,"error":"Unauthorized","path":"/mcp"}- Endpoint
- https://keystone-core.pro/mcp (streamable-http)
- Host
- keystone-core.pro
- 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://keystone-core.pro/mcp --header "Authorization: Bearer …".
Read from the server's public OAuth metadata, without a token. Method. - Repository
- https://github.com/runafterasun/keystone-core
- Website
- https://keystone-core.pro
- Registry
- active, updated 2026-11-10 · registry entry
Compare this server with others.
More servers
Servers that mention keystone.
- io.github.CSOAI-ORG/keystone-verify-proxy-mcp · install failed
- Keystone io.github.Srikarmk/keystone · alive
- OpenStack io.github.oomchiller/openstack-mcp-server · crashed on start
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.