io.github.sidyellur/tether
PYPI · TETHER-MEMORY · SCANNED SEP 20
Local-first agent memory over SQLite: remember, recall, link, forget. Degrades, never fails.
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 Security50
- 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 native-build step with no shell scripting around it. View diagnostics → Pass
- 1 of 29 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency32
- 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
- License check failed: the license (MIT License) isn't a recognized OSI-approved license. See how to fix → Fail
- 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 Usability77
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1237 tokens (~206/item across 6 items; 4 tools + 2 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management43
- Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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.sidyellur/tether MCP server?
io.github.sidyellur/tether runs locally as a PyPI package, launched with uvx tether-memory. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · tether-memory
claude mcp add sidyellur-tether -- uvx tether-memory
{
"mcpServers": {
"sidyellur-tether": {
"command": "uvx",
"args": [
"tether-memory"
]
}
}
} {
"servers": {
"sidyellur-tether": {
"command": "uvx",
"args": [
"tether-memory"
]
}
}
} codex mcp add sidyellur-tether -- uvx tether-memory
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"sidyellur-tether": {
"type": "local",
"command": [
"uvx",
"tether-memory"
],
"enabled": true
}
}
} openclaw mcp add sidyellur-tether --command uvx --arg tether-memory
mcp_servers:
sidyellur-tether:
command: "uvx"
args: ["tether-memory"] {
"McpServers": {
"sidyellur-tether": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"tether-memory"
]
}
}
} assistant mcp add sidyellur-tether -t stdio -c uvx -a tether-memory
{
"mcpServers": {
"sidyellur-tether": {
"command": "uvx",
"args": [
"tether-memory"
]
}
}
} 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 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 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 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 +3
- Stability: unverified → 0.27 ▲ functional
- 12 Sept 26 +15
- Malware scan: unverified → pass ▲ security
- 11 Sept 26 −15
- Malware scan: pass → unverified ▼ security
- 9 Sept 26 +15
- Malware scan: unverified → pass ▲ 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/tether-memory@0.6.1
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 29 packages
| Packages resolved | 29 |
|---|---|
| No linked repository | 1 |
| 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 →
forget ~78
Soft-delete a memory by id: marks it no longer current (excluded from recall/the boot index) but keeps the row, reversibly, like consolidation and the forgetting sweep already do. Returns {"forgotten", "existed"}. (Permanent purge is an admin-only CLI operation, not available here.)
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | – |
No output schema declared.
No examples provided.
link ~34
Create a bidirectional link between two memories by id.
| Name | Type | Req | Description |
|---|---|---|---|
| id_a | integer | yes | – |
| id_b | integer | yes | – |
No output schema declared.
No examples provided.
recall ~541
Search memories by keyword and semantic similarity, then follow the usage graph to related memories, most relevant first. Ask in plain language, the way you would ask a colleague ("how do we run the integration tests?", "what did the user decide about the auth library?") - a memory matching some of the words is a hit, and the best match ranks first. Recall BEFORE starting a task, not only when stuck: the index you were given at session start is titles only. Memories from the current project rank slightly ahead of equally-good ones from elsewhere. Each hit carries {id, type, title, body, tags, updated_at} and a `via` receipt explaining why it surfaced (a direct match, or the edge it was reached through). Use `updated_at` to judge staleness (an old fact may no longer hold; verify before relying on it) and `id` to cite what you update via remember/link. `body` is an EXCERPT centered on your query, not the whole memory. When a memory was longer than the excerpt, the hit also carries `truncated: true` and `body_chars` (the full length). To read one in full, call recall(id=N) - that returns just that memory, whole. Args: query: free text; punctuation is safe. May be omitted if `tags` is given. type: optional filter ("user"/"feedback"/"project"/"reference"). limit: max results (default 20). budget: how far to follow associations (0 = direct matches only). session: optional id grouping related recalls so they prime each other. tags: optional comma-separated tags; exact-match filter (a memory must carry every listed tag). Combine with `query` to filter its ranked hits, or use alone (query omitted) to list every current memory with those tags, newest first, deterministic rather than ranked - raise `limit` to fetch beyond the default page size. id: fetch this one memory in full instead of searching. Use it after a search returns a `truncated` hit you want to read completely. full: return complete bodi…
| Name | Type | Req | Description |
|---|---|---|---|
| budget | – | – | – |
| full | boolean | – | – |
| id | – | – | – |
| limit | integer | – | – |
| query | string | – | – |
| session | – | – | – |
| tags | – | – | – |
| type | – | – | – |
No output schema declared.
No examples provided.
remember ~419
Save a durable memory. UPSERTS: a memory of the same `type` with the same (whitespace/case-normalized) `title` is updated in place instead of duplicated, so re-remembering a fact refines it rather than cluttering. Worth remembering: decisions and their reasons, conventions, gotchas that cost time, the user's preferences and how they like to work, facts about the environment (paths, commands, accounts) you had to discover. Not worth it: anything derivable from the code, or a transcript of what you did. Remember it when you learn it, not at the end of the session. Memories of type project/feedback/reference are tagged with the current project automatically (`proj:<name>`, from CLAUDE_PROJECT_DIR) unless you pass a `proj:` tag yourself; `user` memories are about the person and stay global. Args: type: one of "user", "feedback", "project", "reference". title: a short label; also the dedup key within a type. body: the fact. For feedback/project, a "Why:" / "How to apply:" line helps. tags: optional comma-separated tags. links: optional list of related memory ids. Merged (union) into any links already on the memory, never replaces them - omitting this on a refine call preserves links set earlier. crystallizes: optional list of source memory ids this memory abstracts; links it over them as a crystallized principle (needs TETHER_CRYSTALLIZE). Returns {"id", "action"} where action is "created", "updated", or (with TETHER_CONSOLIDATE on) "consolidated" - a near-duplicate was superseded.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | yes | – |
| crystallizes | – | – | – |
| links | – | – | – |
| tags | string | – | – |
| title | string | yes | – |
| type | string | yes | – |
No output schema declared.
No examples provided.
What is the io.github.sidyellur/tether MCP server?
io.github.sidyellur/tether is an MCP server listed in the public MCP registry as io.github.sidyellur/tether. Local-first agent memory over SQLite: remember, recall, link, forget. Degrades, never fails. This page covers its PyPI package (tether-memory).
Is the io.github.sidyellur/tether MCP server safe to use?
io.github.sidyellur/tether scores 57 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.sidyellur/tether MCP server expose?
io.github.sidyellur/tether exposes 4 tools: remember, recall, link, forget. Their descriptions and schemas cost roughly 1,072 tokens of context every time the server is loaded.
Is the io.github.sidyellur/tether MCP server still maintained?
io.github.sidyellur/tether 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.