ai ml workflow/launched

YantrikDB MCP

MCP server exposing YantrikDB's recall/remember/think/graph to any agent.

https://yantrikdb.com/mcp

Share

XRedditHNLinkedInFacebook

Instagram has no web-share URL. On mobile use the Share… button — the OS share sheet covers Instagram + WhatsApp + iMessage + others.

verification

L1

Ownership verified · GitHub repo admin: yantrikos/yantrikdb-mcp

Ownership verified — not quality endorsement. icantmarket verifies control of listed assets only. last rechecked 8/3/2026.

stars

24

forks

7

created

Mar 2026

pushed

Aug 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

    v0.19.5 — recall(order=...) actually orders

    ## Fixed `recall(order="recency")` returned relevance order. Verified on a live store: the ordered and unordered calls came back **byte-identical** — same rids, same sequence, same scores — and that

    github releases · 8/26/2026, 7:15:01 AM

  • release

    v0.19.4 — engine 0.18.x admitted

    Pin `yantrikdb>=0.15.4,<0.19.0` (was `<0.18.0`). No MCP tool change in this release; the pin lift is the whole delta. Engine 0.18.0 is additive — the pack substrate (structured `hit["pack"]` provenan

    github releases · 8/26/2026, 5:15:01 AM

  • release

    v0.19.3 — engine 0.16.x and 0.17.x admitted; mcp 2.1.x compat probe

    - **Engine ceiling widened to `<0.18.0`** — admits yantrikdb 0.16.x and 0.17.x (floor unchanged at 0.15.4). Verified with the full suite on engine 0.16.0 and 0.17.0 (Windows + Linux), a normal-resolut

    github releases · 8/25/2026, 10:15:02 PM

  • release

    v0.19.2 — engine floor 0.15.3: retrieval correctness, not a feature

    The ceiling already admitted 0.15.3. The **floor** is the claim that matters: engine 0.15.0–0.15.2 carry three ranking defects and four cutover races, so a floor that still admits them is a floor we k

    github releases · 8/18/2026, 7:15:02 AM

  • release

    v0.19.1 — the reminder rides the response

    The calling LLM is the only scheduler a reactive deployment has — so maintenance debt now surfaces in the tool responses themselves, instead of waiting indefinitely to be asked. - **remember()**: cro

    github releases · 8/17/2026, 5:15:02 AM

Audit log · 4

Public · append-only

  • 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