updated 2026-11-10 04:07 UTC

Token Optimizer MCP

Repository by ooples

Measure token savings per AI coding agent, optimize context, and share a live local knowledge graph across 16 CLI clients.

MCP Servers JavaScript Listed MIT

Is Token Optimizer MCP safe? Strong public trust posture, backed by multiple independent signals.

OSSF Scorecard 6.0 / 10
Provenance Attested
Signed commits 100%
Last push today
Advisories None known
Compare Token Optimizer MCP

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →
Suggest a correction

In detail: Token Optimizer MCP scores 85.8/100 (Grade A), ranked #86 of 1374 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; OSSF Scorecard rates its supply-chain practices 6.0/10; 100% of recent commits are signed; no published advisory affects its latest release (@ooples/token-optimizer-mcp); last pushed 2026-11-10. Every point is earned from checkable signals — never paid placement. How scoring works →

How Token Optimizer MCP could raise its score

Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.

Already done? Suggest a correctionAdd the trust badge

Chain of custody

Scanners check what the code says. This traces who ships Token Optimizer MCP and whether that has changed: from the source repository, through how changes are reviewed and released, to the package you install. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.

  1. Source Signed

    github.com/ooples/token-optimizer-mcp, MIT, last pushed 2026-11-10. 100% of the last 100 commits carry a verified signature, so changes trace to a verified account.

  2. Review and release Mixed

    OpenSSF Scorecard rates the repository's practices 6.0/10 (scanned Oct 28, 2026). The checks that decide who can get a change released:

    • Code Review0
    • Branch Protection5
    • Signed Releasesn/a
    • Dangerous Workflow10
    • Token Permissions0
    • Pinned Dependencies3
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 5
    CI-Tests 10
    CII-Best-Practices 0
    Code-Review 0
    Contributors 3
    Dangerous-Workflow 10
    Dependency-Update-Tool 10
    Fuzzing 0
    License 10
    Maintained 10
    Packaging 10
    Pinned-Dependencies 3
    SAST 10
    Security-Policy 10
    Signed-Releases -1
    Token-Permissions 0
    Vulnerabilities 0

  3. Published packages Linked and attested

  4. What you install today No known advisories

    Latest release checked: @ooples/token-optimizer-mcp 7.9.0. No published advisory affects it (OSV, checked 2026-11-09).

Changes to this chain

  • 2026-09-23 Package provenance attestation detected
  • 2026-08-26 OSSF Scorecard: 6.1/10

Evidence behind this score

Coverage B: 3 of 5 independent evidence types found.

  • GitHub repository data
  • Package downloads
  • Supply-chain checks
  • Public actions (missing)
  • Community mentions (missing)

Verify this score yourself

Every build re-issues Token Optimizer MCP’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.

Signed credential (JSON) How to verify

What this score doesn’t check

It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.

How Token Optimizer MCP compares in MCP Servers

  1. #24 Godot AI 86.8 +1.0
  2. #25 Safari MCP 86.2 +0.4
  3. #26 Token Optimizer MCP 85.8 this agent
  4. #27 Genexus18MCP 85.6 −0.2
  5. #28 App Store Connect MCP 85.5 −0.3

Bars show each HVTrust score; the tick marks Token Optimizer MCP’s 85.8.

Where the 85.8 comes from

HVTrust dimensions vs the MCP Servers average

85.8 / 100 · 100.0% confidence

Token Optimizer MCP MCP Servers average (778 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
20.0 / 25
9.2 above avg 10.8
Identity / Provenance60% listing status · 40% build provenance
18.0 / 18
4.3 above avg 13.7
Transparency50% declared license · 50% OSSF Scorecard
13.6 / 17
1.3 above avg 12.3
Maintenance60% last-push freshness · 40% commit activity
19.1 / 20
6.9 above avg 12.2
AdoptionLog-scaled stars · package downloads
11.6 / 20
4.0 above avg 7.6

Quick Trust Read

What Would Improve It
Improve adoption to lift the weakest part of the trust profile.
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 6.0/10. Tighten the weakest checks to improve public safety evidence.
Compare with another agent
View MCP Servers Report missing data
72.6
Activity sub-score · out of 100
#26
In MCP Servers

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade A reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-11-10 04:07 UTC · Repo last pushed today

Rank Trend

2026-09-29 2026-11-10

Activity & Reach

Stars
577
Forks
73
Last Push
2026-11-10
today
Commits (4 wk)
60
Downloads (7d)
5,679
npm
HN mentions (30d)
—
Open Issues
3
Rank Change
=
was #86

Analysis

Activity Inputs

72.6 / 100
StarsRepository reach
16.6 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
22.3 / 25
CommunityFork signal
8.7 / 20

Common questions about Token Optimizer MCP

Public supply-chain signals for Token Optimizer MCP are strong: it has multiple independent trust indicators in place. This does not replace your own security review, but Token Optimizer MCP carries less obvious unverified-evidence risk than projects with thin signals.
Does Token Optimizer MCP publish package provenance?
Yes. Token Optimizer MCP's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.
Does Token Optimizer MCP have an OpenSSF Scorecard?
Token Optimizer MCP has an OpenSSF Scorecard score of 6.0/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.
Is Token Optimizer MCP actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does Token Optimizer MCP use?
Token Optimizer MCP ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Token Optimizer MCP's commits signed?
100% of the last 100 commits to Token Optimizer MCP are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.

AI agent surface

MCP, providers, tool surface
Scored in HVTrust

These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →

MCP Server Support
high confidence
Implemented
Token Optimizer MCP appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
high confidence
2 detected
Public provider/service dependencies detected.
Credential signal: API keys or service config markers documented.
Tool / Plugin Surface
high confidence
Declared
Declared plugin/integration surface detected.
Detailed evidence is not shown in the public view.
Package Provenance Drift
high confidence
Match
Published package metadata matches the tracked repo
Detailed evidence is not shown in the public view.
  • MCP signal live
  • External deps live
  • Tool / plugin surface live
  • Package provenance drift live
How this surface has changed

Detected changes to Token Optimizer MCP's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.

2026-09-23
Tool Surface Changed
Detected tool/plugin surface changed: none → declared
2026-09-23
Provider Added
Runtime surface grew — new detected provider dependencies: Anthropic, Google Gemini
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Provenance Added
Package provenance attestation detected

Maintain Token Optimizer MCP?

For maintainers

HVTrust scores Token Optimizer MCP from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history
Rank 19HVTrust 3Grade 3Scorecard 1Delisted 1Listed 1Provenance 1MCP 1Surface 1Surface 1
2026-10-01
Rank Moved
Rank dropped 11 spots (#75 → #86)
2026-09-23
Tool Surface Changed
Detected tool/plugin surface changed: none → declared
2026-09-23
Provider Added
Runtime surface grew — new detected provider dependencies: Anthropic, Google Gemini
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Provenance Added
Package provenance attestation detected
2026-09-23
Grade Changed
Trust grade D → A
2026-09-23
Rank Moved
Rank rose 546 spots (#612 → #66)
2026-09-23
HVTrust Changed
HVTrust up 52.6pts (33.5 → 86.1)
2026-09-22
Newly Listed
First tracked at rank #612
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-20
Rank Moved
Rank dropped 10 spots (#54 → #64)
2026-09-07
Grade Changed
Trust grade C → A
2026-09-07
Rank Moved
Rank rose 569 spots (#620 → #51)
2026-09-07
HVTrust Changed
HVTrust up 29.2pts (57.4 → 86.6)
2026-09-06
Rank Moved
Rank dropped 17 spots (#603 → #620)
2026-09-05
Rank Moved
Rank dropped 82 spots (#521 → #603)
2026-09-04
Rank Moved
Rank dropped 17 spots (#504 → #521)
2026-09-03
Rank Moved
Rank dropped 22 spots (#482 → #504)
2026-09-01
Rank Moved
Rank dropped 12 spots (#465 → #477)
2026-08-31
Rank Moved
Rank dropped 29 spots (#436 → #465)
2026-08-30
Rank Moved
Rank rose 13 spots (#449 → #436)
2026-08-29
Rank Moved
Rank dropped 15 spots (#434 → #449)
2026-08-27
Rank Moved
Rank dropped 11 spots (#420 → #431)
2026-08-26
Scorecard Added
OSSF Scorecard: 6.1/10
2026-08-26
Grade Changed
Trust grade D → C
2026-08-26
Rank Moved
Rank rose 55 spots (#475 → #420)
2026-08-26
HVTrust Changed
HVTrust up 8.6pts (48.8 → 57.4)
2026-08-24
Rank Moved
Rank dropped 15 spots (#461 → #476)
2026-08-22
Rank Moved
Rank rose 17 spots (#481 → #464)
2026-08-19
Rank Moved
Rank dropped 12 spots (#469 → #481)
2026-08-17
Rank Moved
Rank rose 12 spots (#480 → #468)
2026-08-13
Rank Moved
Rank dropped 13 spots (#461 → #474)
GitHub → npm: @ooples/token-optimizer-mcp

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 85.8 Grade A
Markdown:
[![HVTrust](https://hvtracker.net/badge/token-optimizer-mcp.svg)](https://hvtracker.net/agents/token-optimizer-mcp)
HTML:
<a href="https://hvtracker.net/agents/token-optimizer-mcp"><img src="https://hvtracker.net/badge/token-optimizer-mcp.svg" alt="HVTrust"></a>

Other agents in MCP Servers

Data sources
GitHub REST API (repo, commits, stars, forks, license) · npm Registry (downloads, provenance) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON