Agentverse Memory

io.github.fetchaiPublished by GitHub account fetchaiv1.0.0Updated Oct 24, 2026

Graph-native persistent memory for AI agents — 33 MCP tools, zero-LLM writes.

The publisher's own server: Memory.fit

VerifiedStreamable HTTPWeb executableKnowledge & Memory

Overview

AI-generated overview

Gives an AI assistant graph-native persistent memory through a remote MCP endpoint with 33 tools and zero-LLM writes.

What you can do
Agentverse Memory is a remote memory service for AI agents. It exposes 33 MCP tools over a graph-native store, and its writes are described as zero-LLM, so storing memories does not call a language model. The manifest does not list individual tools, so the exact operations are not documented here.
When to use it
Worth considering when an assistant needs memory that persists across sessions and is organized as a graph rather than flat notes, and when you prefer a hosted endpoint over running a local memory server.
Requirements
A remote MCP connection to the provider's streamable HTTP endpoint. An API key is required and sent in the X-Api-Key header; the description says a free key can be obtained by posting an agent ID to the provider's key endpoint. No local runtime or environment variables are declared.
Before you install
The API key is a secret sent in the X-Api-Key header, so keep it out of logs and shared configuration. Memory content is stored on a third-party hosted service, so avoid putting sensitive data in it. The manifest lists no tools, so review what the 33 tools can write or change before relying on it.

Installation

In SourceWeft

  1. Open Agentverse Memory in the dashboard and add it to a workspace.
  2. Connect X-Api-Key credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. 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.fetchai%2Fagentverse-memory/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": {
    "agentverse-memory": {
      "type": "http",
      "url": "https://am-server-jbneh74b5q-uc.a.run.app/mcp",
      "headers": {
        "X-Api-Key": "<YOUR_API_KEY>"
      }
    }
  }
}

README

This repository has no README.

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

60% 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 listed15 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.

  • License10 pts

    Declare a license in the repository or the registry entry.

Other Memory integrations