Gnosem
REMOTE · GNOSEM.DEV
Cross-vendor AI memory over MCP. One semantic store, readable and writeable from every MCP client.
Available components
Last scanned (18 hours ago)
Scores higher than 93% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Memory and Knowledge
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 Security83
- 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 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
- 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 Usability71
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1177 tokens (~196/item across 6 items; 6 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 Management97
- Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage97
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 90% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
- 4 Nov 26 0
- Stability: pass → 0.97 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
- 25 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
- 30 Aug 26 0
- Stability: 0.97 → pass security
- 26 Aug 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
- 11 Aug 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
- 1 Aug 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
- 31 Jul 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
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 4 Nov 2026 · Probed https://gnosem.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=gnosem.dev | CN=WE1,O=Google Trust Services,C=US | 26 Sept 2026 | 26 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 6b08a00f1328f3b20ebc6dbf80bba0d0 |
| SANs: gnosem.dev, *.gnosem.dev | ||||||
| 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 gnosem.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| gnosem.dev. | 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 resource_metadata="https://gnosem.dev/.well-known/oauth-protected-resource"
Bearer resource_metadata="https://gnosem.dev/.well-known/oauth-protected-resource"| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | accelerometer=(), camera=(), geolocation=(), gyroscope=(), microphone=(), payment=(), usb=() |
Protected resource metadata
| Document | https://gnosem.dev/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | Yes |
| Resource | https://gnosem.dev |
| Authorisation server | https://gnosem.dev |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://gnosem.dev/mcp | Verified | 200 | |
| http (plaintext) | http://gnosem.dev/mcp | 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 →
memory_forget ~47
Soft-delete a memory by id. The row is retained for audit but excluded from search/list and removed from the vector index.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | UUID of the memory to forget. |
No output schema declared.
No examples provided.
memory_list ~222
List the user's most recent memories in reverse chronological order. Use for browsing or catching up on what the user's other model sessions have written recently. Same content/content_raw shape as memory_search. Optional filters (tags, written_by, session_id, since, until) narrow the listing at the SQL level.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | integer | – | Pagination cursor from a previous call's `cursor` field (ms epoch); returns rows older than this timestamp. |
| limit | integer | – | Max rows to return (1–200). Default 50. |
| raw | boolean | – | Return original prose instead of the compressed form. Default false. |
| session_id | string | – | Only return memories with an exact session_id match. |
| since | integer | – | Only return memories created at or after this ms-epoch timestamp. |
| tags | array | – | Only return memories containing ALL of these tags (AND semantics). |
| until | integer | – | Only return memories created strictly before this ms-epoch timestamp. |
| written_by | string | – | Only return memories with an exact written_by match. |
No output schema declared.
No examples provided.
memory_search ~311
Search the user's memories. Default mode is 'hybrid': blends semantic (cosine over Vectorize) and keyword (BM25 over SQLite FTS5) hits via Reciprocal Rank Fusion (k=60). Semantic catches paraphrases; keyword catches exact-string hits (IDs, dates, code snippets). Pass mode:'semantic' or mode:'keyword' to run just one. Content defaults to the LLM-optimized (compressed) form when available (raw:true to invert). Excludes forgotten + superseded. Optional filters narrow after retrieval: tags (AND), written_by, session_id, and/or since/until (ms epoch).
| Name | Type | Req | Description |
|---|---|---|---|
| k | integer | – | Max results (1–50). Default 10. |
| mode | string | – | Retrieval mode. Default 'hybrid'. |
| query | string | yes | Search query. Interpreted as natural language for semantic mode and as FTS5-safe text for keyword mode. |
| raw | boolean | – | Return original prose instead of the compressed form. Default false. |
| session_id | string | – | Only return memories with an exact session_id match. |
| since | integer | – | Only return memories created at or after this ms-epoch timestamp. |
| tags | array | – | Only return memories containing ALL of these tags (AND semantics). |
| until | integer | – | Only return memories created strictly before this ms-epoch timestamp. |
| written_by | string | – | Only return memories with an exact written_by match (e.g. 'claude-code'). |
No output schema declared.
No examples provided.
memory_supersede ~106
Replace a stale memory with a corrected one. The old row is marked superseded and excluded from future reads; the new row becomes the current version. Use for corrections; use memory_forget for pure deletions.
| Name | Type | Req | Description |
|---|---|---|---|
| new_content | string | yes | New content that supersedes the old memory. |
| old_id | string | yes | UUID of the memory to replace. |
| session_id | string | – | – |
| tags | array | – | – |
| written_by | string | – | – |
No output schema declared.
No examples provided.
memory_write ~330
Save a fact, preference, decision, or note to the user's cross-model memory. Any MCP client can read this back later. Include written_by (e.g. 'claude-code', 'gpt-5', 'kimi-k2') for provenance and session_id to group related writes. Long content (>400 chars) is automatically compressed on write to a structured-facts form optimized for LLM reading — the raw text is preserved. Pass no_optimize:true to skip. Writes are deduped by default: (1) SHA-256 of trim(content) short-circuits byte-identical writes with { id, exact_duplicate:true } for free (no embed call); (2) failing that, semantic dedup returns { id, deduped:true, matched_score } when cosine ≥ 0.85. Pass force:true to bypass both, or use memory_supersede to explicitly correct a prior memory.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | The fact or note to remember. Plain text, max 8000 characters. |
| force | boolean | – | Bypass semantic dedup and write anyway. Default false. |
| no_optimize | boolean | – | Skip AI compression of long content. Default false. |
| session_id | string | – | Opaque identifier grouping related writes from the same conversation. |
| tags | array | – | Optional short labels for filtering (e.g. ['preference','stack']). |
| written_by | string | – | Identifier of the model / client writing this (e.g. 'claude-code', 'gpt-5', 'kimi-k2', 'manual'). |
No output schema declared.
No examples provided.
memory_write_bulk ~161
Write up to 50 memories in a single call. Each entry runs the same path as memory_write (semantic dedup by default; pass force:true per-entry to skip). Embeddings + optimizations run in parallel; D1 inserts are batched. Returns { results: [...] } with one entry per input in the same order — each is { id, created_at, optimized? } on success, { id, created_at, deduped, matched_score } on dedup, or { error } on failure. Free-tier limits apply to the sum: if adding N would exceed 200, the first (200 - existing) succeed and the rest return an error.
| Name | Type | Req | Description |
|---|---|---|---|
| memories | array | yes | Array of memory-write entries (1–50). |
No output schema declared.
No examples provided.
How do I install the Gnosem MCP server?
Gnosem is a hosted endpoint at https://gnosem.dev/mcp, 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 · gnosem.dev
claude mcp add --transport http dev-gnosem-gnosem 'https://gnosem.dev/mcp'
What is the Gnosem MCP server?
Gnosem is an MCP server listed in the public MCP registry as dev.gnosem/gnosem. Cross-vendor AI memory over MCP. One semantic store, readable and writeable from every MCP client. This page covers its hosted endpoint (https://gnosem.dev/mcp).
Is the Gnosem MCP server safe to use?
Gnosem scores 86 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 Gnosem MCP server expose?
Gnosem exposes 6 tools: memory_write, memory_search, memory_list, memory_forget, memory_supersede, memory_write_bulk. Their descriptions and schemas cost roughly 1,177 tokens of context every time the server is loaded.
Does the Gnosem MCP server require authentication?
Yes. Gnosem 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 Gnosem MCP server still maintained?
Gnosem is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.