Kaneme — Your writing identity, measured and portable
REMOTE · KANEME.COM · 2 COMPONENTS
Build a voice from your own texts, measure whether a text still sounds like you, then write in it.
Available components
Last scanned (15 hours ago)
Scores higher than 85% of remote servers
Reachable. Last reached 5 Nov 2026.
Category AI and Machine Learning
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 Security69
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- 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
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability67
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 682 tokens (~341/item across 2 items; 2 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 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
Checks we ran (12)
- TLS certificate
- Authorization
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
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.
- HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
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 →
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.
- 3 Nov 26 +7
- Stability: fail → pass ▲ security
- 27 Oct 26 +4
No change was recorded against any check on this day. Stability & Change Management went from 25 to 50.
- 14 Oct 26 0
- Server version: 5.3.0 → 5.4.0 functional
- 12 Oct 26 0
- Server version: 5.2.0 → 5.3.0 functional
- 10 Oct 26 +1
- Schema quality: 430 → 341 ▲ functional
- 6 Oct 26 0
- Server version: 5.0.0 → 5.1.0 functional
- 4 Oct 26 70
- A breaking change shipped without a version bump: still 1.7.0 ▼ security
- Tool “verify_certificate” was removed ▼ security
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: 349 → 430 ▼ functional
- MCP protocol: Implements a current MCP spec version (2026-07-28). functional
- MCP protocol version: 2025-11-25 → 2026-07-28 functional
- Server version: 1.7.0 → 5.0.0 functional
- 3 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “measure_authorship” rewrote its description, which is the text the model reads security
- Tool “verify_certificate” rewrote its description, which is the text the model reads security
- Schema quality: 304 → 349 ▼ functional
- Server version: 1.6.0 → 1.7.0 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 5 Nov 2026 · Probed https://kaneme.com/api/mcp/public
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=kaneme.com | CN=WE1,O=Google Trust Services,C=US | 9 Oct 2026 | 7 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 7a22175ee8b809111371494ae765be94 |
| SANs: kaneme.com, *.kaneme.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 kaneme.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| kaneme.com. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline' https://challenges.cloudflare.com https://accounts.google.com/gsi/client https://static.cloudflareinsights.com https://js.stripe.com https://apis.google.com; style-src 'self' 'unsafe-inline' https://accounts.google.com/gsi/style; font-src 'self' data:; img-src 'self' data: blob: https://vzktjydyprgdswouvanf.supabase.co https://www.google.com https://lh3.googleusercontent.com https://*.stripe.com https://img.logo.dev; connect-src 'self' https://vzktjydyprgdswouvanf.supabase.co wss://vzktjydyprgdswouvanf.supabase.co https://cloudflareinsights.com https://*.ingest.sentry.io https://*.ingest.de.sentry.io https://challenges.cloudflare.com https://accounts.google.com/gsi/ https://api.stripe.com https://www.googleapis.com https://content.googleapis.com; frame-src 'self' https://www.youtube.com https://www.youtube-nocookie.com https://challenges.cloudflare.com https://accounts.google.com/gsi/ https://js.stripe.com https://checkout.stripe.com https://hooks.stripe.c |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://kaneme.com/api/mcp/public | Verified | 200 | |
| http (plaintext) | http://kaneme.com/api/mcp/public | Inconclusive | 405 |
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 →
measure_authorship Trial measurement, no account ~221
Measures whether a text is by the SAME HAND as three reference texts pasted in the call. No account, no credits, nothing stored. Exactly 3 references of 100+ words each, in DIFFERENT registers, and a text of 50+ words (150 to leave low confidence). Returns a calibrated PROBABILITY, its label and four stylometric dimensions (not a breakdown of the probability). `probability: null` with `unavailable` is a measured abstention; only `embedding_layer` is an outage on our side. Not verify_authorship, which uses the account’s saved voice. For that, a Kaneme account at https://kaneme.com and the authenticated MCP connection.
| Name | Type | Req | Description |
|---|---|---|---|
| question | string | – | human = this person vs an AI (default) · author = this person vs another human. |
| samples | array | yes | Exactly 3 texts by the person, 100+ words each, different registers. |
| text | string | yes | Text to attribute (50+ words), not taken from the references (self_overlap). |
No output schema declared.
No examples provided.
read_observatory_signals Observatory reading (free) ~229
Reads a text with the Observatoire method (frozen copy, `methodVersion` returned): passages to reread, each with its criterion (G01 generic phrasing, S01 announced conclusion, V01 claim without visible evidence, R01 near-repeated vocabulary, S02 repeated opening, D01 long sentence), UTF-16 positions, the quoted passage and editorial advice. No account, no credits, nothing stored. It is NOT an AI detector, NOT a proof of authorship and has NO score: never turn the number of passages into a verdict, and never merge it with a Kaneme measurement. Labels and advice are in French: relay them in the user’s language. Language is detected when omitted; English rules are experimental. To rewrite the text in the user’s own voice, use improve_in_voice (account required).
| Name | Type | Req | Description |
|---|---|---|---|
| documentType | string | – | Kind of text; tunes the advice (default: general). |
| language | string | – | Text language (detected when omitted). |
| text | string | yes | Text to read (12,000 characters max). |
No output schema declared.
No examples provided.
How do I install the Kaneme — Your writing identity, measured and portable MCP server?
Kaneme — Your writing identity, measured and portable is a hosted endpoint at https://kaneme.com/api/mcp/public, 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 · kaneme.com
claude mcp add --transport http com-kaneme-kaneme 'https://kaneme.com/api/mcp/public'
What is the Kaneme — Your writing identity, measured and portable MCP server?
Kaneme — Your writing identity, measured and portable is an MCP server listed in the public MCP registry as com.kaneme/kaneme. Build a voice from your own texts, measure whether a text still sounds like you, then write in it. This page covers its hosted endpoint (https://kaneme.com/api/mcp/public).
Is the Kaneme — Your writing identity, measured and portable MCP server safe to use?
Kaneme — Your writing identity, measured and portable scores 82 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 Kaneme — Your writing identity, measured and portable MCP server expose?
Kaneme — Your writing identity, measured and portable exposes 2 tools: read_observatory_signals, measure_authorship. Their descriptions and schemas cost roughly 450 tokens of context every time the server is loaded.
Does the Kaneme — Your writing identity, measured and portable MCP server require authentication?
No. We connected to Kaneme — Your writing identity, measured and portable without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Kaneme — Your writing identity, measured and portable MCP server still maintained?
Kaneme — Your writing identity, measured and portable is still listed as active in the MCP registry. We last reached this channel on 5 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 Kaneme — Your writing identity, measured and portable MCP server?
VerifyMCP ran 12 checks on Kaneme — Your writing identity, measured and portable, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Kaneme — Your writing identity, measured and portable: HTTPS. 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.