Project Telos
Related Servers
Alternatives to Project Telos
No user-submitted related servers found.
Related Servers
AlicenseNot gradedqualityAmaintenanceEnables AI assistants to run local-first operations checks, review evidence, and manage durable tickets in a SQLite-backed ledger through self-describing MCP tools.MIT
telos-mcpofficial
AlicenseAqualityBmaintenanceExposes TELOS governance primitives—action scoring, receipt verification, Purpose Anchor inspection, audit-chain queries, and CCRS counterfactual replay—as MCP tools, resources, and prompts for any MCP-compatible client.5Apache 2.0- AlicenseNot gradedqualityBmaintenanceEnables AI agents such as Claude, Gemini, and a headless Runner to post, list, claim, report, and defer work on a single shared board through seven MCP tools. Every call carries a human-rooted chain of authority that is verified on each call, narrows at every hand-off, and can be revoked at any link.Apache 2.0
- AlicenseNot gradedqualityBmaintenanceSecure, local-first collaboration layer for AI agent teams, enabling authenticated agent-to-agent communication, shared memory with provenance, and scoped service execution through MCP.Apache 2.0
- AlicenseAqualityBmaintenanceRetired snapshot of the former 15-tool Apache-2.0 beta. Use Living Stack Community for the free seven-tool proof edition; Complete Local is the paid runtime with memory, recovery, signed traces, release verification, and multi-agent workflows.14Apache 2.0
- FlicenseNot gradedqualityCmaintenanceA local-first MCP server stub that exposes provisioning tools for converting ecological intent into work packets, proof plans, receipts, and validation workflows.-
TDQS
Scored across 50 tools
Each tool has a specific 'Use when' target, but with 50 tools across repeated families such as doctor, proof, research, context, and learning, boundaries blur. Choosing among telos.doctor, telos.operator.doctor, domain-specific doctors, and various proof/convention packets requires careful description reading, making misselection likely.
Names uniformly follow a lowercase dotted telos.<domain>.<noun> hierarchy with no camelCase/snake_case mixing. The convention is predictable throughout, even though it is noun-oriented rather than verb_noun.
50 tools is far beyond the typical 3-15 range and creates a heavy selection surface even for a broad Telos workbench. Many tools are narrow diagnostic, proof, or convention variants, so the count feels inflated rather than well-scoped.
The read-only Telos workbench surface covers many domains—status, diagnostics, proofs, reach/crawl, research, rendering, context, CI, accessibility—so it is broad and hard to call incomplete. However, it contains no mutating, promotion, or execution operations, and several workflows end at queues/registries/receipts, leaving minor dead ends.