telos-mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TELOS_AGENT_ID | No | The agent ID for TELOS governance. Used to identify the calling agent. |
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| telos_scoreA | Score a proposed agent action against the active Purpose Anchor. Returns a verdict (EXECUTE / CLARIFY / ESCALATE) plus a 6-dimension
score breakdown across purpose, scope, boundary, tool, chain, and
codebase_fidelity. Each call also mints an unsigned integrity-hash
receipt (shared telos-receipt envelope) that Args: action_name: Name of the action being proposed (e.g. "write_file"). action_params: Parameter dict the agent intends to pass to the action. agent_id: Stable identifier of the agent proposing the action. Returns: Dict with keys: verdict, composite_score, scores, agent_id, action_name, receipt, stub, engine. |
| telos_verifyA | Verify an unsigned integrity-hash receipt offline. Recomputes the receipt's integrity hash over its canonical payload using the shared telos-receipt contract -- the same verifier the trust surface runs -- so the answer matches end-to-end. Key-free; not a signature check. Args: receipt_json: The receipt to verify, either as a JSON string or as a JSON object (clients may pass either; both are accepted). Returns: Dict with keys: match (bool), stated_integrity_hash, recomputed_integrity_hash, covered_fields, signing_status, note, reason. |
| telos_get_paA | Return the active Purpose Anchor for an agent. The PA is the governance contract: purpose statement, hard boundaries, declared scope, allowed tool list, and the centroid dimensions used to score the agent's actions. Args: agent_id: Stable identifier of the agent whose PA to load. Returns: Dict with keys: agent_id, pa_id, purpose, boundaries, scope, allowed_tools, centroid_dimensions, compiled_at, stub. |
| telos_auditA | Return audit chain entries within a time window. Capped at 100 entries to keep MCP payloads bounded. For deeper queries,
use the Args: start_iso: ISO-8601 window start (e.g. "2026-04-25T00:00:00Z"). end_iso: ISO-8601 window end (must be later than start). Returns: Dict with keys: entries (list, max 100), count, capped (bool), window {start, end}. |
| telos_replayA | Queue a CCRS counterfactual replay against an alternate config. CCRS Mode C re-runs the lifecycle that produced Args: receipt_id: ID of the receipt to replay against. alt_config_path: Path to the alternate config (YAML) to apply. Returns: Dict with keys: job_id, receipt_id, alt_config_path, status, queued_at, estimated_runtime_seconds, result_uri, stub. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| governance_review | User-invokable: have the model review a proposed action for governance fit. |
| audit_walkthrough | User-invokable: walk through the audit chain in a date window. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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