InfoLang Memory MCP Server

by infolang Your server? Claim it

not responding

InfoLang Memory is listed as active in the registry but did not answer our last check.

InfoLang semantic memory MCP — investigate, memorize, and recall compressed agent context.

The linked repository no longer exists on GitHub — it was deleted or made private.

Uptime history 51 days of history · worst day 0%

51 days agonow

0.0%

Uptime 24h

0 of 91 checks

—

Tools

hidden behind auth

811 ms

Response time

average over 24h

open, no key

Access

streamable-http

InfoLang Memory does not always answer

Over the last week it answered 0.0% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 7 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add mcp --transport http https://api.infolang.ai/v1/mcp/

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "mcp": {
      "url": "https://api.infolang.ai/v1/mcp/"
    }
  }
}

~/.codex/config.toml

[mcp_servers.mcp]
url = "https://api.infolang.ai/v1/mcp/"

.cursor/mcp.json

{
  "mcpServers": {
    "mcp": {
      "url": "https://api.infolang.ai/v1/mcp/"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "mcp": {
      "url": "https://api.infolang.ai/v1/mcp/"
    }
  }
}

Endpoints

URL	Transport	State	Latency	Checked
https://api.infolang.ai/v1/mcp/	streamable-http	answering	811 ms	7 min ago

Alternatives to InfoLang Memory

same job, measured the same way

RecallMax-Neural

by evozim

Semantic context compression and cognitive memory layer for LLM swarms.

answering

ContextStream MCP Server

by contextstream

Project memory, semantic code search, and grounded agent context.

answering

Synap Memory

by maximem

Persistent memory for AI agents — log and recall conversation context over MCP.

4 tools answering

Montycat MCP - Shared Memory for AI Agents

by montygovernance

Shared, persistent memory for AI agents, with semantic recall and live updates.

1 522 installs/wk local only

Cap Shield

by robinlidberg-dot

Context selection and compression for AI agents - recall measured, not claimed.

217 installs/wk local only

Memdata

by thelabvenice

Persistent memory for AI agents. Store context, retrieve it semantically.

34 installs/wk local only

Claude Memory Manager

by nyxtoolsdev

Cross-session memory for Claude Code — context capture, semantic search, recall

80 installs/wk local only

GrantAi Memory

by solonai

Persistent memory for AI agents. Infinite context with sub-millisecond recall.

local only

InfoLang Memory — questions

Answers built from our own checks of this server.

Is InfoLang Memory working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 0 of 91 checks got a reply (0.0%), average response time 811 ms. The bar chart above shows every period we have measured.

Is InfoLang Memory still maintained?

The linked repository no longer exists on GitHub — it was deleted or made private. We show this because it changes what you can expect: an unmaintained server may keep answering for months and then stop without warning.

The registry lists InfoLang Memory as active — why does it not respond?

The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.

How do I connect InfoLang Memory?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does InfoLang Memory need an API key?

No. InfoLang Memory completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. This is what we observed, not what the docs claim.