mcp-registry/ai.maximem/synap · v0.1.1
As of 2026-10-22 22:06 UTC, the Maximem Synap MCP server is up with a Glimind reliability score of 85/100 (grade B). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 35 outages in 90 days, with a median recovery of 4 minutes.
Persistent memory for AI agents — log and recall conversation context over MCP.
Claude Code
claude mcp add --transport http maximem-synap-mcp-server https://synap-mcp.maximem.ai/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"maximem-synap-mcp-server": {
"type": "http",
"url": "https://synap-mcp.maximem.ai/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
8 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 →
4 of 4 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 →
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%2Fai.maximem%2Fsynap/fixes
{
"name": "check_memory_status",
"description": "Check whether a logged exchange has finished processing. Pass the ingestion_id returned by log_exchange. Returns the processing status and how many memories were extracted. Useful to confirm a save completed (extraction is asynchronous). Takes no user_id or customer_id: an ingestion_id already identifies the write, so the identifier contract does not apply here.",
"inputSchema": {
"type": "object",
"title": "check_memory_statusArguments",
"required": [
"ingestion_id"
],
"properties": {
"ingestion_id": {
"type": "string",
"title": "Ingestion Id"
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "list_recent_memories",
"description": "List recent things remembered about this user. Useful for debugging or to confirm that memory is working. Pass user_id to scope to one person. SCOPING: customer_id is B2B ONLY. On a B2B instance (user_context_isolation=strict) it is REQUIRED and a user_id on its own is an error. On a B2C instance (user_context_isolation=equals_customer) it is NOT accepted: the API rejects it with HTTP 400, customer-scoped retrieval does not exist there, and user_id is the whole identity. If you do not know which",
"inputSchema": {
"type": "object",
"title": "list_recent_memoriesArguments",
"properties": {
"user_id": {
"anyOf": [
{
"type": "string"
},
{
"type": "null"
}
],
"title": "User Id",
"default": null,
"description": "Stable id of the end-user this call belongs to. On a B2C instance this is the ONLY identifier you send and it is the whole identity. On a B2B instance send it together with customer_id. Omit both if every conversation is the same single user."
},
"customer_id": {
"anyOf": [
{
"type": "string"
},
{
"type": "null"
}
],
"title": "Customer Id",
"default": null,
"description": "B2B ONLY. Required on a B2B instance (user_context_isolation=strict), where a user_id on its own is an error. NOT accepted on a B2C instance (user_context_isolation=equals_customer): the API rejects it with HTTP 400 and there is no customer scope to read from. When in doubt leave this out and send user_id alone. GET /api/v1/auth/whoami reports the mode."
},
"max_results": {
"type": "integer",
"title": "Max Results",
"default": 10
}
}
},
"annotations": {
"readOnlyHint": true
}
}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/ai.maximem/synap"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/ai.maximem/synap"}) over MCP.
log_exchange ~498 tokensrecall_context ~445 tokenslist_recent_memories ~423 tokenscheck_memory_status ~162 tokensStatic 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:
[](https://glimind.com/server/mcp-registry%2Fai.maximem%2Fsynap?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fai.maximem%2Fsynap?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fai.maximem%2Fsynap.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fai.maximem%2Fsynap.svg :target: https://glimind.com/server/mcp-registry%2Fai.maximem%2Fsynap?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:a838f332db570797…, first seen 2026-10-17, included at leaf 8419 of 48,390. Version history · verify what your client received.
Compare: most reliable knowledge servers
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.
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"
}
}
}
As of 2026-10-22 22:06 UTC, the Maximem Synap MCP server is up with a Glimind reliability score of 85/100 (grade B). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 35 outages in 90 days, with a median recovery of 4 minutes.
Maximem Synap MCP server advertises 4 tools, including check_memory_status, list_recent_memories, log_exchange, recall_context.
Point your MCP client at this streamable-http endpoint: https://synap-mcp.maximem.ai/mcp
Glimind scanned all 4 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.
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.