Token Diet

io.github.EvozimPublished by GitHub account Evozimv1.0.0Updated Oct 24, 2026

LLM token optimization gateway implementing semantic pruning.

VerifiedSSEWeb executableAI & ML

Overview

AI-generated overview

A remote MCP gateway that prunes prompt tokens semantically to reduce LLM context size before requests are sent.

What you can do
Token Diet is a remote MCP endpoint described as an LLM token optimization gateway implementing semantic pruning. It is meant to sit between an assistant and a model so that context is trimmed to fewer, more relevant tokens. No tool list is published, so the exact operations it exposes are not documented in the supplied material.
When to use it
Consider it when context length or token cost is a recurring problem and you want an external service to prune prompts before they reach a model. Because no tools are listed, verify what it actually exposes before relying on it in a workflow.
Requirements
A remote SSE connection to the published endpoint; no package or local runtime is declared. No authentication is declared, but a payment-signature header is used for premium settlement, and the endpoint is reached over the network.
Before you install
The payment-signature header carries a Base64-encoded EIP-3009 TransferWithAuthorization signature, which authorizes a token transfer; treat it as a spending credential and never share it. Premium settlement implies possible payment. Prompts routed through the gateway leave your machine for a third-party endpoint, so avoid sending sensitive content.

Installation

In SourceWeft

  1. Open Token Diet in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via SSE. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.Evozim%2Ftoken-diet/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "token-diet": {
      "type": "sse",
      "url": "https://token-diet-mcp.vercel.app/api/mcp"
    }
  }
}

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.