io.github.1picassoai/sticky

sticky

Is the io.github.1picassoai/sticky MCP server down? No. It answered initialize and tools/list in the probe of 2026-11-01.

Persistent memory and context for your agent, on a board you can see. Capped, so it stays small.

alive probed 2026-11-14 · unchanged since 2026-11-01

2tools

365tokens in Claude

0.2 %of Claude's 200k window

0.1×the median server

66 msto initialize

3 msto list tools

Run it: npx -y sticky-mcp@0.2.2 (stdio, probed in a container with the network off)
Host: npmjs.com
Reports itself as: sticky 0.1.0
Capabilities: tools
Instructions: 158 characters
Of a 1M window: <0.1 % of a 1M context window
Count: 365 tokens in Claude, exact, measured 2026-10-25. With the Claude Code prefix mcp__…__ on each tool name: 381. The o200k_base estimate is 232. Counted again when the tool definitions change. Method.
Repository: https://github.com/1picassoai/sticky
Website: https://juvina.ai
Registry: active, updated 2026-09-08 · 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.57×.

Tool	≈ Claude tokens	o200k estimate	Share of this server
post_sticky	263	167	72 %
read_active_stickies	102	65	28 %

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

Servers that mention sticky.

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-25 06:51	alive	197 ms	2	365	232
2026-10-18 06:38	alive	66 ms	2		232

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.