io.github.sidyellur/tether

tether

Is the io.github.sidyellur/tether MCP server down? No. It answered initialize and tools/list in the probe of 2026-10-27.

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

alive probed 2026-11-14 · unchanged since 2026-10-27

4tools

2.3ktokens in Claude Opus 5.5

1.2 %of Claude's 200k window

0.9×the median server

1.9 sto initialize

4 msto list tools

Run it: uvx tether-memory@0.6.1 (stdio, probed in a container with the network off)
Host: pypi.org
Reports itself as: tether
Capabilities: prompts, resources, tools
Instructions: none
Of a 1M window: 0.2 % of a 1M context window
Count: 2.3k tokens in Claude Opus 5.5, exact, measured 2026-10-27. With the Claude Code prefix mcp__…__ on each tool name: 2.3k. The o200k_base estimate is 1.4k. Counted again when the tool definitions change. Method.
Repository: https://github.com/sidyellur/tether
Website: https://github.com/sidyellur/tether
Registry: active, updated 2026-09-07 · registry entry
Changes: 2 recorded, reachable in 2 of them. A row is added when the result, the tool count or the cost changes.

Most expensive tools

The Claude column scales the o200k estimate of each tool by this server's ratio of exact to estimate, 1.61×.

Tool	≈ Claude tokens	o200k estimate	Share of this server
recall	1 154	718	50 %
remember	873	543	38 %
forget	177	110	8 %
link	108	67	5 %

Other registry entries on pypi.org, the ones next to this name; all of them.

Servers that mention tether.

We add a row when the result changes. A server with no change keeps its last row.

Probed	Result	Init	Tools	Claude	o200k
2026-10-27 06:59	alive	1.9 s	4	2.3k	1.4k
2026-10-20 06:45	alive	1.9 s	4		1.4k

The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.

Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.