Khwan
REMOTE · MCP.KHWAN.AI · 2 COMPONENTS · SCANNED SEP 20
Durable AI memory: recall distilled facts in a later session or subagent, and remember new ones.
Available components
Degraded
One or more channels of this server are currently unreachable; their trust score is decaying and will reach 0 if they stay down.
Recent critical change
TLS certificate (16 Sept 2026). See the changelog before you install this server.
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security11
- TLS check failed: the certificate doesn't match the endpoint's hostname. See how to fix → View diagnostics → Fail
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS not yet verified: we couldn't read the response headers to check for it. View diagnostics → Unverified
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but the TLS certificate failed verification. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
How do I install the Khwan MCP server?
Khwan is a hosted endpoint at https://mcp.khwan.ai/mcp/%7Bcore%7D/%7Buser%7D, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.khwan.ai
claude mcp add --transport http ai-khwan-khwan-mcp 'https://mcp.khwan.ai/mcp/%7Bcore%7D/%7Buser%7D'
{
"mcpServers": {
"ai-khwan-khwan-mcp": {
"url": "https://mcp.khwan.ai/mcp/%7Bcore%7D/%7Buser%7D"
}
}
} {
"servers": {
"ai-khwan-khwan-mcp": {
"type": "http",
"url": "https://mcp.khwan.ai/mcp/%7Bcore%7D/%7Buser%7D"
}
}
} [mcp_servers.ai-khwan-khwan-mcp] url = "https://mcp.khwan.ai/mcp/%7Bcore%7D/%7Buser%7D"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ai-khwan-khwan-mcp": {
"type": "remote",
"url": "https://mcp.khwan.ai/mcp/%7Bcore%7D/%7Buser%7D",
"enabled": true
}
}
} openclaw mcp add ai-khwan-khwan-mcp --url 'https://mcp.khwan.ai/mcp/%7Bcore%7D/%7Buser%7D' --transport streamable-http
mcp_servers:
ai-khwan-khwan-mcp:
url: "https://mcp.khwan.ai/mcp/%7Bcore%7D/%7Buser%7D" {
"McpServers": {
"ai-khwan-khwan-mcp": {
"Transport": "http",
"Url": "https://mcp.khwan.ai/mcp/%7Bcore%7D/%7Buser%7D"
}
}
} assistant mcp add ai-khwan-khwan-mcp -t streamable-http -u 'https://mcp.khwan.ai/mcp/%7Bcore%7D/%7Buser%7D'
{
"mcpServers": {
"ai-khwan-khwan-mcp": {
"type": "http",
"url": "https://mcp.khwan.ai/mcp/%7Bcore%7D/%7Buser%7D"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 19 Sept 26 −8
The score moved with no change recorded against any check. We would rather say so than guess.
- 18 Sept 26 −7
The score moved with no change recorded against any check. We would rather say so than guess.
- 16 Sept 26 0
- TLS certificate: pass → fail ▼ critical
- Score status: scored → failed ▼ critical
- Transport: unverified → fail ▼ security
- Authorization: pass → unverified ▼ security
- HSTS header: fail → unverified ▼ security
- Tool safety: Tool safety not yet verified: we couldn't read the endpoint's tools. security
- Schema quality: Schema not yet verified: we couldn't read the endpoint's schema. functional
- Capabilities: Capabilities not yet verified: we couldn't read the endpoint's capabilities. functional
- Tool coverage: Tool coverage not yet verified: we couldn't read the endpoint's tools. functional
- 8 Sept 26 +14
- Transport: fail → unverified ▼ security
- Authorization: unverified → pass ▲ security
- Tool safety: Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools. security
- Tool coverage: Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools. functional
- Schema quality: Schema blocked by authentication: the endpoint requires auth we don't have to read it. functional
- Capabilities: Capabilities blocked by authentication: the endpoint requires auth we don't have to read them. functional
- 5 Sept 26 −14
- Transport: unverified → fail ▼ security
- Authorization: pass → unverified ▼ security
- Tool safety: Tool safety not yet verified: we couldn't read the endpoint's tools. security
- Schema quality: Schema not yet verified: we couldn't read the endpoint's schema. functional
- Tool coverage: Tool coverage not yet verified: we couldn't read the endpoint's tools. functional
- Capabilities: Capabilities not yet verified: we couldn't read the endpoint's capabilities. functional
- 26 Aug 26 37
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Probed https://mcp.khwan.ai/mcp/{core}/{user}
TLS invalid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
Chain error: hostname_mismatch
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.up.railway.app | CN=YE1,O=Let's Encrypt,C=US | 29 Jul 2026 | 27 Oct 2026 | ECDSA 256 | ECDSA-SHA384 | 6da79bb561da3efeb0e751ca21abd3999fe |
| SANs: *.up.railway.app, up.railway.app | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.khwan.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| khwan.ai. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.khwan.ai/mcp/{core}/{user} | TLS failed | ||
| http (plaintext) | http://mcp.khwan.ai/mcp/%7Bcore%7D/%7Buser%7D | HTTPS enforced | 301 | https://mcp.khwan.ai/mcp/%7Bcore%7D/%7Buser%7D |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
No tool schema has been captured from this endpoint yet.
What is the Khwan MCP server?
Khwan is an MCP server listed in the public MCP registry as ai.khwan/khwan-mcp. Durable AI memory: recall distilled facts in a later session or subagent, and remember new ones. This page covers its hosted endpoint (https://mcp.khwan.ai/mcp/{core}/{user}).
Does the Khwan MCP server require authentication?
Its publisher declares no required credentials for Khwan. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the Khwan MCP server still maintained?
Khwan is still listed in the MCP registry, but we have not been able to reach this channel for several days and its score is decaying. We last reached this channel on 15 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.