Is the Gnosem MCP server down?

mcp-registry/dev.gnosem/gnosem · v0.1.0

Also listed as glama/gnosem/gnosem

healthy
Last checked 2026-10-20 08:37 UTC · handshake 508ms

As of 2026-10-20 08:37 UTC, the Gnosem MCP server is up with a Glimind reliability score of 97/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

uptime (30d checks)
100%
checks observed
3,895
outages (90d)
0
tools
6

Cross-vendor AI memory over MCP. One semantic store, readable and writeable from every MCP client.

Install Gnosem MCP server

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http gnosem-mcp-server https://gnosem.dev/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "gnosem-mcp-server": {
      "type": "http",
      "url": "https://gnosem.dev/mcp"
    }
  }
}

Third-party server, listed as discovered. Review its source before installing.

Agent-readiness: C (76/100)

C (76/100): 0 error(s), 3 warning(s) across 6 tool(s); ~1,767 tokens of tool definitions.
Scores higher than 13% of 15,394 MCP servers Glimind has audited.
Its tool list costs an agent ~1,767 tokens per session — lighter than 60% of servers.
76 → 76 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions78
Safety hints0
Token cost100
Client compatibility70
Protocol100
Reliability100
Stability100

What to fix (4)

6 of 6 tool(s) carry no readOnlyHint/destructiveHint annotations.

Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →

Tools: memory_forget, memory_list, memory_search, memory_supersede, memory_write and 1 more

2 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.

Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →

Tools: memory_write, memory_write_bulk

3 parameter(s) across 1 tool(s) have no description.

Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →

Tools: memory_supersede

No tool declares an outputSchema.

Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →

Auto-fix: 4 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 1 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fdev.gnosem%2Fgnosem/fixes

memory_list 1 change
{
  "name": "memory_list",
  "description": "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.",
  "inputSchema": {
    "type": "object",
    "properties": {
      "raw": {
        "type": "boolean",
        "description": "Return original prose instead of the compressed form. Default false."
      },
      "tags": {
        "type": "array",
        "items": {
          "type": "string"
        },
        "description": "Only return memories containing ALL of these tags (AND semantics)."
      },
      "limit": {
        "type": "integer",
        "description": "Max rows to return (1–200). Default 50."
      },
      "since": {
        "type": "integer",
        "description": "Only return memories created at or after this ms-epoch timestamp."
      },
      "until": {
        "type": "integer",
        "description": "Only return memories created strictly before this ms-epoch timestamp."
      },
      "cursor": {
        "type": "integer",
        "description": "Pagination cursor from a previous call's `cursor` field (ms epoch); returns rows older than this timestamp."
      },
      "session_id": {
        "type": "string",
        "description": "Only return memories with an exact session_id match."
      },
      "written_by": {
        "type": "string",
        "description": "Only return memories with an exact written_by match."
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}
memory_search 1 change
{
  "name": "memory_search",
  "description": "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), wr",
  "inputSchema": {
    "type": "object",
    "required": [
      "query"
    ],
    "properties": {
      "k": {
        "type": "integer",
        "description": "Max results (1–50). Default 10."
      },
      "raw": {
        "type": "boolean",
        "description": "Return original prose instead of the compressed form. Default false."
      },
      "mode": {
        "enum": [
          "semantic",
          "keyword",
          "hybrid"
        ],
        "type": "string",
        "description": "Retrieval mode. Default 'hybrid'."
      },
      "tags": {
        "type": "array",
        "items": {
          "type": "string"
        },
        "description": "Only return memories containing ALL of these tags (AND semantics)."
      },
      "query": {
        "type": "string",
        "description": "Search query. Interpreted as natural language for semantic mode and as FTS5-safe text for keyword mode."
      },
      "since": {
        "type": "integer",
        "description": "Only return memories created at or after this ms-epoch timestamp."
      },
      "until": {
        "type": "integer",
        "description": "Only return memories created strictly before this ms-epoch timestamp."
      },
      "session_id": {
        "type": "string",
        "description": "Only return memories with an exact session_id match."
      },
      "written_by": {
        "type": "string",
        "description": "Only return memories with an exact written_by match (e.g. 'claude-code')."
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}
memory_write 1 change
{
  "name": "memory_write",
  "description": "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 w",
  "inputSchema": {
    "type": "object",
    "required": [
      "content"
    ],
    "properties": {
      "tags": {
        "type": "array",
        "items": {
          "type": "string"
        },
        "description": "Optional short labels for filtering (e.g. ['preference','stack'])."
      },
      "force": {
        "type": "boolean",
        "description": "Bypass semantic dedup and write anyway. Default false."
      },
      "content": {
        "type": "string",
        "description": "The fact or note to remember. Plain text, max 8000 characters."
      },
      "session_id": {
        "type": "string",
        "description": "Opaque identifier grouping related writes from the same conversation."
      },
      "written_by": {
        "type": "string",
        "description": "Identifier of the model / client writing this (e.g. 'claude-code', 'gpt-5', 'kimi-k2', 'manual')."
      },
      "no_optimize": {
        "type": "boolean",
        "description": "Skip AI compression of long content. Default false."
      }
    }
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  }
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/dev.gnosem/gnosem"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/dev.gnosem/gnosem"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

Markdown
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fdev.gnosem%2Fgnosem.svg)](https://glimind.com/server/mcp-registry%2Fdev.gnosem%2Fgnosem?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fdev.gnosem%2Fgnosem?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fdev.gnosem%2Fgnosem.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fdev.gnosem%2Fgnosem.svg
   :target: https://glimind.com/server/mcp-registry%2Fdev.gnosem%2Fgnosem?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:02e4064fe68c12a9…, first seen 2026-10-17, included at leaf 5301 of 31,830. Version history · verify what your client received.

Tools (6)

Compare: most reliable database servers · most reliable knowledge servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Gnosem MCP server down right now?

As of 2026-10-20 08:37 UTC, the Gnosem MCP server is up with a Glimind reliability score of 97/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

How many tools does Gnosem MCP server provide?

Gnosem MCP server advertises 6 tools, including memory_forget, memory_list, memory_search, memory_supersede, memory_write.

How do I install Gnosem MCP server?

Point your MCP client at this streamable-http endpoint: https://gnosem.dev/mcp

Is the Gnosem MCP server safe to connect to an AI agent?

Glimind scanned all 6 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Gnosem MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.

Feedback
Help us improve