Project Telos
This MCP server exposes read-only Telos workbench orientation, diagnostics, proof/context contracts, research registers, web/API reads, and static checks, mostly zero-auth and side-effect-free.
Inspect Telos readiness, status, room summary, catalog, server manifest, MCP freshness, and flagship workflow.
Run local doctor checks for CI, CI failure triage, presentation, accessibility, performance, compatibility, and operator/workbench health.
Read the web and public APIs: fetch one page, crawl a small site, read Reddit listings/comments, X posts/API, Hacker News, GitHub, V2EX, Wikipedia, arXiv, YouTube, and Brave search.
Work with proof and context artifacts: agent-action, research, visual, and build proof packets; context envelopes/packs; action receipts; loop ledgers; admission telemetry; objective monitoring.
Measure caller-provided images with L0-L3 measurement layers and SHA-256 receipts; inspect rendering capabilities, creative engine/kernels, display calibration, and browser evidence fixtures.
Browse research, learning, model-foundry, workstation, revival, and showcase registers, plus native-control capability catalogs without actuating browser/app control through MCP.
Provides WebGL2 renderer capability probes and fallback contracts for Telos Studio surfaces.
Provides WebGPU Gaussian-splat and clustered-forward research prototypes and capability probes for advanced rendering.
Provides receipt-backed research seeds from YouTube educator videos, integrated into the Telos creative engine and research queue.
telos
Telos is a local MCP server and command line for AI agents. It lets an agent read web pages and public APIs, triage a failed GitHub Actions run, check an HTML page for accessibility and size problems, and drive a browser or Windows app once you grant permission from your own terminal.
npx -y project-telos-mcp
Project Telos | gather | crucible | index | forum | telos | learn | emet | buildlang
It is plain Node.js 20+ with no npm dependencies. The npm package is project-telos-mcp. It serves 50 tools over stdio to any MCP host, such as Claude Code, Codex or the OpenAI Agents SDK.
What it does
Reads the web and public APIs.
telos reachand nine MCP tools read pages, feeds and sitemaps, and they follow robots.txt and Crawl-delay. They read Reddit through its official API with your own app, single X posts through X's oEmbed endpoint, and APIs such as Hacker News, GitHub, arXiv and Wikipedia. Each fetch is logged with its URL, time, status and a SHA-256 of the bytes. The crawler reads HTML as served and does not run page JavaScript, so pages behind a login or a bot check come back empty. See the reach guide.Controls a browser or Windows app after you grant it. The CLI drives Chrome through the DevTools Protocol and Windows apps through UI Automation. Each verb has a risk tier. Nothing runs until you issue a grant with
telos grant issue, which needs an interactive terminal, so an agent's own shell cannot grant itself access. Consequential actions also ask for a confirmation each time. Password, OTP and card fields are always refused. App control is Windows only. The MCP tool for this lists the verbs and runs none of them. See the tier spec and the control contract.Logs every gated action. Gated actions and refusals append to a hash-chained log. After
telos keys initthe chain heads are signed with a local ed25519 key, andtelos receipts verify <session.jsonl>finds edited, reordered, inserted or deleted entries.Triages CI.
ci-triage --gh-run owner/repo#run_idreads a GitHub Actions run through theghCLI and says whether it failed on a blocking step or only on warnings, such as a deprecated action runtime. It names the failing step type. It does not diagnose the test.Checks HTML pages.
accessibility-doctor --html FILEruns 14 static checks, including language, viewport, skip link, landmarks, focus style, reduced motion and labels.performance-doctor --html FILEruns 14 byte-budget checks. Neither opens a browser.Writes packets you can verify later.
proof.mjswrites a JSON packet for an agent action, a research claim, a colour measurement or a build invariant, with the inputs embedded.proof.mjs verifyrecomputes the hashes and values and prints MATCH, DRIFT (something changed) or UNVERIFIABLE (an input is missing). Packets are hash-checked and unsigned.
The repo also holds work in progress. The model foundry and learning forge are written contracts and call no model. The causal, embodied and quantum packets are small fixed demos. The creative engine is a set of deterministic image kernels behind demo/index.html. The presentation and operator doctors are tuned to the Project Telos repositories.
Related MCP server: company-mesh
Try it
In an MCP host config, set "command": "npx" with "args": ["-y", "project-telos-mcp"]. A tools/list call against 0.9.0 returns 50 tools.
For the command line, install the package globally. That puts telos and telos-mcp on your PATH. Run telos from the install, not through npx, because the npm name telos belongs to an unrelated package.
npm install -g project-telos-mcp
telos reach doctor
# reach doctor 7/12 channels ready
# web ready free
# reddit needs credentials set REDDIT_CLIENT_ID, REDDIT_CLIENT_SECRET
# ...
telos reach fetch https://example.com
# {"result": {"url": "https://example.com/", "status": 200, "page": {"title": "Example Domain", ...}},
# "receipt": {"fetches": [{"url": "https://example.com/robots.txt", "robots": "robots.txt 404: no restrictions", ...
telos ci-triage --gh-run owner/repo#run_id --summary
# blocking 1
# verdict DRIFT
telos accessibility-doctor --html page.html --summary
# checks 14
# passed 10Without a grant, a control verb is refused before it runs:
telos native-control browser navigate https://example.com
# "status": "REFUSED", "tier": "T3", "executed": false, "reason": "NO_GRANT"To run the demos from source:
git clone https://github.com/HarperZ9/telos.git
cd telos
node demo/run.mjs
# RUN A (normal render) : CERTIFIED recheck=true
# RUN B (broken render) : UNVERIFIABLE recheck=trueFrom a checkout, npm start (the same as node demo/telos-mcp.mjs) runs the stdio MCP server.
demo/run.mjs renders a 4-D cube, recovers its vertex and edge counts from the image, and checks them against the known shape. The second render is too small to read, so it comes back UNVERIFIABLE.
The outputs above come from project-telos-mcp 0.9.0 installed from npm, run on Node 25 on Windows.
How it compares
Playwright MCP and Chrome DevTools MCP cover far more browser verbs. Telos covers fewer, and adds Windows app control, a grant you issue from your own terminal, and a log of each action.
Firecrawl and Jina Reader render JavaScript and run as hosted services.
telos reachruns on your machine, reads HTML as served, and follows robots.txt.Lighthouse and axe-core load the page in a real browser and run far more rules. The Telos doctors are quick static checks on the HTML file.
in-toto and Sigstore sign supply-chain attestations with managed keys and public logs. The Telos action log uses one local key, and its packets are hash-checked without a signature.
Running all five Project Telos servers
node demo/server-manifest.mjs prints host config (Codex TOML, Claude JSON, OpenAI Agents) that launches Telos beside gather, index, forum and crucible, for 78 tools in all plus 38 auxiliary compatibility tools. That setup expects all five repositories checked out side by side, with PROJECT_TELOS_PUBLIC set to their parent folder. The orientation commands:
node demo/catalog.mjs --summary # 78 tools across the five servers
node demo/server-manifest.mjs --summary # launch map with host configExpected catalog summary:
Project Telos MCP Catalog
tools 78 total, 78 available
transport stdio, streamable-http
gather 5 tools ...
index 5 tools ...
forum 5 tools ...
crucible 13 tools ...
telos 50 tools ...Health and state:
node demo/status.mjs --summary
node demo/doctor.mjs --summary
node demo/room.mjs --jsonEach command prints JSON with a MATCH, DRIFT or UNVERIFIABLE status. The package's telos and telos-mcp commands route to the same scripts.
See it work
The animated explainer steps through the cube demo, a proof packet verified from its own contents, and four edits that each come back DRIFT with the failing check named. Its source is docs/explainer/index.html.

A passing check can still be wrong is a 2 min 24 s narrated, captioned film about the same loop. The film page has the transcript and sources.
Proof packets
Write the demo agent-action packet, then verify it from the packet alone:
node demo/proof.mjs agent-action --demo --json > packet.json
node demo/proof.mjs verify packet.jsonOutput from a fresh clone:
verdict MATCH
witness unavailable / UNVERIFIABLEEdit the packet and verify again, and the changed fields are named:
$ node demo/proof.mjs verify edited.json
packet_hash_mismatch (DRIFT)
artifact_digest_mismatch (DRIFT) outputs[0].digest
embedded_verdict_not_derived (DRIFT)The witness line is a second check by emet. Telos looks for it in a sibling ../emet checkout or at TELOS_EMET_CLI. With emet present the line reads witnessed / MATCH. The witness can lower a verdict and never raises one.
The packet holds source refs, context refs, route, admission decision, side effects and output digests. The verifier recomputes the digests from the embedded inputs, so editing any of those fields gives DRIFT, and a missing input gives UNVERIFIABLE with its path. The verdict is computed from the checks, so a MATCH written into the packet has no effect. The other packet types work the same way: research recomputes source digests, visual recomputes colour and luminance from embedded sRGB samples, and build checks a conserved quantity against a fixture that must break it. Details are in docs/PROOF-LANES.md.
Command surface
node demo/catalog.mjs is the authoritative map. Highlights by area:
Area | Commands |
Web and APIs |
|
Permissions and log |
|
Orientation |
|
Doctors |
|
Proof |
|
Context |
|
Creative |
|
Research |
|
Foundry |
|
Workstation |
|
Most accept --summary for a compact terminal (TUI) view and --json for IDE, app, and automation hosts.
The doctors in full: node demo/ci-doctor.mjs, node demo/presentation-doctor.mjs, node demo/accessibility-doctor.mjs, node demo/performance-doctor.mjs, node demo/compatibility-doctor.mjs, and node demo/operator-doctor.mjs, plus node demo/ci-triage.mjs and node demo/mcp-freshness.mjs. Live CI intake works read-only: node demo/ci-triage.mjs --gh-run owner/repo#run_id --summary.
Documentation
docs/INTRODUCTION.md: what Telos is and your first ten minutes.
docs/HOW-IT-WORKS.md: the verifier loop, step by step, including where it stops.
docs/ARCHITECTURE.md and docs/PROJECT-CONNECTION-MAP.md: system shape and how the five flagships connect.
docs/PROOF-LANES.md: the proof packet types and what each one recomputes.
docs/CURRENT-STATE.md: current state of each surface.
USAGE.md: install, run, MCP, and verify commands.
Peer repos: gather (research intake), index (workspace maps and context), forum (agent routing with a causal ledger), crucible (claim verification), emet (independent second check). Telos can launch gather, index, forum and crucible beside itself from one manifest; each also stands alone.
Status
project-telos-mcp 0.9.0 is the current release, on npm and as GitHub release artifacts that include native Windows ZIP and MCPB client packages. See the client package guide. npm test runs every test file in demo/, and CI runs it on each change. Interfaces may still move between minor versions. The research packets are fixed demos: they do not do causal discovery, robot safety or hardware error correction.
Upgrading from 0.2.0
0.3.0 writes native-control ledger hash version 2. Upgrade readers before writers, because 0.2.0 readers reject the new format. New readers still accept old receipts. Browser evidence packets are not redacted: URLs, titles, selectors, artifact references and summaries stay in them, so keep them private. See release notes.
The roadmap is docs/PROJECT-TELOS-LARGE-SCALE-ROADMAP-2026-07-02.md. The documentation index is docs/DOCUMENTATION-CONSOLIDATION-REGISTRY-2026-07-02.md, with machine-readable data under docs/registry/.
Reading a record
Most commands print a JSON record. Here is one from the artwork checker, field by field. Run it with python tools/check_repo_art.py --json:
License
Text: CC BY 4.0. Code: FSL-1.1-MIT.
The whitepapers and research notes in docs/research/ are
licensed CC BY 4.0. Share and adapt them with credit to Zain Dana Harper; the
terms are in LICENSE-TEXT.
The code and the software documentation are FSL-1.1-MIT (fair source). The code is open to read and run, free for nearly any use except building a competing product, and each release converts to the MIT license after two years. Copyright is held by the author. See LICENSE.
Version 0.9.0 and earlier releases were published under FSL-1.1-ALv2 and keep that license, so each of them still converts to Apache 2.0. FSL-1.1-MIT applies from the next release.
For developers
Zero dependencies, so there is nothing to install. Run the MCP contract tests and smoke checks before opening a PR:
npm run test:mcp
node demo/catalog.mjs --summary
node demo/server-manifest.mjs --summary
node demo/room.mjs --jsonCI (.github/workflows/ci.yml) runs npm test on Node 24. Run one test file with node demo/<name>.test.mjs. node demo/operator-doctor.mjs --summary checks that the README, package metadata and examples match the code.
Built by Zain Dana Harper in Seattle. More tools: Project Telos, Flywheel and its getting started guide, and the workspace canon.
Available Tools
50 toolstelos.accessibility.doctorAccessibility checkARead-onlyIdempotent
Use when a host needs static HTML accessibility, reduced-motion, keyboard, and canvas-fallback receipts for Telos Studio surfaces. Read-only, zero-auth, no external side effects. Returns JSON MATCH, DRIFT, or UNVERIFIABLE accessibility receipts.
Inputs: no named parameters.
telos.action.receiptAction receiptBRead-onlyIdempotent
Use when modeling proposed action, admission, execution, review, and compensation records. Read-only, zero-auth, no external side effects. Returns a JSON action-receipt interface.
Inputs: no named parameters.
telos.admission.telemetryAdmission recordsARead-onlyIdempotent
Use when designing trace fields that keep action admission separate from verification verdicts. Read-only, zero-auth, no external side effects. Returns a JSON telemetry convention.
Inputs: no named parameters.
telos.browser.evidenceBrowser evidence fixtureARead-onlyIdempotent
Use when a host needs the synthetic browser evidence fixture for contract inspection. Read-only, zero-auth, no external side effects. Returns a JSON browser-evidence packet marked unredacted; URL and title context is retained.
Inputs: no named parameters.
telos.catalogTelos tool catalogARead-onlyIdempotent
Use when a host needs the provider-neutral catalog of Project Telos MCP tools and next actions. Read-only, zero-auth, no external side effects. Returns a JSON catalog.
Inputs: no named parameters.
telos.ci.doctorCI compatibility checkARead-onlyIdempotent
Use when a host needs GitHub Actions runtime, action-major, and latest five-flagship CI compatibility receipts. Read-only, zero-auth, no external side effects. Returns a JSON CI doctor register.
Inputs: no named parameters.
telos.ci.triageCI failure triageARead-onlyIdempotent
Use when a host needs to separate fatal GitHub Actions gate failures from Node runtime migration warnings before routing remediation. Read-only, no external side effects, and no external writes. Supports zero-auth offline fixture packets and live gh run intake through the CLI using local gh auth when required. Returns JSON MATCH, DRIFT, or UNVERIFIABLE CI triage receipts.
Inputs: no named parameters.
telos.compatibility.doctorCompatibility checkARead-onlyIdempotent
Use when a host needs CLI, MCP, protocol, manifest, and integration compatibility receipts. Read-only, zero-auth, no external side effects. Returns JSON MATCH, DRIFT, or UNVERIFIABLE compatibility receipts.
Inputs: no named parameters.
telos.context.envelopeContext envelopeBRead-onlyIdempotent
Use when large-workspace context needs readable source refs, budgets, and receipt chains. Read-only, zero-auth, no external side effects. Returns a JSON context-envelope convention.
Inputs: no named parameters.
telos.context.packContext packARead-onlyIdempotent
Use when preparing a bounded handoff packet for large-codebase agent work. Read-only, zero-auth, no external side effects. Returns a validated JSON context pack with hashes and verdicts.
Inputs: no named parameters.
telos.crawl.fetchRead one web pageARead-only
Use when an agent needs the text, feed items, sitemap URLs or JSON of one public URL. Read-only and zero-auth; checks robots.txt first and stops at a bot check. Reaches the network: one honest Telos User-Agent, per-host pacing with backoff on 429 and 503, no login, no cookies. Returns JSON with the parsed page and a receipt of every fetch.
Inputs: url (required).
telos.crawl.siteRead a small siteARead-only
Use when an agent needs several pages of one site; sitemaps and feeds are read before links, inside a depth (0 to 3) and page budget (1 to 50). Read-only and zero-auth; obeys robots.txt and Crawl-delay. Reaches the network: one honest Telos User-Agent, per-host pacing with backoff on 429 and 503, no login, no cookies. Returns JSON page summaries and a receipt.
Inputs: url (required), depth, same_host, page_budget.
telos.creative.engineCreative engine registerARead-onlyIdempotent
Use when presenting the Telos Creative Engine across generative art, sound, typography, media, CGI, math, and physics lanes. Read-only, zero-auth, no external side effects. Returns a JSON creative-engine manifest.
Inputs: no named parameters.
telos.creative.kernelsCreative kernelsARead-onlyIdempotent
Use when deterministic creative primitives are needed for dithering, pixel sorting, plotter paths, or clustered-light bins. Read-only, zero-auth, no external side effects. Returns JSON creative kernels.
Inputs: no named parameters.
telos.display.calibrationDisplay calibration contractARead-onlyIdempotent
Use when display, color, ICC/LUT, artifact refs, or measurement gates need a non-mutating calibration contract. Read-only, zero-auth, no external side effects. Returns a JSON display-calibration contract.
Inputs: no named parameters.
telos.doctorTelos readiness checkARead-onlyIdempotent
Use before demos, listings, or agent runs to check local Telos operator-spine health. Read-only, zero-auth, no external side effects. Returns JSON check results.
Inputs: no named parameters.
telos.learning.forgeLearning forge registerBRead-onlyIdempotent
Use when video, channel, paper, and benchmark leads need to become receipt-backed learning labs before synthesis. Read-only, zero-auth, no external side effects. Returns a JSON Learning Forge packet.
Inputs: no named parameters.
telos.learning.labsLearning labs registerARead-onlyIdempotent
Use when Learning Forge source leads need executable lab contracts with measurements, failure cases, and five-flagship ownership. Read-only, zero-auth, no external side effects. Returns a JSON Learning Forge labs packet.
Inputs: no named parameters.
telos.loop.ledgerLoop ledgerARead-onlyIdempotent
Use when an agent loop needs durable state across fresh contexts and bounded scheduled runs. Read-only, zero-auth, no external side effects. Returns a JSON loop-ledger convention.
Inputs: no named parameters.
telos.mcp.freshnessCompare loaded MCP serversARead-onlyIdempotent
Use when a host must compare loaded MCP servers against expected versions, tools, and probes. Read-only, zero-auth, no external side effects. Returns JSON MATCH, DRIFT, or UNVERIFIABLE freshness receipts.
Inputs: no named parameters.
telos.measurement.layersMeasurement layersBRead-onlyIdempotent
Use when visual, splat, lighting, dither, audio, uncertainty, or frame-budget evidence needs meters, or when a caller's own image (raw 8-bit RGBA, inline base64 or a file under an allowed local root) needs Telos measurement layers L0 to L3 with SHA-256 receipts. Called with no arguments it returns the demo meters. Read-only, zero-auth, no external side effects. Returns a JSON measurement packet (v1 demo or v2 caller image).
Inputs: n, roi, image, layers, +6 more.
telos.model.foundryModel foundry registerARead-onlyIdempotent
Use when planning model-foundry work across hosted, local, open-weight, post-training, and verifier gates. Read-only, zero-auth, no external side effects. Returns a JSON model-foundry contract.
Inputs: no named parameters.
telos.native.controlNative control catalogARead-onlyIdempotent
Use when a host needs the Telos native background-control capability catalog for browser (Chrome DevTools Protocol) and native-app (Windows UI Automation) actuation, plus the device and learn verbs. Read-only, zero-auth, no external side effects. Returns a JSON capability and verb catalog.
Inputs: no named parameters.
telos.objective.monitorObjective monitorARead-onlyIdempotent
Use when checking whether proxy metrics are drifting away from real agent or build objectives. Read-only, zero-auth, no external side effects. Returns JSON objective-monitor signals.
Inputs: no named parameters.
telos.operator.doctorWorkbench health checkARead-onlyIdempotent
Use when a host needs README, status, catalog, manifest, CI, and current-state discoverability receipts for the Telos operator surface. Read-only, zero-auth, no external side effects. Returns JSON MATCH, DRIFT, or UNVERIFIABLE operator receipts.
Inputs: no named parameters.
telos.performance.doctorPerformance checkARead-onlyIdempotent
Use when a host needs static Studio performance, efficiency, asset-budget, and embedding receipts. Read-only, zero-auth, no external side effects. Returns JSON MATCH, DRIFT, or UNVERIFIABLE performance receipts.
Inputs: no named parameters.
telos.presentation.doctorPresentation checkBRead-onlyIdempotent
Use when a host needs five-flagship README, changelog, and brand-asset presentation parity receipts. Read-only, zero-auth, no external side effects. Returns JSON MATCH, DRIFT, or UNVERIFIABLE presentation receipts.
Inputs: no named parameters.
telos.proofAgent action proof packetARead-onlyIdempotent
Use when a host needs the fixture-backed agent-action proof packet joining source refs, context refs, route, admission, side effects, output digests, verifier checks, and the Emet witness stage. Read-only, zero-auth, no external side effects beyond local subprocess reads. Returns a JSON agent-action proof packet.
Inputs: no named parameters.
telos.proof.buildBuild proof packetARead-onlyIdempotent
Use when a host needs the fixture-backed build scientific-runtime proof packet whose conserved-quantity invariant and conservation drift are recomputed from the run's own embedded samples with stdlib math, checked within bounded tolerances, and controlled by a required negative fixture that must break the invariant. Read-only, zero-auth, no external side effects beyond local subprocess reads. Returns a JSON build proof packet.
Inputs: no named parameters.
telos.proof.researchResearch claim proof packetARead-onlyIdempotent
Use when a host needs the fixture-backed research-claim proof packet joining source provenance, a bounded claim, a required negative control fixture, attempt records, recomputed source digests, and a promotion rung the verifier derives rather than trusts. Read-only, zero-auth, no external side effects beyond local subprocess reads. Returns a JSON research-claim proof packet.
Inputs: no named parameters.
telos.proof.visualVisual proof packetARead-onlyIdempotent
Use when a host needs the fixture-backed visual-truth proof packet whose color and luminance measurements are recomputed from the artifact's own embedded sRGB samples, with a read-only boundary and no physical-calibration overclaim. Read-only, zero-auth, no external side effects beyond local subprocess reads. Returns a JSON visual-truth proof packet.
Inputs: no named parameters.
telos.reach.apiOfficial API readARead-only
Use when an agent needs one operation from an official API: hackernews, github, v2ex, wikipedia, arxiv (zero-auth), or youtube and brave (auth is the user's own key in YOUTUBE_API_KEY or BRAVE_SEARCH_API_KEY). Read-only; keys travel in headers and never in receipts. Reaches the network: one honest Telos User-Agent, per-host pacing with backoff on 429 and 503, no login, no cookies. Returns JSON and a receipt.
Inputs: op (required), channel (required), params.
telos.reach.doctorReach channel checkARead-onlyIdempotent
Use before any reach call to see which channels (web crawler, Reddit, X, official APIs) work for this user and what each one costs and leaves out. Read-only, zero-auth, no external side effects: reads environment variable names only, with no network, file writes or processes. Returns a JSON doctor report.
Inputs: no named parameters.
telos.reddit.commentsReddit post and commentsARead-only
Use when an agent needs one Reddit post and its comment tree through the official Data API. Read-only; auth is the user's own Reddit app credentials from environment variables named by telos.reach.doctor. Reaches the network: one honest Telos User-Agent, per-host pacing with backoff on 429 and 503, no login, no cookies. Returns JSON comments with depth and a receipt.
Inputs: post_id (required), depth, limit.
telos.reddit.listingReddit subreddit listingARead-only
Use when an agent needs posts from a subreddit through Reddit's official Data API. Read-only; auth is the user's own Reddit app credentials from environment variables named by telos.reach.doctor, paced from Reddit's rate-limit headers. Reaches the network: one honest Telos User-Agent, per-host pacing with backoff on 429 and 503, no login, no cookies. Returns JSON posts and a receipt.
Inputs: subreddit (required), sort, time, limit.
telos.rendering.capabilitiesRendering capabilitiesARead-onlyIdempotent
Use when a host must choose WebGPU, WebGL, canvas, or static rendering fallbacks for Studio surfaces. Read-only, zero-auth, no external side effects. Returns a JSON renderer capability contract.
Inputs: no named parameters.
telos.rendering.researchRendering research registerARead-onlyIdempotent
Use when collecting rendering leads for clustered-forward, Gaussian splatting, creative coding, and graphics demos. Read-only, zero-auth, no external side effects. Returns JSON research seeds.
Inputs: no named parameters.
telos.research.seedResearch seed registerBRead-onlyIdempotent
Use when terse research notes need source-backed seed packets before synthesis. Read-only, zero-auth, no external side effects. Returns JSON research seeds with provenance status.
Inputs: no named parameters.
telos.research.thermodynamicThermodynamic research receiptARead-onlyIdempotent
Use when exploring thermodynamic or stochastic AI-chip research through public transcript evidence. Read-only, zero-auth, no external side effects. Returns a JSON research receipt with verification labels.
Inputs: no named parameters.
telos.revival.registryRevival registryARead-onlyIdempotent
Use when deciding which older, siloed, or frozen local tools should be promoted into flagship lanes. Read-only, zero-auth, no external side effects. Returns a JSON revival registry.
Inputs: no named parameters.
telos.roomFlagship room summaryARead-onlyIdempotent
Use when an agent needs the current five-flagship room summary before routing work. Read-only and zero-auth. Requires the sibling gather, crucible, index, and forum source checkouts next to this repo plus a local python interpreter; without them it returns an UNVERIFIABLE envelope naming the missing dependency rather than a live summary. Returns a JSON action envelope.
Inputs: no named parameters.
telos.second_level.queueSecond-level tool queueARead-onlyIdempotent
Use when assessing public-safe second-level flagship candidates before registry promotion. Read-only, zero-auth, no external side effects. Returns a JSON second-level flagship queue.
Inputs: no named parameters.
telos.server.manifestMCP server manifestARead-onlyIdempotent
Use when configuring MCP clients for gather, index, forum, crucible, and telos source checkouts. Read-only, zero-auth, no external side effects. Returns a JSON server manifest.
Inputs: no named parameters.
telos.showcase.scoutShowcase candidate rankingsARead-onlyIdempotent
Use when a host needs fixture-backed OSS Proof Showcase candidate rankings before public patch work. Read-only, zero-auth, no external side effects. Returns JSON scout results.
Inputs: no named parameters.
telos.statusTelos statusARead-onlyIdempotent
Use when a host needs current Telos workbench readiness and next actions. Read-only, zero-auth, no external side effects. Returns a JSON action envelope.
Inputs: no named parameters.
telos.workflowCheck the flagship workflowARead-onlyIdempotent
Use when validating the local five-flagship golden workflow from source checkouts. Read-only and zero-auth, no external side effects beyond local subprocess reads. Requires the sibling gather, crucible, index, and forum source checkouts next to this repo plus a local python interpreter; without them it returns an UNVERIFIABLE envelope naming the missing dependency rather than running the workflow. Returns JSON receipts and verdict counts.
Inputs: no named parameters.
telos.workstation.substrateWorkstation intake registerBRead-onlyIdempotent
Use when a host needs public-safe aggregate intake for local workstation repositories and private/local lane families. Read-only, zero-auth, no external side effects. Returns a JSON workstation substrate register.
Inputs: no named parameters.
telos.x.apiX official API readARead-only
Use when the user has an X developer key and wants a post lookup, recent search or a user's recent posts through the official X API v2. Read-only; auth is X_BEARER_TOKEN, and X bills each read, so the receipt carries a cost estimate. Reaches the network: one honest Telos User-Agent, per-host pacing with backoff on 429 and 503, no login, no cookies. Returns JSON and a receipt.
Inputs: op (required), id, max, query, +1 more.
telos.x.oembedRead one X postARead-only
Use when an agent needs the text, author and date of one public X post from its URL, through X's public oEmbed endpoint. Read-only and zero-auth; no search or timelines. Reaches the network: one honest Telos User-Agent, per-host pacing with backoff on 429 and 503, no login, no cookies. Returns JSON and a receipt.
Inputs: url (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
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.
Maintenance
Related MCP Connectors
Control plane for autonomous software labor. Agents claim objectives over MCP with audit trail.
Agent-native MCP for governed commerce, x402 payments, paid capabilities, and verifiable receipts.
Work management where AI agents are first-class members: tasks, projects, memory over hosted MCP
MCP server for your apps' tools and custom tools, plus hosted AI agents and approval-gated workflows
Related MCP Servers
AlicenseAqualityCmaintenanceExposes 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 gradedqualityDmaintenanceSecure, 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

operations-pulseofficial
AlicenseNot gradedqualityCmaintenanceEnables 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- 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