Clearon Content Archive MCP
Clearon Content Archive MCP
用于仅追加内容记录、已验证发布历史、社交媒体后续跟进以及便于检索的元数据的 MCP 服务器。
它旨在保留来源信息和工作流状态,而自身不发布任何内容。
它能做什么
按 slug 存储仅追加的内容事件。
维护物化快照以支持快速读取。
记录已验证的 WordPress 和社交媒体结果。
在不重写早期历史的情况下跟踪来源修正。
提供重叠搜索、清单和后续跟进报告。
验证事件历史是否与存储的快照完全匹配。
Related MCP server: tatastu-proof
它不能做什么
不向 WordPress 或社交平台发布内容。
不将标记为
publish的载荷视为已实际发布的证明。不做法律或编辑层面的真相判定。
不允许工件路径超出配置的工作区。
环境要求
Node.js
20或更高版本能够启动 stdio 服务器的本地 MCP 客户端
安装
cd tools/clearon-content-archive-mcp
npm install
npm test
npm run smokeMCP 客户端配置
stdio 配置示例:
{
"mcpServers": {
"clearon-content-archive": {
"command": "node",
"args": ["/absolute/path/to/clearon-content-archive-mcp/server.mjs"],
"env": {
"CLEARON_CONTENT_ARCHIVE_WORKSPACE": "/absolute/path/to/workspace"
}
}
}
}使用 CLEARON_CONTENT_ARCHIVE_WORKSPACE 定义用于验证本地工件路径的根目录。使用 CLEARON_CONTENT_ARCHIVE_ROOT 覆盖归档存储位置。
存储
默认情况下,归档数据存储在仓库之外的用户数据目录中:
macOS:
~/Library/Application Support/clearon-content-archive-mcp/content-archiveLinux:
${XDG_DATA_HOME:-~/.local/share}/clearon-content-archive-mcp/content-archiveWindows:
%APPDATA%\\clearon-content-archive-mcp\\content-archive
每条记录位于 records/<slug>/ 下,并存储:
events.jsonlsnapshot.json
验证与修复
verify_archive_record 是只读操作。它将重建的事件历史与存储的快照进行比较,并报告它们是否匹配。
自动修复仅用于需要在追加新事件之前从之前的部分写入中恢复的变更路径。
包审计 CLI 为:
npm run audit它会明确报告验证失败,而不是静默跳过。
推荐工作流
注册本地草稿包。
追加已验证的发布或更新结果。
追加 LinkedIn 和 X 的结果,包括阻塞项或跳过项。
将来源修正记录为新事件。
在起草相关工作之前使用重叠和搜索工具。
在审计期间使用清单和不完整后续跟进输出。
在迁移、手动恢复或疑似损坏后运行验证。
工具
get_server_healthregister_content_packageget_content_recordsearch_content_archivefind_content_recordupdate_content_artifactsrecord_publicationrecord_social_resultrecord_source_correctionapprove_voice_examplecompare_payload_to_live_statefind_content_overlaplist_incomplete_follow_throughlist_update_candidatesgenerate_content_inventoryverify_archive_record
URL 处理
存储的 URL 必须使用 http 或 https,且包含凭据的 URL 会被拒绝。
由于归档历史是仅追加的,请避免写入在查询字符串中包含令牌或其他机密的敏感 URL。
开发
npm test
npm run smoke
npm run syntax
npm run auditMaintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Servers
- AlicenseAqualityCmaintenancePrimary purpose is to maintain a self verifying ledger that requires no consesus. Additional features include support for evm compatible and other block chains.6121MIT
- AlicenseNot gradedqualityBmaintenanceEnables creating and verifying permanent, publicly verifiable content provenance stamps via MCP tools.8MIT
- AlicenseNot gradedqualityBmaintenanceEnables defining and verifying evidence contracts for claims in READMEs, releases, or product pages using constrained verifiers and generating hash-chained receipts and reports.10MIT
- FlicenseAqualityCmaintenanceProvides cryptographic truth infrastructure for AI agents, enabling them to seal content with SHA-256 and Ed25519, verify receipts, anchor them to Bitcoin via OpenTimestamps, generate citations, and audit chains of receipts.5
Related MCP Connectors
Stamp content with permanent, verifiable provenance. Hash locally, verify free forever.
Read-only XRP Ledger MCP tools with proof-annotation envelopes and signed daily snapshots.
Source-first URL clone, capture, rebuild, and fidelity verification tools.
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/kwgoodwin/clearon-content-archive-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server