zettaquant-vslm-mcp
OfficialClick on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@zettaquant-vslm-mcpFilter these earnings call sentences to only ones about AI capex plans."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
zettaquant-vslm-mcp
MCP server that exposes ZettaQuant V-SLM to any MCP-aware LLM host.
Add three lines to your Claude Desktop / Cursor / Zed / Windsurf config and your model can filter noisy context (earnings-call transcripts, news articles, long reports, log lines) using ZettaQuant's topic-conditioned relevancy classifier — typically cutting token spend before the language model even sees the input.
What it exposes
One tool, over stdio, via the Model Context Protocol:
Tool | Purpose |
| Filter |
The LLM decides when to call it on its own — no code you have to write in the host.
Related MCP server: genpark-contextual-compression-filter-skill
Install & configure
You need a ZettaQuant API key with the vslm scope. Get one at zettaquant.ai (or ask your account contact).
Claude Desktop
Edit ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):
{
"mcpServers": {
"zettaquant-vslm": {
"command": "uvx",
"args": ["zettaquant-vslm-mcp"],
"env": {
"ZQ_API_KEY": "<your api key>"
}
}
}
}Restart Claude Desktop. The tools appear under the "Tools" menu.
Cursor
Edit ~/.cursor/mcp.json:
{
"mcpServers": {
"zettaquant-vslm": {
"command": "uvx",
"args": ["zettaquant-vslm-mcp"],
"env": { "ZQ_API_KEY": "<your api key>" }
}
}
}Restart Cursor.
Zed
In ~/.config/zed/settings.json:
{
"context_servers": {
"zettaquant-vslm": {
"command": {
"path": "uvx",
"args": ["zettaquant-vslm-mcp"],
"env": { "ZQ_API_KEY": "<your api key>" }
}
}
}
}Windsurf / other MCP hosts
Any host that supports the standard mcpServers config shape works — use the same command + args + env block as above.
Environment variables
Variable | Required | Default | Notes |
| Yes | — | Your ZettaQuant API key. Must have the |
|
| Override for staging or a private gateway. |
Usage examples in the LLM
Once installed, just ask naturally. Some prompts that will trigger vslm_predict:
"Here are 40 sentences from Apple's Q3 earnings call. Pull out the ones about AI capex plans."
"Filter these log lines down to anything related to lateral movement."
"I pasted a 10-K risk section. Only show me sentences about supply-chain exposure."
The model calls vslm_predict under the hood, gets back the relevant sentences, and works from those — cheaper and more precise than reading the full input.
Development
uv venv
uv pip install -e .
export ZQ_API_KEY="..."
python -m zettaquant_vslm_mcpThe server speaks JSON-RPC on stdin/stdout. To poke it manually, use the MCP Inspector:
npx @modelcontextprotocol/inspector uvx zettaquant-vslm-mcpTroubleshooting
"ZQ_API_KEY is not set" in the host logs → the
envblock in your MCP config didn't propagate. Confirm the config file path and restart the host.401 in tool output → key is valid but wrong. Try it directly:
curl -H "x-api-key: $ZQ_API_KEY" https://api.zettaquant.ai/v1/usage/me.ZettaQuant access denied (403)→ your key doesn't have thevslmscope. Contact ZettaQuant.ZettaQuant quota exceeded (429)→ you hit your per-period cap; the error message includes the reset time.
License
MIT.
Available Tools
1 toolvslm_predictA
Filter a list of sentences to only those relevant to query.
Use this BEFORE feeding noisy context (earnings-call transcripts, news articles, long reports, log lines) to an LLM; it typically cuts token spend without losing important context. Chain it with your own language model.
Args: sentences: raw input sentences; ~2000 per call is comfortable. query: natural-language description of the topic to filter for (e.g. "AI capex plans", "rate cuts", "supply chain risk").
Returns: dict with: relevant_sentences: sentences that passed the filter, original order. total_sentences, relevant_count: counts to compute savings. topic_used: the topic string the model actually filtered against. topic_source: "zettaquant" (server-derived) or "caller" (you supplied). model_id: which V-SLM head handled the request.
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes | ||
| sentences | Yes |
Output Schema
| Name | Required | Description |
|---|---|---|
No output parameters | ||
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
1 tool update
v0.1.1- First observed
vslm_predict
TDQS
Scored across 1 tool
Only one tool exists, so there is no possibility of selecting the wrong tool for a task. The tool's purpose is clearly defined as relevance filtering.
With a single tool, there is no internal naming pattern to violate. The name 'vslm_predict' is readable and action-oriented, though it uses noun-verb ordering rather than the more common verb-noun style.
One tool is below the usual 3-15 range, but it is a dedicated single-purpose utility specialized for sentence relevance filtering. The count feels slightly thin rather than excessive or trivial.
For the stated purpose of filtering noisy sentences before LLM ingestion, the tool provides the core operation plus useful metadata like counts and model info. There is no obvious missing operation within this narrow, well-defined domain.
Maintenance
Related MCP Connectors
Scan prompts for injection attacks, redact PII, and audit LLM SDK usage from any MCP client
Hosted MCP server for LLM cost estimation, model comparison, and budget-aware routing.
Reddit & X data for AI agents over MCP. Semantic search, hosted, no Reddit API.
Free OpenAI-compatible inference with signed provenance receipts and 3 focused MCP tools.
Related MCP Servers
- AlicenseAqualityCmaintenanceEnables any MCP host to search and answer over your own documents with hybrid BM25+dense retrieval, cross-encoder reranking, and grounded, cited responses that refuse when no evidence is found.5MIT
- FlicenseNot gradedqualityBmaintenanceEnables AI agents and MCP clients to compress retrieved web documents against a query, pruning irrelevant noise through deterministic algorithmic scoring so downstream context stays lean. It exposes this capability over the Model Context Protocol for integration with Claude Desktop, Cursor, and similar clients.8-
- FlicenseNot gradedqualityNot gradedmaintenanceEnables AI agents to compress retrieved web documents against a query, pruning irrelevant noise so only the most relevant context reaches the model. It runs as a zero-dependency Python MCP server that accepts a query payload and returns structured, scored output.7-
- FlicenseNot gradedqualityBmaintenanceEnables sentence-level factual grounding verification and hallucination detection for RAG outputs via MCP, with deterministic scoring and structured telemetry.7-