Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Kythene

REMOTE · KYTHENE.COM

Your AI's work, reviewed by your team, remembered - shared artifacts with review, plus team memory.

Available components

0 this week 38 Trust /100

Last scanned (21 hours ago)

Scores higher than 28% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Memory and Knowledge

Trust breakdown (7 categories)

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
Transport & Reachability0
Schema Quality & AI Usability0
  • Schema blocked by authentication: the endpoint requires auth we don't have to read it. See how to fix → Unverified
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
  • Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Tool Safety0
  • Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Capabilities0
  • Capabilities blocked by authentication: the endpoint requires auth we don't have to read them. See how to fix → Unverified

Unverified: 6 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. Claim this server and supply a read-only token to verify it and lift the score.

What we tested

Checks we ran (5)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC

Checks we could not complete (6)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Transport in Transport & Reachability (scores 0 for this)Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http.
  • Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema blocked by authentication: the endpoint requires auth we don't have to read it.
  • Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
  • Tool coverage in Tool Coverage (scores 0 for this)Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.
  • Tool safety in Tool Safety (scores 0 for this)Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.
  • Capabilities in Capabilities (scores 0 for this)Capabilities blocked by authentication: the endpoint requires auth we don't have to read them.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 6 Nov 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
  • 28 Oct 26 +15
    • Endpoint reachability: not serving MCP → behind authorisation ▼ security
    • Transport: fail → unverified ▼ security
    • Authorization: unverified → pass ▲ security
    • HSTS header: fail → 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
  • 27 Oct 26 −15
    • Endpoint reachability: behind authorisation → not serving MCP ▼ security
    • Transport: unverified → fail ▼ security
    • Authorization: pass → unverified ▼ security
    • HSTS header: pass → fail ▼ security
    • Tool safety: Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list. security
    • Tool coverage: Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list. functional
    • Capabilities: Capabilities not yet verified: we couldn't read the endpoint's capabilities. functional
    • Schema quality: Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list. functional
  • 23 Oct 26 38
    • Endpoint reachability: reachable → behind authorisation ▼ security
    • Stability: pass → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Transport: pass → unverified ▼ security
    • Authorization: The endpoint enforces authorisation, advertised via RFC 9728 protected-resource metadata. security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
  • 22 Oct 26 0
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
  • 21 Oct 26 0
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
  • 20 Oct 26 0
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
  • 19 Oct 26 0
    • Stability: 0.97 → pass security
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
Diagnostics

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 21 Nov 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. DS published 19718 13 Verified
kythene.com. No DS 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 connection
HTTP status 401

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=31536000; includeSubDomains; preload
content-security-policy default-src 'self'; base-uri 'self'; object-src 'none'; frame-ancestors 'none'; script-src 'self' 'nonce-GQGm/wcS325nT9Cx06M1Cg=='; style-src 'self' 'unsafe-inline'; img-src 'self' data:; font-src 'self' data:; connect-src 'self'; frame-src 'self'
x-content-type-options nosniff
referrer-policy strict-origin-when-cross-origin
www-authenticate 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"

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 Auth required 401
http (plaintext) http://kythene.com/mcp/kythene HTTPS enforced 301 https://kythene.com/mcp/kythene
MCP tools · 48 exposed · ~11,880 tokens

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 →

Tool Tokens
share_collection ~235

Map a collection into another space you belong to (e.g. a shared client space), or remove that mapping. Requires membership of both spaces. space_id is the TARGET space (id or name from list_spaces); do not put it in `space`, which is the space you act from. Pass remove=true to unmap it from space_id instead (visibility from that space ends immediately; the origin space cannot be removed).

NameTypeReqDescription
collectionIdstringyescollection_id is the collection to map into the target space.
removeboolean–remove unmaps the collection from space_id instead of mapping it in. It cannot remove the collection's origin space (the domain enforces this).
spacestring–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.
spaceIdstringyesspace_id is the TARGET space to map the collection into - an id or a name from list_spaces. (Do NOT confuse it with `space` below, which is the space you are acting FROM.)

Structured output declared, but exposes no named fields.

No examples provided.

update_page ~343

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. The response's `url` is the page's link - hand that to a person, not the id.

NameTypeReqDescription
baseRevisionintegeryesbase_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…
bodystringyesbody is the new markdown, in full - this replaces the page, it does not append to it.
notestring–note is a short line about what changed - it shows on the page's history.
pagestringyespage is the page's id or its full path within the wiki.
spacestring–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.
titlestring–title optionally retitles the page.
wikistring–wiki is the wiki the page is in - its id or slug.
NameTypeReqDescription
urlstring–url is the page's canonical link - hand THAT to a person, never the bare id.

No examples provided.

Install

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

# add to Claude Code
claude mcp add --transport http com-kythene-kythene 'https://kythene.com/mcp/kythene'
Common questions

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 38 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,880 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 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the Kythene MCP server?

VerifyMCP ran 5 checks on Kythene, covering TLS certificate, Authorization, HTTPS, HSTS header and 1 more. 6 items could not be completed, a gap on our side rather than a finding about Kythene: Transport, Schema quality, Stability, Tool coverage and 2 more. 6 categories score 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.