Stellar Jay
Related Servers
Alternatives to Stellar Jay
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceOpen-source, self-hosted database and workspace for AI agents. Its MCP server lets agents manage structured records, documents, files, reusable skills, and apps, with auditable Change Requests for writes.729MIT
- AlicenseNot gradedqualityBmaintenanceGives AI agents a shared, self-hosted memory of the people, companies and deals a business works with, letting them log interactions and read back typed fields and provenance-linked facts. Fields and objects can be extended at runtime, and everything is reachable over MCP or a REST API with no UI involved.26 npmAGPL 3.0
- AlicenseAqualityBmaintenanceUniversal verifiable recovery for long-running AI agents with semantic checkpoints, idempotent action ledger and hash chained log as a deny by default MCP server. Framework agnostic with adapters for LangGraph, LangChain and OpenAI plus gateway and OTel.1326Apache 2.0
- AlicenseBqualityBmaintenanceFree, open-source (MIT), local-first Swiss accounting MCP server: an AI agent posts double-entry journal entries, categorises and chases invoices, and prepares the MWST-Abrechnung (the Swiss VAT return), with a minimalist Studio for human oversight. Posted entries are append-only and immutable, corrections are reversing entries, and every query is tenant-scoped.500118 npm1MIT
- AlicenseAqualityBmaintenanceAuditable long-term memory for coding agents: facts carry their evidence and full supersession history, so why explains where a belief came from and forget retires instead of deleting. Runs embedded on a keyless SQLite store (npx -y statecore-mcp) with optional LLM distillation and a self-hosted StateCore server mode.644 npm1MIT
- AlicenseNot gradedqualityBmaintenanceProvides AI agents with shared communication and persistent state over HTTP and MCP, letting an agent save its progress, search and reuse other agents' prior work, coordinate tasks in shared spaces, exchange direct messages, and hand its role to a successor when a session ends. State is kept on PostgreSQL with signed, append-only records that anyone can verify.Business Source 1.1
TDQS
Scored across 8 tools
Each tool targets a distinct operation: status for health, record/correct/retract for the three fact-mutation paths, get_entity for reads, list_changes for auditing, undo_changes for reversal, and save_checkpoint for snapshots. The record/correct/retract trio is cleanly separated by intent (new value vs. replacement vs. no replacement), so there is no realistic misselection risk.
Most tools follow a clear verb_noun pattern (record_fact, correct_fact, retract_fact, get_entity, list_changes, undo_changes, save_checkpoint). The lone outlier is 'status,' a bare noun, but the deviation is minor and does not impair readability.
Eight tools map neatly onto the fact-store lifecycle with no redundant or filler entries. The count is well within the ideal range for a focused append-only fact/audit service.
The surface covers the full fact lifecycle (record, correct, retract), reading current state, auditing changes, bulk undo, checkpointing, and health. The only soft gap is the absence of a way to list or restore named checkpoints explicitly, which agents can largely work around by re-saving by name.