ai.knowdrive/knowdrive-mcp
KnowDrive
Is the KnowDrive MCP server down? No. It is up and needs auth (HTTP 401), probed 2026-11-15.
Private, multimodal knowledge store for agents: hybrid search with cited, provenance-backed results.
needs auth probed 2026-11-15 · HTTP 401 · Bearer
Streamable HTTP error: Error POSTing to endpoint: Unauthorized
- Endpoint
- https://knowdrive.ai/api/v1/mcp (streamable-http)
- Host
- knowdrive.ai
- Package
- The publisher's package npm:@knowdrive/mcp did not list its tools in the container: needs network, MCP error -32000: Connection closed KnowDrive: couldn't reach https://knowdrive.ai/api/v1/mcp (fetch failed). Check your network connection and that KNOWDRIVE_B.
- Getting access
- OAuth with dynamic client registration. A client such as Claude Code, Cursor or npx mcpcost auth https://knowdrive.ai/api/v1/mcp registers itself and opens the consent page; the publisher has nothing to set up for you.
Authorization server knowdrive.ai, PKCE S256, grants authorization_code, client_credentials, password, refresh_token, urn:ietf:params:oauth:grant-type:token-exchange.
Scopes functions:/api/v1/mcp:read.
Read from the server's public OAuth metadata, without a token. Method. - Repository
- https://github.com/Recourse-Software-Inc/knowdrive-mcp
- Website
- https://knowdrive.ai
- Registry
- active, updated 2026-11-10 · registry entry
Compare this server with others.
More servers
Servers that mention multimodal or provenance.
- Aard ai.aard/aard · needs auth
- GroundTruth - Environmental Records ai.agentlookups/groundtruth · alive
- Decision Log ai.decisionlog/mcp · alive
- Duskly ai.duskly/duskly · alive
- ai.jawz/jawz · alive
- Manpage MCP ai.manpage/mcp · alive
- ai.partsgraph/catalog · server error
- ai.raisonn/connect · 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.