Clearon Content Archive MCP
Related Servers
Alternatives to Clearon Content Archive MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables users to create frozen, auditable snapshots of selected Markdown or text-layer PDFs and perform read-only, verifiable local searches with SQLite FTS5/BM25, preserving source hashes, schemas, and page/line anchors.82Apache 2.0
- AlicenseBqualityBmaintenanceEnables canonical social content packages to be ingested, adapted into platform-native variants with classified diffs, and bound to hash-verified owner approvals. It also evaluates engagement policy, tracks accounts and kill switches, and records hash-chained receipts without performing platform actions or network calls.15MIT
- AlicenseNot gradedqualityCmaintenanceEnables capturing web evidence, freezing content-addressed snapshots, and comparing research agents on the same sources with traceable access and quotations.1MIT
- AlicenseBqualityCmaintenanceEnables deterministic RSS 2.0 feed publishing and lifecycle management, including immutable entry IDs, corrections, retractions, archiving, content-addressed media assets, and semantic search over active entries.16MIT
- AlicenseAqualityCmaintenanceEnables privacy-aware, deterministic, read-only chat analysis through tools for briefs, aggregate interaction signals, evidence-aware claim audits, and canonical resource discovery.242MIT
- AlicenseAqualityBmaintenanceEnables drafting once, reviewing per-platform previews and adaptation diffs, approving by content hash, and syndicating approved content to beehiiv/Ghost drafts and Substack paste packs. It also provides provenance-labeled cross-platform analytics and hash-chained receipts while refusing publishing and scraping.6MIT
TDQS
Scored across 16 tools
Most tools target distinct resources and actions, such as searching, exact lookup, and registering content. The main ambiguity is between list_incomplete_follow_through and list_update_candidates, which both surface records needing verification or correction, but their descriptions largely clarify the intended focus.
All tool names use a consistent lower_snake_case verb_noun pattern, such as get_content_record, record_publication, and approve_voice_example. Even the longer compound names like compare_payload_to_live_state and list_incomplete_follow_through follow the same predictable action-first convention.
The server has 16 tools, which is slightly above the typical well-scoped range, but each tool appears to support a distinct archival lifecycle concern. The count is not excessive given the breadth of content, publication, social, correction, and voice-example workflows being covered.
The tool set covers the core content archive lifecycle: register, read, search, update, verify, and append publication/social/correction outcomes. Minor gaps exist, such as no explicit unpublish or approval-revocation tool, but the append-only design and existing verification tools make those acceptable omissions.