Is the Usememra Memra MCP server down?

mcp-registry/com.usememra/memra · v4.7.1

As of 2026-10-24 23:50 UTC, the Usememra Memra MCP server is down with a Glimind reliability score of 38/100 (grade F). Over the last 30 days it answered 98.1% of Glimind's liveness checks. It had 66 outages in 90 days, with a median recovery of 8 minutes.

Persistent memory for AI agents. EU-hosted, privacy-first, hybrid recall, contradiction detection.

Point your MCP client at this streamable-http endpoint: https://usememra.com/mcp

Agent-readiness: C (76/100)

What to fix (5)

Auto-fix: 2 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%2Fcom.usememra%2Fmemra/fixes

{
  "name": "memra_get",
  "description": "Get a single memory by ID with full content. Use when you need the complete text of a memory (search results are truncated).",
  "inputSchema": {
    "type": "object",
    "required": [
      "memory_id"
    ],
    "properties": {
      "memory_id": {
        "type": "string",
        "description": "The memory ID to retrieve"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}

{
  "name": "memra_list",
  "description": "List memories in Memra for a namespace. Returns paginated results with filtering options.",
  "inputSchema": {
    "type": "object",
    "required": [
      "namespace"
    ],
    "properties": {
      "tags": {
        "type": "array",
        "items": {
          "type": "string"
        },
        "description": "Filter by tags"
      },
      "type": {
        "enum": [
          "fact",
          "event",
          "pattern",
          "working",
          "decision",
          "preference",
          "context",
          "entity",
          "reference"
        ],
        "type": "string",
        "description": "Filter by memory type"
      },
      "limit": {
        "type": "integer",
        "default": 20,
        "maximum": 100,
        "minimum": 1,
        "description": "Max results"
      },
      "offset": {
        "type": "integer",
        "default": 0,
        "description": "Pagination offset"
      },
      "namespace": {
        "type": "string",
        "description": "Tenant namespace"
      },
      "project_id": {
        "type": "string",
        "description": "Filter by project ID"
      },
      "min_importance": {
        "type": "integer",
        "maximum": 10,
        "minimum": 1,
        "description": "Minimum importance"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}

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/com.usememra/memra"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/com.usememra/memra"}) over MCP.

Passed

• Every tool has a well-formed, typed input schema.
• No tool-poisoning patterns (hidden characters, instruction overrides, concealment, secret access, tool shadowing).
• Compact tool list (~2,078 tokens).
• Tool names are unique and portable across clients.
• No breaking contract changes in 30 days.

Largest tool definitions

• memra_remember ~559 tokens
• memra_recall ~524 tokens
• memra_supersede ~269 tokens
• memra_bootstrap ~244 tokens
• memra_list ~233 tokens

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:

[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.usememra%2Fmemra.svg)](https://glimind.com/server/mcp-registry%2Fcom.usememra%2Fmemra?ref=badge)

<a href="https://glimind.com/server/mcp-registry%2Fcom.usememra%2Fmemra?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.usememra%2Fmemra.svg" alt="MCP agent-readiness"></a>

.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.usememra%2Fmemra.svg
   :target: https://glimind.com/server/mcp-registry%2Fcom.usememra%2Fmemra?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:62dc7627815afc82…, first seen 2026-10-17, included at leaf 4200 of 74,339. Version history · verify what your client received.

Working alternatives

• load_context ai.ctxstore/ctxstore-mcp
• initialize_context io.github.SynapseLayer/synapse-layer
• recall io.github.kapoost/humanmcp
• get_context_pack com.dayze/life-context

Tools (7)

• memra_bootstrap
• memra_get
• memra_history
• memra_list
• memra_recall
• memra_remember
• memra_supersede

Compare: most reliable knowledge servers

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

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

FAQ

Is the Usememra Memra MCP server down right now?

As of 2026-10-24 23:50 UTC, the Usememra Memra MCP server is down with a Glimind reliability score of 38/100 (grade F). Over the last 30 days it answered 98.1% of Glimind's liveness checks. It had 66 outages in 90 days, with a median recovery of 8 minutes.

How many tools does Usememra Memra MCP server provide?

Usememra Memra MCP server advertises 7 tools, including memra_bootstrap, memra_get, memra_history, memra_list, memra_recall.

How do I install Usememra Memra MCP server?

Point your MCP client at this streamable-http endpoint: https://usememra.com/mcp

Is the Usememra Memra MCP server safe to connect to an AI agent?

Glimind scanned all 7 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 Usememra Memra 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.