Telos logo

Telos

by HarperZ9

Local MCP tools for web intake, CI triage, static HTML checks, gated app control, and verifiable proof packets.

Install Telos

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "harperz9-telos": {
      "command": "npx",
      "args": [
        "-y",
        "project-telos-mcp"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Install not yet sandbox-tested— we haven't run this command through our automated sandbox yet. Not a red flag; we're working through the catalog.

Overview

HarperZ9/telos exposes 50 local MCP tools and a CLI for web and public API intake, GitHub Actions triage, static HTML checks, gated browser or Windows app control, and proof verification. It runs as a dependency-free Node.js 20+ stdio server and can be launched with the `project-telos-mcp` npm package. Reach for it when agent work needs local execution, robots-aware fetching, explicit permission gates, action receipts, or MATCH/DRIFT/UNVERIFIABLE results. Browser control uses Chrome DevTools Protocol, while Windows app control uses UI Automation and requires a terminal-issued grant.

Use cases

  • Fetch public pages and APIs with crawl-policy compliance
  • Triage a GitHub Actions run for blocking failures
  • Check an HTML file for static accessibility issues
  • Review HTML byte budgets without launching a browser
  • Verify whether recorded inputs have changed

Key features

  • Local web, feed, sitemap, and public API intake
  • 50 MCP tools over stdio
  • Grant-gated Chrome and Windows app control
  • Hash-chained action and refusal receipts
  • Static accessibility and performance doctors
  • MATCH, DRIFT, and UNVERIFIABLE proof verification

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 1d ago

Recent health check succeeded.

11/11 checks healthy over the last 85d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 13d ago via OSV.dev · project-telos-mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars4Stargazers on the source repository.
npm downloads197Package downloads in the last 30 days.
Last commit8d agoMost recent push to the default branch.
Directory activity3 viewsConfig copies, upvotes, and views on AllMCPs.

How Telos works

What HarperZ9/telos does

HarperZ9/telos combines agent-facing MCP tools with a command-line interface for inspectable local work. Its 50 tools cover several distinct tasks:

  • Reading HTML pages, feeds, sitemaps, and selected public APIs.
  • Reviewing a GitHub Actions run through the gh CLI.
  • Running static accessibility and performance checks against an HTML file.
  • Driving Chrome or Windows applications only after an explicit permission grant.
  • Recording gated actions and refusals in a hash-chained log.
  • Creating and checking proof packets for actions, research claims, measurements, and build invariants.

The package is published as project-telos-mcp and runs on Node.js 20 or newer without npm dependencies.

How it works

The MCP process communicates over stdio with an MCP host. A host can start it with npx -y project-telos-mcp, or a global installation can provide the telos and telos-mcp commands.

Web intake runs locally and reads HTML as served, without executing page JavaScript. Fetches honor robots.txt and Crawl-delay, and each result records the URL, timestamp, status, and SHA-256 of the fetched bytes. Reddit access uses the official API with the operator's app credentials; single X posts use the X oEmbed endpoint. Other supported public sources include Hacker News, GitHub, arXiv, and Wikipedia.

Control operations are permission-gated. A grant must be issued from an interactive terminal, preventing an agent shell from granting itself access. Consequential actions require confirmation, and password, one-time-code, and card fields are refused. Action records can be signed with a locally initialized Ed25519 key, while proof packets recompute their embedded inputs and report MATCH, DRIFT, or UNVERIFIABLE.

Setup and configuration

For an MCP host, configure npx as the command and pass -y and project-telos-mcp as arguments. The package can also be installed globally:

Terminal
npm install -g project-telos-mcp
telos reach doctor

Use telos reach doctor to inspect available intake channels and credential requirements. Reddit requires REDDIT_CLIENT_ID and REDDIT_CLIENT_SECRET when that source is used. The repository's multi-server demonstration expects related Project Telos repositories beside one another and uses PROJECT_TELOS_PUBLIC for their parent directory.

Tools and capabilities

telos reach fetches pages, feeds, sitemaps, and supported public APIs while producing fetch receipts. ci-triage --gh-run owner/repo#run_id identifies whether a run failed at a blocking step or only produced warnings; it does not diagnose the underlying test.

accessibility-doctor --html FILE performs 14 static checks covering items such as language, viewport, landmarks, focus styling, reduced motion, skip links, and labels. performance-doctor --html FILE performs 14 byte-budget checks. Neither command opens a browser.

native-control can navigate Chrome through DevTools Protocol and control Windows applications through UI Automation, subject to grants and risk tiers. proof.mjs creates packets, and proof.mjs verify checks whether their inputs and values still match.

Limitations and notes

Web fetching does not render JavaScript, so login-protected pages and bot checks can produce empty results. Browser and app control is narrower than dedicated browser automation servers, and Windows app control is Windows-only. Static HTML doctors do not provide browser-based audits. Proof packets are hash-checked but unsigned; signed action-log chain heads require local key initialization. The CI tool classifies failure steps and warnings without diagnosing test failures.

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Telos

HarperZ9/telos is an MCP server that connects AI agents to local web and public API intake, GitHub Actions triage, static HTML checks, gated Chrome or Windows app control, and proof verification. Its 50 stdio tools produce fetch receipts, action logs, and MATCH, DRIFT, or UNVERIFIABLE results.

Install it with `npx -y project-telos-mcp` in an MCP host configuration, or run `npm install -g project-telos-mcp` for the `telos` and `telos-mcp` commands. The server requires Node.js 20 or newer and has no npm dependencies.

Yes. HarperZ9/telos is documented as working with Claude Code through its stdio MCP server. Configure the host to launch `npx` with `-y project-telos-mcp` as the argument.

Yes, it can drive Chrome through the DevTools Protocol after a grant is issued from an interactive terminal. Consequential actions require confirmation, and password, OTP, and card fields are refused.

No. Its web intake reads HTML as served and does not execute page JavaScript, so pages behind login screens or bot checks may return empty results. Fetches follow robots.txt and Crawl-delay.

Related MCP servers

Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewTelos AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/harperz9-telos?style=directory)](https://allmcps.com/mcp/harperz9-telos)
HTML Embed
<a href="https://allmcps.com/mcp/harperz9-telos"><img src="https://allmcps.com/api/badge/harperz9-telos?style=directory" alt="Telos on AllMCPs" /></a>