# io.github.sidyellur/tether (pypi · tether-memory)

Local-first agent memory over SQLite: remember, recall, link, forget. Degrades, never fails.

- Trust score: 57/100 (low)
- Change this week: −9
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- pypi · `tether-memory`: 57/100 (this document), [markdown](https://verifymcp.io/servers/sidyellur-tether/tether-memory.md), [page](https://verifymcp.io/servers/sidyellur-tether/tether-memory)

## Channel facts

- Registry: `pypi`
- Package: `tether-memory`
- Version: `0.6.1`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Supply Chain Security**: 50/100
  - Malware scan not yet available for this package.
  - No known CVEs affecting this package version or its production dependencies.
  - Runs hatchling.build at install time, a recognised native-build step with no shell scripting around it.
  - 1 of 29 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 32/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - License check failed: the license (MIT License) isn't a recognized OSI-approved license.
  - Actively maintained (last published 12 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 77/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 43/100
  - Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 67/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### 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.

### Claude

```bash
claude mcp add sidyellur-tether -- uvx tether-memory
```

### Cursor

```json
{
  "mcpServers": {
    "sidyellur-tether": {
      "command": "uvx",
      "args": [
        "tether-memory"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "sidyellur-tether": {
      "command": "uvx",
      "args": [
        "tether-memory"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add sidyellur-tether -- uvx tether-memory
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "sidyellur-tether": {
      "type": "local",
      "command": [
        "uvx",
        "tether-memory"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add sidyellur-tether --command uvx --arg tether-memory
```

### Hermes

```yaml
mcp_servers:
  sidyellur-tether:
    command: "uvx"
    args: ["tether-memory"]
```

### Netclaw

```json
{
  "McpServers": {
    "sidyellur-tether": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "tether-memory"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add sidyellur-tether -t stdio -c uvx -a tether-memory
```

### Other

```json
{
  "mcpServers": {
    "sidyellur-tether": {
      "command": "uvx",
      "args": [
        "tether-memory"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-20 (score 57, +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.

### 2026-09-18 (score 56, +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.

### 2026-09-17 (score 55, −15)

- [security regression] Malware scan: pass → unverified

### 2026-09-16 (score 70, +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.

### 2026-09-15 (score 69, +3)

- [functional improvement] Stability: unverified → 0.27

### 2026-09-12 (score 66, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-09-11 (score 51, −15)

- [security regression] Malware scan: pass → unverified

### 2026-09-09 (score 66, +15)

- [security improvement] Malware scan: unverified → pass

## MCP tools (4)

### `remember` (~419 tokens)

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.

Input parameters:

- `body` (string, required)
- `crystallizes`
- `links`
- `tags` (string)
- `title` (string, required)
- `type` (string, required)

### `recall` (~541 tokens)

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…

Input parameters:

- `budget`
- `full` (boolean)
- `id`
- `limit` (integer)
- `query` (string)
- `session`
- `tags`
- `type`

### `link` (~34 tokens)

Create a bidirectional link between two memories by id.

Input parameters:

- `id_a` (integer, required)
- `id_b` (integer, required)

### `forget` (~78 tokens)

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.)

Input parameters:

- `id` (integer, required)

## Diagnostics

Captured diagnostic sections: Provenance, Install scripts, Dependencies. The full working is on the page: https://verifymcp.io/servers/sidyellur-tether/tether-memory#diagnostics

## Score history

- 2026-09-20: 57
- 2026-09-19: 56
- 2026-09-18: 56
- 2026-09-17: 55
- 2026-09-16: 70
- 2026-09-15: 69
- 2026-09-14: 66
- 2026-09-13: 66
- 2026-09-12: 66
- 2026-09-11: 51
- 2026-09-10: 66
- 2026-09-09: 66
- 2026-09-08: 51
- 2026-09-07: 36

## Common questions

### 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.

## Links

- PyPI project: https://pypi.org/project/tether-memory/
- Socket report: https://socket.dev/pypi/package/tether-memory
- Repository: https://github.com/sidyellur/tether
- Changelog RSS feed: https://verifymcp.io/servers/sidyellur-tether/tether-memory.xml
- Changelog JSON feed: https://verifymcp.io/servers/sidyellur-tether/tether-memory.json
- HTML version of this page: https://verifymcp.io/servers/sidyellur-tether/tether-memory