io.github.SunrisesIllNeverSee/tteop-mcp
NPM · TTEOP-MCP
Build, validate, and describe TTEOP telemetry envelopes for AI operator token efficiency.
Available components
Last scanned (19 hours ago)
Scores higher than 94% of npm servers
Category AI and Machine Learning
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 Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects @modelcontextprotocol/server 2.0.0, a direct dependency. A fixed version is available. View diagnostics → Fail
- 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 62 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 31 Oct 26 +1
- Stability: 0.97 → pass security
- 30 Oct 26 −1
- Stability: pass → 0.97 functional
- 28 Oct 26 0
- GHSA-f897-62hf-6gxq affects this package: high ▼ security
- 24 Oct 26 +1
- CVE-2023-54404 affects this package: high ▼ security
- Stability: 0.97 → pass security
- 23 Oct 26 −1
- Stability: pass → 0.97 functional
- 21 Oct 26 −5
- CVE-2026-111771 affects this package: high ▼ security
- CVE-2026-111770 affects this package: high ▼ security
- CVE-2026-111768 affects this package: high ▼ security
- Known CVEs: pass → fail ▼ security
- 17 Oct 26 0
- Stability: 0.97 → pass security
- 16 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 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 5 Nov 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 | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:1ca113df53ad499c760eff574d88cec93420fee698cabd43e7876bec6ffbfa4fa637af02bb0a9145fcd451d18706d9b23ad0651c56af048a7a6d7de81 |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 5 findings
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-46jr-4wx8-v453 | CVE-2026-111768 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
| GHSA-f897-62hf-6gxq | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes | |
| GHSA-jm63-cq47-j5jp | CVE-2026-111770 | high | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:H | yes |
| GHSA-rvq5-wwqv-78pq | CVE-2026-111771 | medium | CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N | yes |
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
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.
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
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 91 out of 100 on VerifyMCP. We recorded 5 known advisories against it as of 5 November 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 5 November 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.
What did VerifyMCP test on the io.github.SunrisesIllNeverSee/tteop-mcp server?
VerifyMCP ran 16 checks on io.github.SunrisesIllNeverSee/tteop-mcp, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.