telos-mcp
OfficialClick on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@telos-mcpScore an action 'deploy_contract' for agent-123"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
telos-mcp
Model Context Protocol server for TELOS AI Labs governance.
Exposes TELOS governance primitives -- action scoring, unsigned integrity-hash receipt verification, Purpose Anchor inspection, audit-chain queries, and CCRS counterfactual replay -- as MCP tools, resources, and prompts. Any MCP-compatible client (Claude Desktop, Claude Code, Cursor, Cline, etc.) can call them as native tools.
v0.1 status. This release ships the protocol surface with stubbed engine calls so clients can exercise every tool, resource, and prompt end-to-end without an installed engine. Scores are synthetic and receipts are unsigned integrity-hash receipts (
signature: null,signing_status: "unsigned_integrity_hash"): a key-free SHA-256 over the receipt payload, not a digital signature. v0.2 wires the livetelos-govengine behind the same receipt shape, and a real signature fills the existingsignaturefield then, with no schema break.
What this server exposes
Tools (LLM-callable)
Tool | Purpose |
| Score a proposed action against the active Purpose Anchor. Returns verdict ( |
| Verify an unsigned integrity-hash receipt offline (key-free; not a signature check). Returns |
| Return the active Purpose Anchor: purpose, hard boundaries, declared scope, allowed tools, centroid dimensions. |
| Return audit-chain entries within a time window (capped at 100). |
| Queue a CCRS counterfactual replay against an alternate config; returns a |
Resources (LLM-readable)
URI template | Returns |
| A TELOS governance wiki page by relative path. |
| Compiled centroid metadata for one of |
| The audit-chain segment for a given |
Prompts (user-invokable templates)
Prompt | Purpose |
| Have the model review a proposed action for governance compliance. |
| Walk through the audit chain in a date window. |
Related MCP server: aman-mcp
Install
pip install telos-mcpThe live engine (telos-gov) lands in v0.2, after the clean-facade
republish. v0.1 ships no installable engine extra; the stub is the only
supported engine. (telos-mcp[engine] returns in v0.2 pinned to the
republished clean facade.)
The package installs a telos-mcp console script that starts the server
over stdio. You can also invoke it via python -m telos_mcp.server.
Requires Python 3.10+.
Client configuration
Each client below assumes telos-mcp is installed in a Python environment
on PATH. If you prefer not to install globally, use uvx telos-mcp or
substitute the absolute path to the telos-mcp script in the snippets.
Claude Desktop
Edit ~/Library/Application Support/Claude/claude_desktop_config.json
(macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows). Add
the telos-governance entry under mcpServers:
{
"mcpServers": {
"telos-governance": {
"command": "telos-mcp",
"args": [],
"env": {
"TELOS_AGENT_ID": "claude-desktop-default"
}
}
}
}Restart Claude Desktop. The five telos_* tools should appear in the
MCP tool tray.
Claude Code
Use the claude mcp add CLI:
claude mcp add telos-governance -- telos-mcpOr edit ~/.config/claude-code/mcp_servers.json directly:
{
"telos-governance": {
"command": "telos-mcp",
"args": []
}
}Cursor
Edit ~/.cursor/mcp.json (global) or .cursor/mcp.json (per-project):
{
"mcpServers": {
"telos-governance": {
"command": "telos-mcp",
"args": [],
"env": {
"TELOS_AGENT_ID": "cursor-default"
}
}
}
}Cline (VS Code extension)
Open Cline -> MCP Servers -> Edit Configuration. Add:
{
"mcpServers": {
"telos-governance": {
"command": "telos-mcp",
"args": [],
"transportType": "stdio"
}
}
}Verifying the install
From any client, ask:
Use the
telos_get_patool withagent_id="test"and show the Purpose Anchor.
You should see a stub PA back containing "stub": true and the six
canonical centroid dimensions.
Development
git clone https://github.com/TELOS-Labs-AI/telos-mcp
cd telos-mcp
python -m venv .venv && source .venv/bin/activate
pip install -e ".[dev]"
# Run the server over stdio (what MCP clients spawn):
python -m telos_mcp.server
# Or use the MCP Inspector for interactive exploration:
mcp dev telos_mcp/server.pyRoadmap
v0.1 (this release) -- protocol surface complete, engine stubbed, registry-submission-ready manifest.
v0.2 -- swap stubs for live
telos-govcalls (after the clean-facade republish). Receipts gain a real signature after the signing ceremony, filling the existingsignaturefield with no schema break.telos-govbecomes a hard dependency.v0.3 -- streaming audit subscriptions, per-tenant PA selection via
TELOS_TENANTenv, optional HTTP transport.
License
Apache-2.0. See LICENSE.
Links
TELOS AI Labs: https://telos-labs.ai
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
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/TELOS-Labs-AI/telos-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server