mcp-registry/io.github.vortx-ai/emem · v2.4.4
Also listed as awesome/vortx-ai/emem
Verdict. Vortx Ai Emem MCP server answered 99.52% of Glimind's liveness checks over 30 days, better than 16% of MCP servers, with 745 ms median handshake and 248 outages in 90 days. Its agent-readiness grade is A (92/100) across 18 tools, costing an agent about 11,411 tokens to load. Checked every few minutes; no tool is ever called.
Data as of .
| Metric | Value | Better than |
|---|---|---|
| Uptime, 30 days | 99.52% | 16% of MCP servers |
| Median handshake latency | 745 ms | 35% of MCP servers |
| p95 handshake latency | 2820 ms | — |
| Checks in 30 days | 4,828 | — |
| Outages, 90 days | 248 | — |
| Median recovery | 3 min | — |
| Agent-readiness score | 92/100 (A) | 73% of MCP servers |
| Tools | 18 | — |
| Tool-list size for an agent | ~11,411 tokens | 16% of MCP servers |
| Days observed | 29 | — |
As of 2026-10-26 18:59 UTC, the Vortx Ai Emem MCP server is up with a Glimind reliability score of 80/100 (grade B). Over the last 30 days it answered 99.5% of Glimind's liveness checks. It had 247 outages in 90 days, with a median recovery of 4 minutes.
Shared memory for AI agents. One address per fact, one signature you check. No key to read.
Claude Code
claude mcp add --transport http vortx-ai-emem-mcp-server https://emem.dev/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"vortx-ai-emem-mcp-server": {
"type": "http",
"url": "https://emem.dev/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
2 tool definition(s) exceed ~1,200 tokens each (largest: emem_intent, ~1,619).
Move long reference material out of descriptions (link a doc or expose a resource), drop repeated examples, and collapse large enums. Trimming these to ~600 tokens saves ~1,718 tokens every session. How to fix →
3 parameter(s) across 1 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →
In the last 30 days: 0 tool(s) removed and 14 schema change(s).
Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts. How to fix →
Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.github.vortx-ai/emem"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/io.github.vortx-ai/emem"}) over MCP.
emem_intent ~1,619 tokensemem_recall ~1,299 tokensemem_ask ~896 tokensemem_tools ~869 tokensemem_find_similar ~794 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fio.github.vortx-ai%2Femem?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fio.github.vortx-ai%2Femem?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.vortx-ai%2Femem.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.vortx-ai%2Femem.svg :target: https://glimind.com/server/mcp-registry%2Fio.github.vortx-ai%2Femem?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:a70f1bfd886ee22c…, first seen 2026-10-24, included at leaf 61862 of 74,904. Version history · verify what your client received.
Compare: most reliable knowledge servers · most reliable other servers · most reliable ml servers · most reliable security servers · most reliable retrieval servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-26 18:59 UTC, the Vortx Ai Emem MCP server is up with a Glimind reliability score of 80/100 (grade B). Over the last 30 days it answered 99.5% of Glimind's liveness checks. It had 247 outages in 90 days, with a median recovery of 4 minutes.
Vortx Ai Emem MCP server advertises 18 tools, including emem_ask, emem_echo_verify, emem_entity, emem_entity_link, emem_entity_resolve.
Point your MCP client at this streamable-http endpoint: https://emem.dev/mcp
Glimind scanned all 18 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.