Other · Remote MCP server
MMW Managed Memory Workspace
Ultra-fast persistent memory workspace with tenant isolation and cross-model continuity.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.msingatullin/mmw- Version
- 1.0.0
- Status
- Active
- Category
- other
- Transport
- Streamable HTTP
- Published
- 2026-09-23
- Updated
- 2026-09-23
- Publisher
- msingatullin (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/msingatullin) · how
- Website
- mmwhub.tech
- Repository
- github.com/msingatullin/mmw-mcp
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://mcp.mmwhub.tech/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 MMW Managed Memory Workspace
MMW Managed Memory Workspace is a remote MCP server: there is nothing to install. Its endpoint is https://mcp.mmwhub.tech/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
Site checks
The website's own root, mmwhub.tech, was checked for the files that tell AI systems about a site.
| File | Result |
|---|---|
/llms.txt | No real file found |
/.well-known/mcp.json | No real file found |
/.well-known/ai-plugin.json | No real file found |
/agents.json | No real file found |
More other servers
| Server | Runs |
|---|---|
| MixpanelAnalyze user behavior with funnels, retention, cohorts, and event segmentation. | Local · stdio |
| MixpanelQuery Mixpanel events, funnels, retention, segmentation and insights (JQL). | Remote · HTTPLive check: ✓ handshake |
| Mixpanel MCPQuery Mixpanel events, funnels, retention, cohorts, and user profiles. | Local · stdio |
| MlflowMLflow MCP - experiments, runs, registered models, versions, traces, assessments (MLflow 3) | Local · stdio |
| MnemaLocal-first, formally verified memory for AI agents: consult/learn/related/list over MCP. | Local · stdio |
| MnemexTemporal memory for AI with decay and reinforcement. Two-layer storage (JSONL + Markdown). | Local · stdio |
| Mnemolog MCPHosted MCP memory and agent control plane for durable conversations, jobs, and operations. | Remote · HTTPLive check: sign-in required |
| MnemoscopePredict context rot, sign every agent write, tier reads. Markdown-native, 100% local. | Local · stdio |