RecallMax-Neural

io.github.EvozimPublished by GitHub account Evozimv1.0.0Updated Oct 25, 2026

Semantic context compression and cognitive memory layer for LLM swarms.

VerifiedSSEWeb executableKnowledge & MemoryAI & ML

Overview

AI-generated overview

A remote MCP endpoint that provides semantic context compression and a cognitive memory layer for LLM swarms.

What you can do
The registry description presents it as a semantic context compression and cognitive memory layer for LLM swarms, aimed at condensing context and retaining memory across model interactions. No tools are listed in the manifest, so the specific operations an assistant can call are not documented here. The only declared interface detail is a payment-signature header tied to premium settlement.
When to use it
Consider it when you want an assistant to compress semantic context or keep a shared memory layer across multiple LLM agents, and you are prepared to settle premium usage through the declared payment header.
Requirements
A remote SSE endpoint; no local package or runtime is needed. No authentication is declared, but premium settlement requires the payment-signature header carrying a Base64-encoded EIP-3009 TransferWithAuthorization signature. Network access to the remote endpoint is required.
Before you install
The server asks for a payment-signature header containing a signed transfer authorization, which can authorize a payment; only supply it if you accept the spending. No tools are documented, so what data it receives or stores cannot be verified. It is a third-party remote service, so context and memory content you send leaves your machine.

Installation

In SourceWeft

  1. Open RecallMax-Neural in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via SSE. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.Evozim%2Frecallmax/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "recallmax-neural": {
      "type": "sse",
      "url": "https://recallmax-mcp.vercel.app/api/mcp"
    }
  }
}

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.