io.github.TeleAI-UAGI/telemem
PYPI · TELEMEM · SCANNED SEP 20
Long-term and multimodal memory for AI agents - character-aware, mem0-compatible, fully-local option
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security99
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
- 6 of 59 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 36 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability81
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 677 tokens (~84/item across 8 items; 8 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
- Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 3 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the io.github.TeleAI-UAGI/telemem MCP server?
io.github.TeleAI-UAGI/telemem runs locally as a PyPI package, launched with uvx telemem. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · telemem
claude mcp add teleai-uagi-telemem -- uvx telemem
{
"mcpServers": {
"teleai-uagi-telemem": {
"command": "uvx",
"args": [
"telemem"
]
}
}
} {
"servers": {
"teleai-uagi-telemem": {
"command": "uvx",
"args": [
"telemem"
]
}
}
} codex mcp add teleai-uagi-telemem -- uvx telemem
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"teleai-uagi-telemem": {
"type": "local",
"command": [
"uvx",
"telemem"
],
"enabled": true
}
}
} openclaw mcp add teleai-uagi-telemem --command uvx --arg telemem
mcp_servers:
teleai-uagi-telemem:
command: "uvx"
args: ["telemem"] {
"McpServers": {
"teleai-uagi-telemem": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"telemem"
]
}
}
} assistant mcp add teleai-uagi-telemem -t stdio -c uvx -a telemem
{
"mcpServers": {
"teleai-uagi-telemem": {
"command": "uvx",
"args": [
"telemem"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +16
- Malware scan: unverified → pass ▲ security
- 17 Sept 26 −15
- Malware scan: pass → unverified ▼ security
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 −3
- Stability: pass → 0.80 functional
- 13 Sept 26 0
- Stability: 0.97 → pass security
- 12 Sept 26 +16
- Malware scan: unverified → pass ▲ security
- 11 Sept 26 −15
- Malware scan: pass → unverified ▼ security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Analysed pypi/telemem@1.10.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 59 packages
| Packages resolved | 59 |
|---|---|
| Stale | 4 |
| No linked repository | 2 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
add_memory Add memory ~177
Store a fact, preference, or conversation in TeleMem long-term memory. Provide `text` for a single statement or `messages` for conversation turns. Scoped by user_id/agent_id/run_id; defaults to the server's default user.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | – | – | Optional agent scope. |
| infer | boolean | – | Extract salient facts with the LLM before storing (TeleMem's default pipeline). Set false to store the raw text as-is. |
| messages | – | – | Conversation turns as [{"role": "user"|"assistant", "content": "..."}]. Takes precedence over `text`. |
| metadata | – | – | Arbitrary metadata to attach to the stored memories. |
| run_id | – | – | Optional run/session scope. |
| text | – | – | A single statement to remember. Use this or `messages`. |
| user_id | – | – | User the memory belongs to. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | object | yes | – |
No examples provided.
delete_all_memories Delete all memories in scope ~71
Delete every memory in the given scope. Destructive: requires an explicit user_id, agent_id, or run_id — the default user is never assumed.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | – | – | Agent scope to wipe. |
| run_id | – | – | Run scope to wipe. |
| user_id | – | – | User scope to wipe. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | object | yes | – |
No examples provided.
delete_memory Delete memory ~29
Delete a single memory by memory_id.
| Name | Type | Req | Description |
|---|---|---|---|
| memory_id | string | yes | Exact memory_id to delete. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | object | yes | – |
No examples provided.
get_memories List memories ~82
List stored memories for a user/agent/run with their memory_ids. Use user_id "events" to list shared conversation-event memories.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | – | – | Optional agent scope. |
| limit | integer | – | Maximum memories to return. |
| run_id | – | – | Optional run/session scope. |
| user_id | – | – | User scope; defaults to the server's default user. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | object | yes | – |
No examples provided.
get_memory Get memory ~30
Fetch a single memory by its memory_id.
| Name | Type | Req | Description |
|---|---|---|---|
| memory_id | string | yes | Exact memory_id to fetch. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | object | yes | – |
No examples provided.
memory_history Memory history ~37
Show the change history (ADD/UPDATE/DELETE events) of a memory.
| Name | Type | Req | Description |
|---|---|---|---|
| memory_id | string | yes | Exact memory_id to inspect. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | object | yes | – |
No examples provided.
search_memories Search memories ~126
Semantic search over TeleMem memories. Returns the matching memories as one consolidated text passage (TeleMem fuses related memories). Shared event memories (pseudo-user "events") are searched automatically.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | – | – | Optional agent scope. |
| limit | integer | – | Maximum memories to consider. |
| query | string | yes | Natural-language description of what to find. |
| run_id | – | – | Optional run/session scope. |
| threshold | – | – | Minimum similarity score in [0, 1] for a memory to match. |
| user_id | – | – | User scope; defaults to the server's default user. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | object | yes | – |
No examples provided.
update_memory Update memory ~53
Overwrite the text of an existing memory by memory_id.
| Name | Type | Req | Description |
|---|---|---|---|
| memory_id | string | yes | Exact memory_id to update. |
| metadata | – | – | Optional replacement metadata. |
| text | string | yes | Replacement text for the memory. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | object | yes | – |
No examples provided.
What is the io.github.TeleAI-UAGI/telemem MCP server?
io.github.TeleAI-UAGI/telemem is an MCP server listed in the public MCP registry as io.github.TeleAI-UAGI/telemem. Long-term and multimodal memory for AI agents - character-aware, mem0-compatible, fully-local option. This page covers its PyPI package (telemem).
Is the io.github.TeleAI-UAGI/telemem MCP server safe to use?
io.github.TeleAI-UAGI/telemem scores 85 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.TeleAI-UAGI/telemem MCP server expose?
io.github.TeleAI-UAGI/telemem exposes 8 tools: add_memory, search_memories, get_memories, get_memory, update_memory, and 3 more. Their descriptions and schemas cost roughly 605 tokens of context every time the server is loaded.
Is the io.github.TeleAI-UAGI/telemem MCP server still maintained?
io.github.TeleAI-UAGI/telemem is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.TeleAI-UAGI/telemem MCP server under?
io.github.TeleAI-UAGI/telemem declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.