YantrikDB MCP
MCP server exposing YantrikDB's recall/remember/think/graph to any agent.
https://yantrikdb.com/mcpverification
L1Ownership verified · GitHub repo admin: yantrikos/yantrikdb-mcp
Ownership verified — not quality endorsement. icantmarket verifies control of listed assets only. last rechecked 9/3/2026.
stars
24
forks
8
created
Mar 2026
pushed
Sep 2026
active ask · launch
Trying to nail the tool descriptions. Agent planners route by description prose — the difference between a tool that gets called and one that gets ignored is usually one good sentence. Pick any of the 7 tools at the README and tell me whether the description tells you when to use it.
- Looking for:
- Anyone who has written or debugged MCP servers, or who runs MCP-equipped agents daily. Strong bonus if you have shipped a published MCP server.
- Time:
- 15m
- In return:
- I will review tool descriptions on your MCP server with the same lens — when-to-use clarity, failure-mode honesty, sensible defaults.
- Closes:
- 6/16/2026
Success means: I have one specific tool description to rewrite based on the helpers feedback.
Posts · 1
Recent activity · 5
GitHub releases · PyPI downloads · npm versions
- release
Admits engine 0.23.x (pin `yantrikdb>=0.15.4,<0.24.0`); registry manifest 0.24.0. - New `atlas` tool (#44): exports the server's own store with the engine's packaged Memory Atlas exporter (`yantrikdb
github releases · 9/14/2026, 5:15:01 AM
- release
v0.23.0 — engine 0.22.x admitted; store probe in a child process
Engine pin `yantrikdb>=0.15.4,<0.23.0` (was `<0.22.0`). Engine 0.22.0 brings the claim-chain eligibility gate (opens in `shadow`: results unchanged, counters in `stats`), occurrence-local relation bi
github releases · 9/7/2026, 10:15:02 PM
- release
v0.22.0 — engine 0.21.x admitted
## v0.22.0 — engine 0.21.x admitted Engine pin `yantrikdb>=0.15.4,<0.22.0`. No server code change. Engine 0.21.0 is additive (schema v52): the store learns its own lexicon, so a sentence-initial com
github releases · 9/6/2026, 7:15:02 PM
- release
v0.21.0 — remember(event_time=...): the temporal tag at ingestion
## v0.21.0 — remember(event_time=...): the temporal tag at ingestion Engine pin `yantrikdb>=0.15.4,<0.21.0` (engine 0.20.x admitted). - `remember(event_time=...)`: when the memory is ABOUT, not when
github releases · 9/6/2026, 9:15:01 AM
- release
v0.20.0 — remember(claims=...): state the facts you want tracked
## v0.20.0 — remember(claims=...): state the facts you want tracked Engine pin `yantrikdb>=0.15.4,<0.20.0` (engine 0.19.x admitted). - `remember(text=..., claims=[{"subject", "relation", "object"},
github releases · 9/6/2026, 6:15:01 AM
Audit log · 5
Public · append-only
- 9/3/2026, 4:00:02 AMreverifiedtrust=L1
- 8/3/2026, 4:00:02 AMreverifiedtrust=L1
- 7/3/2026, 4:00:02 AMreverifiedtrust=L1
- 6/2/2026, 6:42:20 AMverifiedtrust=L1
- 6/2/2026, 6:42:20 AMclaimedtrust=L1