io.github.SunrisesIllNeverSee/tteop-mcp
NPM · TTEOP-MCP · SCANNED SEP 21
Build, validate, and describe TTEOP telemetry envelopes for AI operator token efficiency.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security99
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 4 of 11 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to SunrisesIllNeverSee/tteop-mcp). View diagnostics → Pass
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 17 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability81
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 482 tokens (~120/item across 4 items; 4 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management73
- Stability observed for 22 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the io.github.SunrisesIllNeverSee/tteop-mcp server?
io.github.SunrisesIllNeverSee/tteop-mcp runs locally as an npm package, launched with npx -y tteop-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · tteop-mcp
claude mcp add sunrisesillneversee-tteop-mcp -- npx -y tteop-mcp
{
"mcpServers": {
"sunrisesillneversee-tteop-mcp": {
"command": "npx",
"args": [
"-y",
"tteop-mcp"
]
}
}
} {
"servers": {
"sunrisesillneversee-tteop-mcp": {
"command": "npx",
"args": [
"-y",
"tteop-mcp"
]
}
}
} codex mcp add sunrisesillneversee-tteop-mcp -- npx -y tteop-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"sunrisesillneversee-tteop-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"tteop-mcp"
],
"enabled": true
}
}
} openclaw mcp add sunrisesillneversee-tteop-mcp --command npx --arg -y --arg tteop-mcp
mcp_servers:
sunrisesillneversee-tteop-mcp:
command: "npx"
args: ["-y", "tteop-mcp"] {
"McpServers": {
"sunrisesillneversee-tteop-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"tteop-mcp"
]
}
}
} assistant mcp add sunrisesillneversee-tteop-mcp -t stdio -c npx -a -y tteop-mcp
{
"mcpServers": {
"sunrisesillneversee-tteop-mcp": {
"command": "npx",
"args": [
"-y",
"tteop-mcp"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 21 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes. Other categories moved too: Supply Chain Security rose 1.
- 9 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Sept 2026 · Analysed npm/tteop-mcp@0.2.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | SunrisesIllNeverSee/tteop-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/SunrisesIllNeverSee/tteop-mcp/.github/workflows/release.yml@refs/heads/main |
| Rekor log index | 2702589159 |
| Predicate type | https://slsa.dev/provenance/v1 |
| Subject digest | sha512:1ca113df53ad499c760eff574d88cec93420fee698cabd43e7876bec6ffbfa4fa637af02bb0a9145fcd451d18706d9b23ad0651c56af048a7a6d7de81 |
Background: How many MCP packages publish verified provenance →
Dependencies 11 packages
| Packages resolved | 11 |
|---|---|
| Stale | 4 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
tteop_build_envelope ~281
Build a TTEOP v0.1-draft schema-conforming telemetry envelope from token counts. Computes Yield (Υ), Leverage (L), Velocity (V), output_fraction (F), and log_leverage (D). No data is submitted or persisted. Returns the complete envelope as JSON.
| Name | Type | Req | Description |
|---|---|---|---|
| cache_read | – | – | Cache-read tokens, or null when unavailable. |
| cache_write | – | – | Cache-write tokens, or null when unavailable. |
| cohort_id | string | – | Cohort identifier for private-managed-cohort mode. Requires operator_key. |
| input | integer | yes | Fresh input tokens (non-negative integer, required). |
| model | string | – | Model identifier (e.g., 'claude-sonnet-4', 'gpt-4o'). |
| operator_key | string | – | Pseudonymous operator identifier. Must not contain real-world identity. |
| output | integer | yes | Output tokens (non-negative integer, required). |
| privacy_mode | string | – | Privacy mode. Default: public-pseudonymous. |
| provenance_level | string | – | Provenance level. Default: self-reported. |
| provider | string | – | Provider name (e.g., 'anthropic', 'openai', 'google'). |
| tool | string | – | AI tool name (e.g., 'claude-code', 'cursor', 'copilot'). |
No output schema declared.
No examples provided.
tteop_describe_protocol ~48
Get TTEOP protocol metadata: version, supported versions, privacy modes, provenance levels, forbidden fields, metric definitions (formulas, symbols, rounding), and schema/spec URLs.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
tteop_run_conformance ~62
Run the TTEOP conformance suite: canonical vector invariants, zero-input/zero-output null semantics, missing-cache handling, build-validate round-trip, forbidden field detection, and banker's rounding. Returns pass/fail counts and detailed results.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
tteop_validate_envelope ~91
Validate a TTEOP v0.1-draft telemetry envelope against the JSON Schema and semantic rules. Returns validation status, schema errors, semantic errors, warnings, and computed metrics if valid.
| Name | Type | Req | Description |
|---|---|---|---|
| envelope | object | yes | The TTEOP telemetry envelope to validate (as a JSON object). |
| expected_profile | string | – | If set, asserts the envelope's privacy mode matches this profile. |
No output schema declared.
No examples provided.
What is the io.github.SunrisesIllNeverSee/tteop-mcp server?
io.github.SunrisesIllNeverSee/tteop-mcp is listed in the public MCP registry as io.github.SunrisesIllNeverSee/tteop-mcp. Build, validate, and describe TTEOP telemetry envelopes for AI operator token efficiency. This page covers its npm package (tteop-mcp).
Is the io.github.SunrisesIllNeverSee/tteop-mcp server safe to use?
io.github.SunrisesIllNeverSee/tteop-mcp scores 93 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 September 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.SunrisesIllNeverSee/tteop-mcp server expose?
io.github.SunrisesIllNeverSee/tteop-mcp exposes 4 tools: tteop_build_envelope, tteop_validate_envelope, tteop_describe_protocol, tteop_run_conformance. Their descriptions and schemas cost roughly 482 tokens of context every time the server is loaded.
Is the io.github.SunrisesIllNeverSee/tteop-mcp server still maintained?
io.github.SunrisesIllNeverSee/tteop-mcp is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.SunrisesIllNeverSee/tteop-mcp server under?
io.github.SunrisesIllNeverSee/tteop-mcp declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.