Engraphy runs on your own machine — the client starts it, so there is no endpoint to ping.
Self-hosted MCP memory server: a typed knowledge graph on Postgres 16 and pgvector.
Nothing serious here today
Today is the operative word: we check Engraphy every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.
Alternatives to Engraphy
same job, measured the same waySelf-hosted semantic memory over MCP for an engineering team's tacit knowledge. Needs Postgres.
Self-hosted, source-traceable memory layer and MCP server for AI agents, on your own Postgres.
A label property graph on SQLite/Postgres with multi-ontology routing and a gated MCP server.
Local-first AI memory layer with hybrid search. Postgres + pgvector. Self-hosted, MIT.
Enterprise PostgreSQL MCP server with NL queries, hybrid search (pgvector+BM25), and web UI
Persistent local AI memory. SQLite + FTS5 + vector search, knowledge graph. No cloud, no API keys.
SQLite-backed MCP server for persistent memory, full-text retrieval, and graph traversal.
Embedded memory for AI agents with SQLite, pgvector, and Neo4j graph search.
Engraphy — questions
Answers built from our own checks of this server.