Developer · Remote MCP server

memoric

Provenance-first database for teams and agents: every value carries sources, rules and coverage.

Visit memoric's website

What the MCP Registry states

The entry as published to the official MCP Registry (read 2026-10-04), latest version.

Registry name
io.memoric/memoric
Version
0.1.0
Status
Active
Category
developer
Transport
Streamable HTTP
Published
2026-09-19
Updated
2026-09-19
Publisher
io.memoric
Namespace
Namespace verified by the MCP Registry via the domain memoric.io · how
Website
memoric.io
Source
Registry API entry

Remote endpoints

TransportURLHeaders declared
Streamable HTTPhttps://app.memoric.io/api/mcpNone

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; OAuth advertised (the answer points to its authorization metadata)
Checked on
2026-10-05

How the live check works

How to connect memoric

memoric is a remote MCP server: there is nothing to install. Its endpoint is https://app.memoric.io/api/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.

No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.

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

All 5,152 →
ServerRunsEndpoint or package
MemocoreShared memory for all your AI agents, your whole team and every MCP client - save, search, recall.Remote · HTTPLive check: sign-in requiredmemocore.ai
MemographGraph-based memory system for LLMs with knowledge graphs and semantic search.Local · stdioPyPI: memograph
MemoirPersistent memory for AI coding tools via MCP. Remembers across sessions and machines.Local · stdionpm: memoir-cli
Memoize - persistent agent memoryPersistent cross-session memory shared by Codex, Claude Code, ChatGPT, and other AI agents.Remote · HTTPLive check: sign-in requiredmemoize.xyz
MemoroPersonal AI memory layer on your own computer. Read/write durable memory across MCP clients.Local · stdionpm: @memoro/mcp-server
MemoryShared, persistent memory for AI agents - works with Claude, Kiro, Cursor, or any MCP client.Local · stdionpm: cortex-memory-mcp
Memory FabricFile-first, local-first MCP memory for AI coding assistants: Markdown + YAML, no vector DB.Local · stdioPyPI: memory-fabric
Memory for AILocal codebase knowledge graph for AI agents - 162 languages, sub-ms queries, 99% fewer tokens.Local · stdionpm: memory-for-ai-mcp