Marrow
OfficialRelated Servers
Alternatives to Marrow
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceMCP server for governing agent actions: an agent can propose a retry but cannot approve it itself. Deterministic policy allows, holds or refuses each typed action, a held action needs a single-use human approval none of the tools can create, and every run leaves a verifiable receipt.1MIT
- AlicenseAqualityDmaintenanceUniversal governance layer for AI agents — MCP-native, fail-closed, LNN interpretability. Governed receipts, IPFS audit proofs, and rollback for any agent in any framework.379 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.207MIT
- FlicenseNot gradedqualityBmaintenanceEnables autonomous agents and MCP-compatible clients to enforce policy-approved actions using risk tiers, reversible checkpoints, and token approval bounds.7-
- FlicenseNot gradedqualityAmaintenanceEnables AI agents to execute real-world API actions with exactly-once reliability, deduplication, auditing, and human-in-the-loop safeguards via MCP.2-
- 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.23Apache 2.0
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.