Marrow
OfficialRelated Servers
Alternatives to Marrow
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceUniversal governance layer for AI agents — MCP-native, fail-closed, LNN interpretability. Governed receipts, IPFS audit proofs, and rollback for any agent in any framework.356 npmApache 2.0
- AlicenseNot gradedqualityAmaintenanceServer-enforced workflow discipline for AI agents. An MCP server providing persistent work items, dependency graphs, quality gates, and actor attribution. Schemas define what agents must produce — the server blocks the call if they don't. Works with any MCP-compatible client.204MIT
- AlicenseNot gradedqualityAmaintenanceUniversal 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.28Apache 2.0
- FlicenseNot gradedqualityCmaintenanceMCP server that enforces governance on agentic decisions with auditable evidence records, providing tools for understanding, calibrating confidence, and navigating handoffs based on policy.1-
- AlicenseNot gradedqualityCmaintenanceLocal-first MCP Work Model for coding agents: retrieves scored memory, records commitments, and credits outcomes from tests, reviews, replies, or owner approval. Public repo includes Apache-2.0 integration glue; the local engine binary is proprietary.7Apache 2.0
- AlicenseBqualityBmaintenanceA governance proxy for AI tools — every MCP/agent tool call is policy-gated, secret-redacted, and written to a hash-chained, offline-verifiable audit trail.13MIT
TDQS
Scored across 56 tools
Many tools have overlapping purposes. For example, marrow_orient, marrow_think, marrow_decision_brief, marrow_agent_runtime, and marrow_workflow_gate all provide pre-action guidance and risk assessment. Similarly, multiple tools report value/proof (marrow_value_report, marrow_buyer_proof, marrow_agent_performance, marrow_dashboard), making it challenging to select the correct tool.
All tools share the 'marrow_' prefix, and many follow a verb_noun pattern (e.g., list_memories, get_memory, update_memory). However, deviations like marrow_orient, marrow_think, marrow_auto, and marrow_buyer_proof break the pattern, creating noticeable inconsistency.
With 56 tools, the server is heavily over-scoped. The high count leads to redundancy and visual clutter, making it difficult for agents to discover and choose tools efficiently. A more focused set of 15-20 tools would better serve the platform's purpose.
The tool set provides broad lifecycle coverage across memories (create/read/update/delete/supersede/export/import), keys (create/rotate/revoke/list/get), handoffs (create/update/status), workflows (register/start/advance/list/get/instances), and policies (create/update/assign/resolve). Minor gaps like workflow cancellation or explicit key update are present but workable.