Developer · Remote MCP server
ReasonGraph Cloud memory
Graph memory for AI agents: entities, cause-effect links, cross-session recall, time travel.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
ai.primaxiom.memory/reasongraph- Version
- 0.6.6
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP
- Published
- 2026-09-07
- Updated
- 2026-09-07
- Publisher
- ai.primaxiom.memory
- Namespace
- Namespace verified by the MCP Registry via the domain memory.primaxiom.ai or a parent domain of it · how
- Website
- memory.primaxiom.ai
- Repository
- github.com/bgokden/reasongraph
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://memory.primaxiom.ai/mcp | Authorization (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; a Bearer token is asked for
- Checked on
- 2026-10-05
How to connect ReasonGraph Cloud memory
ReasonGraph Cloud memory is a remote MCP server: there is nothing to install. Its endpoint is https://memory.primaxiom.ai/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: Authorization (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 |
|---|---|
| ReadyAgentsLocal YAML/JSON agent workflow CLI with approvals, resume, and optional stdio or loopback MCP HTTP. | Local · stdio |
| ReadyoraiZero-cost MCP server for local code inspection and best-practice recommendations. | Local · stdio |
| Real Fake DataRealistic synthetic test data - valid PESELs, NIPs, IBANs, addresses, people across 27 EU countries. | Local · stdio |
| Reality Graph Verification ToolsRead-only AI coding tools for change verification, release readiness, capacity, and guidance. | Remote · HTTPLive check: ✓ handshake |
| RebaseSchema, database, document, user and dev-server tools for a Rebase backend project. | Local · stdio |
| RecallPersistent memory for Claude Code and Codex. Search and re-inject context from any session. | Local · stdio |
| Recall - persistent memory for agentsPersistent memory for AI agents. Free, no LLM, no SDK. Open Worker you can self-host in 2 commands. | Remote · HTTP |
| RecaoRank a competitor's EU App Store ads by longevity. From Apple's official Ad Repository. | Remote · HTTPLive check: ✓ handshake |