Tteop MCP server
io.github.SunrisesIllNeverSee/tteop-mcp·v0.2.1Build, validate, and describe TTEOP telemetry envelopes for AI operator token efficiency.
0 stars44 downloads/wk
Reviews
Write oneNobody has reviewed Tteop yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Tteop tools (4, 1 write)
write = sends, deletes, buys or postsRead from the package source without running it. The installed server may list more.
tteop_build_envelopeBuild a TTEOP v0.1-draft schema-conforming telemetry envelope from token counts.
tteop_describe_protocolGet TTEOP protocol metadata: version, supported versions, privacy modes,
tteop_run_conformancewrite actionRun the TTEOP conformance suite: canonical vector invariants, zero-input/zero-output null semantics,
tteop_validate_envelopeValidate a TTEOP v0.1-draft telemetry envelope against the JSON Schema and semantic rules.
Public scan report
scanner v0.1.10 · 2026-10-16 · same rubric, same numbers if you re-run it
- Code scan4 source files scanned25/25
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitylocal package, no credentials required12/15
- Maintenancelast push 7 days ago15/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
How Tteop compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 92/100
- higher than 93% of 48,243 servers
- Tools
- 4
- the typical server has 7
- Tools that change things
- 25%
- typical: 0%. Fewer write tools means less an agent can break
- Downloads a week
- 44
- more than 34% of 12,306 servers with a package
What its tools let an agent do: 3 read · 1 change
Install Tteop in Claude Code, Cursor or VS Code
Runs npx -y tteop-mcp on your machine. Read the scan report first; the gateway never runs local packages.
claude mcp add tteop-mcp -- npx -y tteop-mcp
What the publisher says
From the Tteop repository's README, as published. We do not edit it. Read it on GitHub
tteop-mcp
Production MCP server for TTEOP — Token Telemetry Evaluation Operator Protocol.
Build, validate, and describe TTEOP telemetry envelopes via the Model Context Protocol. Powered by the official MCP TypeScript SDK v2 and the tteop-spec reference implementation.
New here? Read START-HERE.md. Automated contributors must also read AGENTS.md.
Architecture
This package is a thin MCP transport layer. All protocol logic — envelope construction, metric computation (banker's rounding), schema validation, and semantic rules — is delegated to tteop-spec via its stable JavaScript API:
- tteop-spec/builder → buildEnvelope(telemetry, options)
- tteop-spec/validator → validateEnvelope(envelope, options), computeMetrics(telemetry)
No metric formulas or schema logic are duplicated here. When tteop-spec updates its validator or builder, this server inherits the changes.
Product separation
Install
npm install -g tteop-mcp
# or use directly:
npx tteop-mcpTools
Usage
With Claude Desktop
Add to claudedesktopconfig.json:
{
"mcpServers": {
"tteop": {
"command": "npx",
"args": ["-y", "tteop-mcp"]
}
}
}With MCP Inspector
npx @modelcontextprotocol/inspector npx -y tteop-mcpOpen the browser tab, click Connect, open the Tools tab, and call any tool.
Programmatic
import { spawn } from "node:child_process";
const proc = spawn("npx", ["-y", "tteop-mcp"], { stdio: ["pipe", "pipe", "pipe"] });
// Send JSON-RPC 2.0 messages to proc.stdin, read responses from proc.stdoutDevelopment
# Install the exact locked dependency graph
npm ci
# Optional: test unpublished local tteop-spec changes after the clean install.
# This overrides node_modules locally and is never used by CI or releases.
cd ../otep-spec && npm link && cd ../tteop-mcp && npm link tteop-spec
# Run tests
npm test # real MCP client test
npm run test:packaged # packaged tarball test
npm run test:release # package/lockfile/registry version agreement
npm run test:all # complete local release gate
# Run with MCP Inspector
npm run inspect
# Start the server
npm startAcceptance criteria
- [x] npx tteop-mcp waits for an MCP connection
- [x] initialize succeeds
- [x] tools/list returns complete schemas (4 tools)
- [x] Every tool can be called through MCP Inspector
- [x] Invalid token values return structured MCP errors (isError: true with validation message)
- [x] stdout contains protocol messages only
- [x] CI runs an actual MCP client against the packaged tarball
Distribution status and release order
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Tteop: common questions
- Is Tteop MCP server safe?
- Yes, by our scan: it is graded A (92/100). Read the Tteop safety report
- How do I install Tteop?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does Tteop need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is Tteop maintained?
- The last commit was 27 days ago (2026-10-09). The latest release is v0.2.1.
- How does Tteop compare with other MCP servers?
- safety score 92/100 (higher than 93% of 48,243 servers); tools 4 (the typical server has 7); tools that change things 25% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.