io.github.fellanH/context-vault
Context Vault
Is the Context Vault MCP server down? No. It is up and needs auth (HTTP 401), probed 2026-11-14.
Hosted memory for AI agents: save what your agent learns and recall it in the next session.
needs auth probed 2026-11-14 · HTTP 401 · Bearer
Streamable HTTP error: Error POSTing to endpoint: {"jsonrpc":"2.0","error":{"code":-32000,"message":"missing authorization header"},"id":null}- Endpoint
- https://api.context-vault.com/mcp (streamable-http)
- Host
- api.context-vault.com
- Package
- The publisher's package npm:context-vault did not list its tools in the container: crashed on start, MCP error -32000: Connection closed [context-vault] Failed to load embedding model: Cannot find package '@huggingface/transformers' imported from /work/node_mod.
- Getting access
- OAuth with dynamic client registration. A client such as Claude Code, Cursor or npx mcpcost auth https://api.context-vault.com/mcp registers itself and opens the consent page; the publisher has nothing to set up for you.
Authorization server api.context-vault.com, PKCE S256, grants authorization_code, client_credentials, refresh_token.
Scopes vault:read vault:write.
Read from the server's public OAuth metadata, without a token. Method. - Repository
- https://github.com/fellanH/context-vault
- Website
- https://context-vault.com
- Registry
- active, updated 2026-11-12 · registry entry
Compare this server with others.
More servers
Servers that mention vault.
- Hyperresearch ai.hyperresearch/hyperresearch · needs auth
- JustOnce ai.justonce/memory · needs auth
- ai.smithery/Hint-Services-obsidian-github-mcp · not found
- ai.smithery/sunub-obsidian-mcp-server · not found
- Insuro au.com.insuro/insuro · alive
- Arca build.arca.mcp/arca-mcp-server · needs auth
- cc.accrue/mcp · alive
- AgentBrink com.agentbrink.www/mcp · needs auth
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.