CodeRoot-Authoring-MCP
OfficialRelated Servers
Alternatives to CodeRoot-Authoring-MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables agents and gateways to seal each action into a tamper-evident W3C PROV record backed by a signed Merkle transparency log, and to fetch tree heads, inclusion and consistency proofs, verify records, and trace artifact lineage through six typed MCP tools.Apache 2.0
- AlicenseNot gradedqualityBmaintenanceLocal-first, MCP-first cross-agent cognitive asset layer that enables agents to store, retrieve, govern, and migrate memory, roles, and verified skills as portable assets via MCP tools and SQLite.1Apache 2.0
- AlicenseAqualityBmaintenanceEnables AI agents to store and retrieve provenance-aware facts with source, age, and boundaries, supporting search, read, propose, and local telemetry via MCP tools.426 npmApache 2.0
- FlicenseNot gradedqualityBmaintenanceEnables coding agents to run bounded local profiling, tracing, benchmarking, and capture operations from explicit artifacts or commands, then inspect typed evidence, provenance, coverage, limitations, and preserved replay sources through MCP tools.-

CarpeOS MCP Serverofficial
AlicenseNot gradedqualityAmaintenanceEnables AI agents to capture, search, and manage structured memory from agent sessions with append-only events and provenance tracking, providing eight local MCP stdio tools.1Apache 2.0- AlicenseNot gradedqualityCmaintenanceEnables autonomous multi-agent workflows to capture, preserve, and retrieve immutable transcripts and atomic memory cards through a local MCP server, providing tools for forensic search, topic mapping, and structured fact access without losing context fidelity.1MIT
TDQS
Scored across 4 tools
Each tool has a clearly distinct role: schema retrieval, fact recording, record reading, and finalization. There is no functional overlap, and the descriptions explicitly delineate boundaries (e.g., record_facts vs. finalize_record).
All tool names follow a consistent verb_noun pattern (get_, record_, read_, finalize_). The naming is predictable and unambiguous, with no mix of conventions.
Four tools is an appropriate size for a focused authoring workflow. Each tool serves a necessary, non-redundant function, and the count falls well within the ideal 3-15 range.
The tool set covers the complete lifecycle of an asset record: reading the schema, recording facts, reading the current state, and finalizing with author confirmation. No obvious dead ends or missing operations for the stated purpose.