Is the Borisinc Memory MCP server down?

mcp-registry/com.borisinc/memory · v1.30.0

degraded
Last checked 2026-10-27 06:18 UTC · handshake 972ms

As of 2026-10-27 06:18 UTC, the Borisinc Memory MCP server is degraded with a Glimind reliability score of 56/100 (grade D). Over the last 30 days it answered 92.2% of Glimind's liveness checks. It had 152 outages in 90 days, with a median recovery of 3 minutes.

uptime (30d checks)
92.2%
checks observed
3,820
outages (90d)
152
tools
8

Persistent agent memory paid per call via x402 USDC. Your wallet is your private memory namespace.

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

Agent-readiness: D (67/100)

D (67/100): 1 error(s), 3 warning(s) across 8 tool(s); ~1,125 tokens of tool definitions.
Scores higher than 1% of 15,781 MCP servers Glimind has audited.
Its tool list costs an agent ~1,125 tokens per session — lighter than 75% of servers.
68 → 67 since 2026-10-18
no tool-poisoning patterns
Schemas100
Descriptions55
Safety hints0
Token cost100
Client compatibility70
Protocol100
Reliability50
Stability100

What to fix (5)

Reachable 92.2% of the time over the last 30 days; median recovery 3 min.

Agents fail over to an alternative the first time a call fails. Add health checks and restart-on-failure, and avoid cold starts on serverless hosts.

8 of 8 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_export, memory_forget, memory_import, memory_search, memory_search_free and 3 more

4 parameter(s) across 4 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_search, memory_search_free, memory_write, memory_write_free

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_free

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: 7 corrected tool definitions

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

memory_export 1 change
{
  "name": "memory_export",
  "description": "Export memories in YOUR payer-wallet namespace (up to 1000/call, newest first; use offset to page through namespaces >1000). Your data is yours. Includes superseded_by so history is exportable. Paid: $0.01 via x402.",
  "inputSchema": {
    "type": "object",
    "properties": {
      "offset": {
        "type": "integer",
        "description": "row offset for paging past the first 1000 (default 0)"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}
memory_import 1 change
{
  "name": "memory_import",
  "description": "Bulk-write memories into YOUR namespace (max 200/call, content <=8k chars each). Accepts the exact shape memory_export emits, so a whole namespace can move in with one paid call. Embeds best-effort; missing embeddings are backfilled hourly. Paid: $0.01 flat via x402.",
  "inputSchema": {
    "type": "object",
    "required": [
      "memories"
    ],
    "properties": {
      "memories": {
        "type": "array",
        "items": {
          "type": "object",
          "required": [
            "content"
          ],
          "properties": {
            "ts": {
              "type": "number"
            },
            "tags": {
              "type": "array",
              "items": {
                "type": "string"
              }
            },
            "content": {
              "type": "string"
            }
          }
        },
        "description": "up to 200 items"
      }
    }
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  }
}
memory_search 1 change
{
  "name": "memory_search",
  "description": "Semantic search over YOUR stored memories (payer-wallet namespace). Returns top-k by embedding similarity. Paid: $0.002 per search via x402.",
  "inputSchema": {
    "type": "object",
    "required": [
      "query"
    ],
    "properties": {
      "k": {
        "type": "integer",
        "description": "max results (default 5, cap 20)"
      },
      "query": {
        "type": "string"
      }
    }
  },
  "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.borisinc/memory"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/com.borisinc/memory"}) 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%2Fcom.borisinc%2Fmemory.svg)](https://glimind.com/server/mcp-registry%2Fcom.borisinc%2Fmemory?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fcom.borisinc%2Fmemory?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.borisinc%2Fmemory.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.borisinc%2Fmemory.svg
   :target: https://glimind.com/server/mcp-registry%2Fcom.borisinc%2Fmemory?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:f1b0f5736b91d517…, first seen 2026-10-17, included at leaf 4099 of 77,796. Version history · verify what your client received.

Working alternatives

Tools (8)

Compare: most reliable data servers · most reliable knowledge servers · most reliable search 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 Borisinc Memory MCP server down right now?

As of 2026-10-27 06:18 UTC, the Borisinc Memory MCP server is degraded with a Glimind reliability score of 56/100 (grade D). Over the last 30 days it answered 92.2% of Glimind's liveness checks. It had 152 outages in 90 days, with a median recovery of 3 minutes.

How many tools does Borisinc Memory MCP server provide?

Borisinc Memory MCP server advertises 8 tools, including memory_export, memory_forget, memory_import, memory_search, memory_search_free.

How do I install Borisinc Memory MCP server?

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

Is the Borisinc Memory MCP server safe to connect to an AI agent?

Glimind scanned all 8 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 Borisinc Memory 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