Kythene
REMOTE · KYTHENE.COM · SCANNED OCT 1
Your AI's work, reviewed by your team, remembered - shared artifacts with review, plus team memory.
Available components
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 Security94
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability68
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 11637 tokens (~242/item across 48 items; 48 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management40
- Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 49 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the Kythene MCP server?
Kythene is a hosted endpoint at https://kythene.com/mcp/kythene, 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 · kythene.com
claude mcp add --transport http com-kythene-kythene 'https://kythene.com/mcp/kythene'
{
"mcpServers": {
"com-kythene-kythene": {
"url": "https://kythene.com/mcp/kythene"
}
}
} {
"servers": {
"com-kythene-kythene": {
"type": "http",
"url": "https://kythene.com/mcp/kythene"
}
}
} [mcp_servers.com-kythene-kythene] url = "https://kythene.com/mcp/kythene"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-kythene-kythene": {
"type": "remote",
"url": "https://kythene.com/mcp/kythene",
"enabled": true
}
}
} openclaw mcp add com-kythene-kythene --url 'https://kythene.com/mcp/kythene' --transport streamable-http
mcp_servers:
com-kythene-kythene:
url: "https://kythene.com/mcp/kythene" {
"McpServers": {
"com-kythene-kythene": {
"Transport": "http",
"Url": "https://kythene.com/mcp/kythene"
}
}
} assistant mcp add com-kythene-kythene -t streamable-http -u 'https://kythene.com/mcp/kythene'
{
"mcpServers": {
"com-kythene-kythene": {
"type": "http",
"url": "https://kythene.com/mcp/kythene"
}
}
} 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.
- 1 Oct 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 30 Sept 26 +1
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 29 Sept 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Sept 26 +1
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 26 Sept 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 25 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
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 1 Oct 2026 · Probed https://kythene.com/mcp/kythene
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=kythene.com | CN=WE1,O=Google Trust Services,C=US | 27 Sept 2026 | 26 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | a1d0f4e937a45dad13964535ebc68b64 |
| SANs: kythene.com, *.kythene.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of kythene.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| kythene.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer error="invalid_token", error_description="authentication required", resource_metadata="https://kythene.com/.well-known/oauth-protected-resource/mcp/kythene", scope="kythene:read kythene:write"
Bearer error="invalid_token", error_description="authentication required", resource_metadata="https://kythene.com/.well-known/oauth-protected-resource/mcp/kythene", scope="kythene:read kythene:write"| Header | Value |
|---|---|
| strict-transport-security | max-age=86400; includeSubDomains |
| content-security-policy | default-src 'self'; base-uri 'self'; object-src 'none'; frame-ancestors 'none'; script-src 'self' 'nonce-oDyPHjzLtExUkGoNSJh55g=='; style-src 'self' 'unsafe-inline'; img-src 'self' data:; font-src 'self' data:; connect-src 'self'; frame-src 'none' |
| x-content-type-options | nosniff |
| referrer-policy | strict-origin-when-cross-origin |
Protected resource metadata
| Document | https://kythene.com/.well-known/oauth-protected-resource/mcp/kythene |
|---|---|
| Retrieved | Yes |
| Resource | https://kythene.com/mcp/kythene |
| Authorisation server | https://kythene.com |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://kythene.com/mcp/kythene | Verified | 200 | |
| http (plaintext) | http://kythene.com/mcp/kythene | HTTPS enforced | 301 | https://kythene.com/mcp/kythene |
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 →
update_page Update page ~321
Replace a page's body with `body`, in FULL - this is not an append. `base_revision` is REQUIRED and must be the one get_page just gave you: if the page has moved on since, the write is refused and names the newer revision, so read it again and re-apply your change. That refusal is the point - two agents race on a page exactly as readily as two people. Writing does not publish: a live page keeps showing readers the published version until you publish the new one. `note` is a short line about what changed, shown on the page's history.
| Name | Type | Req | Description |
|---|---|---|---|
| baseRevision | integer | yes | base_revision is the revision you read before writing (from get_page). REQUIRED: if it is no longer current the write is refused, naming the newer one, so a second writer cannot silently overwrite… |
| body | string | yes | body is the new markdown, in full - this replaces the page, it does not append to it. |
| note | string | – | note is a short line about what changed - it shows on the page's history. |
| page | string | yes | page is the page's id or its full path within the wiki. |
| space | string | – | space optionally selects which of your spaces to act in (an id or name from list_spaces). Omit it when you belong to a single space. |
| title | string | – | title optionally retitles the page. |
| wiki | string | – | wiki is the wiki the page is in - its id or slug. |
Structured output declared, but exposes no named fields.
No examples provided.
What is the Kythene MCP server?
Kythene is an MCP server listed in the public MCP registry as com.kythene/kythene. Your AI's work, reviewed by your team, remembered - shared artifacts with review, plus team memory. This page covers its hosted endpoint (https://kythene.com/mcp/kythene).
Is the Kythene MCP server safe to use?
Kythene scores 83 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Kythene MCP server expose?
Kythene exposes 48 tools: remember, recall, forget, deprecate, link_memory, and 43 more. Their descriptions and schemas cost roughly 11,460 tokens of context every time the server is loaded.
Does the Kythene MCP server require authentication?
Yes. Kythene asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the Kythene MCP server still maintained?
Kythene is still listed as active in the MCP registry. We last reached this channel on 1 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.