Developer · Remote MCP server
Agentverse Memory
Graph-native persistent memory for AI agents - 33 MCP tools, zero-LLM writes.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.fetchai/agentverse-memory- Version
- 1.0.0
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP
- Published
- 2026-05-17
- Updated
- 2026-05-17
- Publisher
- fetchai (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/fetchai) · how
- Repository
- github.com/fetchai/agentverse-memory
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://am-server-jbneh74b5q-uc.a.run.app/mcp | X-Api-Key (required, secret) |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 401)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 401
- Checked on
- 2026-10-05
How to connect Agentverse Memory
Agentverse Memory is a remote MCP server: there is nothing to install. Its endpoint is https://am-server-jbneh74b5q-uc.a.run.app/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
The registry entry declares an HTTP header for the connection: X-Api-Key (required, secret). A secret header usually carries an API key or token issued by the service; clients that accept custom headers set it with the server's URL.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| AgentSQLGuard AI agents' PostgreSQL/MySQL access via MCP: SQL audit, auth, masking, write approval. | Remote · HTTPLive check: sign-in required |
| AgentSUMOMCP server for LLM-driven SUMO traffic simulation, scenario design, and result analysis. | Local · stdio |
| agentsyncMulti-agent coordination MCP: claim work, survey peers, resolve conflicts via a git branch as CAS. | Local · stdio |
| AgenttunePersonality tuning files for AI agents: 43 MIT-licensed tunings + 5 inline personality tests. | Remote · HTTPLive check: ✓ handshake |
| AgentvetValidate tool-call args before execution. Returns LLM-friendly retry hints. | Local · stdio |
| AgentWatchMulti-agent observability: cascade failure detection, heartbeats, and forensic replay. | Local · stdio |
| AggreteMCP policy proxy: enforces a code of conduct across connectors before the upstream is called. | Local · stdio |
| agilitycms.comAn MCP server that provides access to Agility CMS. See https://mcp.agilitycms.com for more details. | Remote · HTTPLive check: sign-in required |