kremis_ingestLABSCO SUMMARY
Absence is an answer here, and it comes with a proof.
Ask about something never ingested and you get an explicit not-found — and the certify tool will hand you a certificate of that absence, re-derivable offline against the graph's BLAKE3 state hash. Same input, same output: no randomness and no floating-point arithmetic in the core, with ACID persistence underneath.
What it is
A deterministic graph engine written in Rust, with an MCP bridge. It starts empty, every node comes from a signal you ingested, and a missing fact returns an explicit not-found rather than a plausible guess.
What you get
kremis_ingest— record an entity, attribute and value, or a relationship between two entitieskremis_lookupandkremis_properties— a node by id, and all of its propertieskremis_traverse— walk out from a node to a depth (default 2, maximum 100), optionally keeping only thetop_khighest-weight edgeskremis_pathfor the strongest path between two nodes, andkremis_intersectfor the nodes connected to all of several inputskremis_retract— decrement an edge's weight, floored at 0kremis_statusfor node count, edge count and density;kremis_hashfor the canonical BLAKE3 hash of the whole graph statekremis_certify— a Verifiable Query Certificate carrying the verdict, the canonical state hash, and a base64 proof a third party re-derives offline, including proof that something is absent
Requirements
Rust 1.89+ and Cargo. A release build produces kremis — the CLI and HTTP server — and kremis-mcp, the MCP server; the Docker image runs the MCP server by default. KREMIS_URL points the bridge at the HTTP server, defaulting to http://localhost:8080. KREMIS_API_KEY enables bearer authentication and KREMIS_RATE_LIMIT defaults to 100. Marked alpha: breaking changes are possible before v1.0.
Setup effort
Run a container — build the image from the repository, then point your client at it
USE CASES
01
Giving an agent facts it cannot embellish
Ingest what is true; anything not ingested comes back as not-found rather than as a confident invention.
02
Finding how two things are connected
Ask for the strongest path between them, or for what they have in common with a third.
03
Proving a fact to someone outside the loop
Produce a certificate they re-derive offline against the graph's state hash, without access to your system.
04
Weakening a link that turned out to be wrong
Decrement the edge instead of deleting history — the weight floors at 0 rather than going negative.
10 tools
Listed in project docs. Your client may show a different list.
kremis_lookupkremis_traversekremis_pathkremis_intersectkremis_statuskremis_propertieskremis_retractkremis_hashkremis_certifyBEFORE YOU INSTALL
What to know first
Tools you get
10 tools named in the project's documentation.
Requires
docker on PATH
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
Build the image from the repository, then point your client at it.
Server setup
TERMINAL
git clone https://github.com/TyKolt/kremis.git
cd kremis
docker build -t kremis .Add the configuration under MCP Clients to your client; it runs the image with docker run -i --rm kremis
MCP Clients
Any MCP client
ANY MCP CLIENT · JSON
{
"mcpServers": {
"docker": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"kremis"
]
}
}
}
