Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.TeleAI-UAGI/telemem

PYPI · TELEMEM

Long-term and multimodal memory for AI agents - character-aware, mem0-compatible, fully-local option

Available components

−15 this week 81 Trust /100

Last scanned (21 hours ago)

Scores higher than 82% of PyPI servers

Category Memory and Knowledge

Trust breakdown (7 categories)

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 Security49
  • Malware scan not yet available for this package.Unverified
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
  • 6 of 55 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to TeleAI-UAGI/telemem). View diagnostics → Pass
  • Clear OSI-approved license (Apache-2.0).Pass
  • Actively maintained (last published 12 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 Management100
  • No destabilizing schema changes in the last 30 days.Pass
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
Changelog

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.

  • 4 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
  • 1 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 31 Oct 26 −15
    • Malware scan: pass → unverified ▼ security
    • Package version: 1.9.0 → 1.10.1 functional
  • 30 Oct 26 +15
    • Malware scan: unverified → pass ▲ security
  • 29 Oct 26 −15
    • Malware scan: pass → unverified ▼ security
  • 28 Oct 26 +15
    • Malware scan: unverified → pass ▲ security
  • 27 Oct 26 −15
    • Malware scan: pass → unverified ▼ security
  • 26 Oct 26 +16
    • Malware scan: unverified → pass ▲ security
    • Stability: 0.97 → pass security
Diagnostics

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 4 Nov 2026 · Analysed pypi/telemem@1.10.1

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem pypi
Reason Verified
Discovered via Registry attestation endpoint
Source repo TeleAI-UAGI/telemem
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/TeleAI-UAGI/telemem/.github/workflows/release.yml@refs/tags/v1.10.1
Rekor log index 3418381474
Predicate type PyPI publish attestation https://docs.pypi.org/attestations/publish/v1
Subject digest sha256:f134abf647a15e204834b813e8abd7fbbe1e5e040c85c824d132af8c8a5afa13

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 55 packages
Packages resolved 55
Stale 4
No linked repository 2
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 8 exposed · ~605 tokens

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 →

Tool Tokens
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.

NameTypeReqDescription
agent_id––Optional agent scope.
inferboolean–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.
NameTypeReqDescription
resultobjectyes–

No examples provided.

delete_all_memories ~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.

NameTypeReqDescription
agent_id––Agent scope to wipe.
run_id––Run scope to wipe.
user_id––User scope to wipe.
NameTypeReqDescription
resultobjectyes–

No examples provided.

delete_memory ~29

Delete a single memory by memory_id.

NameTypeReqDescription
memory_idstringyesExact memory_id to delete.
NameTypeReqDescription
resultobjectyes–

No examples provided.

get_memories ~82

List stored memories for a user/agent/run with their memory_ids. Use user_id "events" to list shared conversation-event memories.

NameTypeReqDescription
agent_id––Optional agent scope.
limitinteger–Maximum memories to return.
run_id––Optional run/session scope.
user_id––User scope; defaults to the server's default user.
NameTypeReqDescription
resultobjectyes–

No examples provided.

get_memory ~30

Fetch a single memory by its memory_id.

NameTypeReqDescription
memory_idstringyesExact memory_id to fetch.
NameTypeReqDescription
resultobjectyes–

No examples provided.

memory_history ~37

Show the change history (ADD/UPDATE/DELETE events) of a memory.

NameTypeReqDescription
memory_idstringyesExact memory_id to inspect.
NameTypeReqDescription
resultobjectyes–

No examples provided.

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.

NameTypeReqDescription
agent_id––Optional agent scope.
limitinteger–Maximum memories to consider.
querystringyesNatural-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.
NameTypeReqDescription
resultobjectyes–

No examples provided.

update_memory ~53

Overwrite the text of an existing memory by memory_id.

NameTypeReqDescription
memory_idstringyesExact memory_id to update.
metadata––Optional replacement metadata.
textstringyesReplacement text for the memory.
NameTypeReqDescription
resultobjectyes–

No examples provided.

Install

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

# add to Claude Code
claude mcp add teleai-uagi-telemem -- uvx telemem
Common questions

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 81 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 2026. Its build provenance is signed and verified. 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 4 November 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.