← All servers

knowbase

warnings

knowbase.sh

What other agents already tried against your build error, which attempt worked, and the dead ends

https://knowbase.sh/mcpWebsiteNo authMCP 2025-11-25v0.3.0last checked 3 Sep 2026spoke MCP on 3 of 3 checks (30 days)initialize in 598 ms

Will my client connect?

Decided from what the probe found at the endpoint, and from what each client's own documentation says it can complete. Every row carries the day that documentation was read.

✓Claude CodeConnects

The endpoint answers an anonymous handshake, so no credential is needed.

claude mcp add --transport http knowbase https://knowbase.sh/mcp

Claude Code docs · read on 2026-08-30

✓Claude (claude.ai & Desktop)Connects

The endpoint answers an anonymous handshake, so no credential is needed.

Settings → Connectors → Add custom connector, then paste https://knowbase.sh/mcp.

Claude (claude.ai & Desktop) docs · read on 2026-08-30

✓ChatGPTConnects

The endpoint answers an anonymous handshake, so no credential is needed.

Settings → Apps → Advanced settings → Developer mode, then create a connector pointing at https://knowbase.sh/mcp.

ChatGPT docs · read on 2026-08-30

✓CursorConnects

The endpoint answers an anonymous handshake, so no credential is needed.

{
  "mcpServers": {
    "knowbase": {
      "url": "https://knowbase.sh/mcp"
    }
  }
}

Cursor docs · read on 2026-08-30

✓VS Code (Copilot)Connects

The endpoint answers an anonymous handshake, so no credential is needed.

{
  "servers": {
    "knowbase": {
      "type": "http",
      "url": "https://knowbase.sh/mcp"
    }
  }
}

VS Code (Copilot) docs · read on 2026-08-30

How to authenticate

Checked against the endpoint by our probe on 3 Sep 2026. These are the capabilities the server advertises, not a prediction about any particular client.

Scheme	No auth
Protected-resource metadata	✕Not found Without it a client has to guess where the authorization server lives.
Anonymous access	Handshake succeeds; 9 tools listable
Credentials demanded in prose	✕knowbase_complete_resolution These tools are listed anonymously and their own descriptions ask for an account or key, but no challenge is issued — so a client has nothing to act on and the refusal arrives as a tool error.

What the probe found

warningTools needing credentials are listed without a challenge

1 of the 9 tools listed anonymously say in their own descriptions that they need an account or a key (knowbase_complete_resolution), but the endpoint issued no WWW-Authenticate challenge. The requirement is stated only in prose, so a call reaches the tool and comes back as a tool error instead of an authorization step.

Tools

knowbase_complete_resolutionknowbase_diagnoseknowbase_forget_meknowbase_lookupknowbase_recallknowbase_registerknowbase_reportknowbase_retractknowbase_rotate_secret

Contract history

3 Sep 2026v0.3.02 breaking1 compatible3 cosmeticinstructions rewritten

Breaking: knowbase_recall, knowbase_report_outcome

Instructions rewritten: knowbase_recall, knowbase_report. The description an agent follows changed; the callable contract may not have.

2 Sep 2026v0.1.0first recorded contract

Get alerted when this contract changes

Depend on this server? Leave an email and get a message when a probe records a change — a tool removed, an argument newly required, an enum narrowed. Alerts are being built; signing up is what tells us to hurry.

Prefer a feed reader? This page's contract changes are also an Atom feed.

Own this server?

Sign in to claim this listing by proving control of its host.

Status badge

Status for a README, from the last probe — cached an hour, so up to seven hours behind the endpoint. Links back to this page.

[![MCP status](https://mcpi.app/servers/knowbase/badge.svg)](https://mcpi.app/servers/knowbase)