Assertion Memory

Ingested from the official MCP Registry

FastDrop pulled this entry from the official MCP Registry as io.github.Assertion-AI/assertion and probed the endpoint. The maker did not submit it, so the outbound link is not endorsed and the description is not theirs.

If this is your server, claim the listing to edit it and take ownership. The registry index lists everything else still awaiting a probe.

Tools this endpoint exposes

Read directly from the endpoint on 25 Sept 2026. Not supplied by the maker.

• recall

  Look up what's known about a topic from prior work. Substring match on a keyword across all claims and evidence; returns up to 20 hits. Use literal terms first; if no hits, try synonyms.

• expand

  Return the sub-claims directly supporting a given claim. Pass a node id (e.g. 'n0042') returned by a prior recall.

• evidence

  Return the raw quote, code snippet, or specific value backing a claim. Pass a node id.

• conflicts

  List open memory conflicts — pairs of stored claims that contradict each other and are awaiting the user's decision. Returns each conflict's id plus both claims (claim_a / claim_b) and their node ids.

• resolve

  Resolve an open memory conflict AFTER the user says which claim is correct. Pass the conflict id and `winner` = the node id of the correct claim. The losing claim is then rewritten (or removed) so the

• superseded

  List recently superseded (tombstoned) claims — what conflict resolution / the sweep retired, with the claim that replaced each. Use to audit auto-resolutions; anything wrong can be reverted with `unsu

• unsupersede

  Undo a supersession — bring a tombstoned claim back into active views. Pass the node id (from `superseded`).

• list_spaces

  List the user's memory workspaces: their personal tree, the team spaces they belong to, which one is the default for new sessions, and (if known) which one THIS session is pinned to. Use when the user

Is this tool yours?

Claim this listing and we’ll verify ownership before handing it over.