Semantically filter MCP tool catalogs to cut LLM input-token costs. Ships with AWS Bedrock defaults; bring-your-own provider supported.
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"mcp-token-saver","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# mcp-token-saver <p align="center"> <img src="https://raw.githubusercontent.com/victorTAKI/mcp-token-saver/main/docs/icon.png" alt="mcp-token-saver logo" width="140"/> </p> **Install on your MCP gateway to reduce input-token costs at scale.** When an LLM agent connects to an MCP server exposing many tools (e.g. 200), the full tool catalog is injected into every LLM call, consuming thousands of input tokens per turn. <p align="center"> <img src="https://raw.githubusercontent.com/victorTAKI/mcp-token-saver/main/docs/demo.gif" alt="mcp-token-saver demo" width="720"/> </p> `mcp-token-saver` sits on the gateway and semantically filters that catalog per user query, keeping only the most relevant tools. Result: **80-95% input-token reduction**. > ⚠️ **Ships with AWS Bedrock defaults.** Real-semantic embeddings (Titan Embed v2) and the LLM router (Claude Haiku) require AWS credentials. Using OpenAI, Vertex, HuggingFace, or a local model? Fully supported — jump to [Not using Bedrock?](#not-using-bedrock) for a 10-line BYO example. ## Install The package ships with three install profiles depending on what you want to plug in. ```bash # Minimal pip install mcp-token-saver # Recommended: real semantic embeddings via AWS Bedrock (Titan Embed v2). # TokenSaver.default() auto-picks Bedrock when AWS_ACCESS_KEY_ID (or AWS_PROFILE # / AWS_ROLE_ARN) is set in the environment. pip install "mcp-token-saver[bedrock]" # Adds the FAISS-backed vector store (recommended when your catalog is huge). pip install "mcp-token-saver[faiss]" # Everything (Bedrock + FAISS): pip install "mcp-token-saver[all]" ``` Or from GitHub directly: ```bash pip install "mcp-token-saver[all] @ git+https://github.com/victorTAKI/mcp-token-saver.git" ``` > **Using a non-Bedrock LLM provider (OpenAI, Vertex, local models, …)?** > > `TokenSaver.default()` auto-picks Bedrock for embeddings (Titan Embed v2) and Bedrock for the LLM router (Claude Haiku). To use another provider: > > - **Custom LLM route…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.