Eclipse Beacon MCP
OfficialRelated Servers
Alternatives to Eclipse Beacon MCP
No user-submitted related servers found.
Related Servers
- AlicenseBqualityCmaintenanceEnables users to maintain append-only content history with verified publication and social follow-through outcomes, search for overlaps, and run read-only integrity verification of stored snapshots.16MIT
- AlicenseNot gradedqualityFmaintenanceEnables defining and verifying evidence contracts for claims in READMEs, releases, or product pages using constrained verifiers and generating hash-chained receipts and reports.3 npmMIT
- AlicenseNot gradedqualityBmaintenanceIssue and verify signed receipts for agent actions, enabling durable, independently checkable proof of policy decisions. Supports offline verification via get_keyset and verify_receipt tools without an account.0Inno Setup
- AlicenseNot gradedqualityAmaintenanceEnables agents and applications to record, query, verify, and receive hash-chained event provenance over stdio, supporting self-metering and independent audit of autonomous system activity.6MIT
- AlicenseNot gradedqualityBmaintenanceProvides permission gates and tamper-evident audit logging for AI agent tool executions, with declarative policies, consent ladders, and hash-chained verification.MIT
- AlicenseBqualityCmaintenanceEnables software agents to maintain a signed, evidence-aware local ledger of claims, with policy-gated proposals, conflict queries, and constitution-pinned access through an MCP stdio server.73Apache 2.0
TDQS
Scored across 5 tools
Each tool maps to a clearly distinct operation: write-side ingestion (policy_ingest), read-side retrieval (policy_list / policy_get), and two analytical views (time-based expiry in radar_report vs coverage gaps in gap_report). The two report tools could superficially overlap, but their descriptions explicitly separate temporal alerts from coverage/duplication/premium analysis.
All names are snake_case two-token identifiers, which is easy to read and predict. There is a minor deviation in that policy_* uses a resource prefix with an action second (ingest/list/get), while radar_report and gap_report are noun+report compounds rather than strict verb_noun.
Five tools is well within a focused, well-scoped surface: one write path, two retrieval paths, and two distinct analyses. No tool looks redundant or padded, and nothing appears to be a trivial wrapper.
Ingest plus list/get covers creation and reading, but there is no explicit update, delete, or archive path for policies, assets, or persons (re-ingestion is implied but undocumented as an edit mechanism). There is also no way to acknowledge/snooze alerts or export the household graph, leaving notable lifecycle gaps.