Gnosem
REMOTE · GNOSEM.DEV · SCANNED AUG 3
Cross-vendor AI memory over MCP. One semantic store, readable and writeable from every MCP client.
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 →
Endpoint Security51
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS not yet verified: we couldn't determine whether a plaintext access path exists. 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 Usability60
- AI-judged instruction clarity (good).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 Management10
- Stability observed for 3 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
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · gnosem.dev
claude mcp add --transport http dev-gnosem-gnosem https://gnosem.dev/mcp
[mcp_servers.dev-gnosem-gnosem] url = "https://gnosem.dev/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"dev-gnosem-gnosem": {
"type": "remote",
"url": "https://gnosem.dev/mcp",
"enabled": true
}
}
} openclaw mcp add dev-gnosem-gnosem --url https://gnosem.dev/mcp --transport streamable-http
mcp_servers:
dev-gnosem-gnosem:
url: "https://gnosem.dev/mcp" {
"mcpServers": {
"dev-gnosem-gnosem": {
"type": "http",
"url": "https://gnosem.dev/mcp"
}
}
} 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.
- 3 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Aug 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
- 31 Jul 26 +37
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 18
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 3 Aug 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 | 29 Jul 2026 | 27 Oct 2026 | ECDSA 256 | ECDSA-SHA256 | 52b97691da13b2321310d75112d2f487 |
| SANs: gnosem.dev, www.gnosem.dev, *.www.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 |
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 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 |
| 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=() |
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.
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.