Other · Remote MCP server
Mengram
Long-term memory for AI agents: semantic facts, episodic events, and procedural workflows.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.alibaizhanov/mengram- Version
- 2.25.4
- Status
- Active
- Category
- other
- Transport
- Streamable HTTP
- Published
- 2026-07-20
- Updated
- 2026-07-20
- Publisher
- alibaizhanov (GitHub) · 2 servers with pages here
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/alibaizhanov) · how
- Website
- mengram.io
- Repository
- github.com/alibaizhanov/mengram
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://mengram.io/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; OAuth advertised (the answer points to its authorization metadata)
- Checked on
- 2026-10-05
How to connect Mengram
Mengram is a remote MCP server: there is nothing to install. Its endpoint is https://mengram.io/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 from alibaizhanov (GitHub)
| Server | Runs |
|---|---|
| DenselyLossless context compression: 2-8x fewer tokens, byte-exact recovery, search inside payloads. | Local · stdio |
More other servers
| Server | Runs |
|---|---|
| MemtrustIndependent, reproducible benchmark harness for agent-memory backends. | Local · stdio |
| MemxusPersistent memory layer that saves and recalls your project context and preferences. | Remote · HTTPLive check: ✓ handshake |
| MencoroTrack and manage how your brand appears in AI answers: rank, mentions, sentiment, share of voice. | Remote & Local · HTTP, stdioLive check: sign-in required |
| MendriftMCP server for ML drift detection, MLflow registry diffing, and HMAC-gated model rollback. | Local · stdio |
| MeniscusLiquid glass design system for AI agents: specs, recipes and reference renders for every platform. | Remote · HTTPLive check: sign-in required |
| MenloComplete a Menlo application, authorize carrier quote requests and answer quote follow-ups. | Remote · HTTPLive check: ✓ handshake |
| Menor Preço Hoje - MPHPreços e ofertas locais em Lages via MCP para consumidores e agentes de IA. | Remote · HTTPLive check: ✓ handshake |
| MentionAgentLink building outreach from your agent: review drafts, send the batch, answer publisher replies. | Remote · HTTPLive check: sign-in required |