
Rtkcontext Mcp
com.clauxel.rtkcontextPublished by rtkcontext.clauxel.comOfficial publisherv1.0.0Updated Oct 24, 2026
A paid remote MCP for OpenAI Codex context compressor, built to return verdicts, receipts, usage log
Overview
A paid hosted MCP endpoint that compresses context for OpenAI Codex tasks and returns savings estimates, receipts and usage history.
- What you can do
- Compress context for a given task and estimate the resulting context savings, with structured JSON results and a public server card for discovery. Issue context receipts and read compression history, giving audit-ready evidence of what was compressed and how much was saved. Access is token-based, so calls are tied to a plan obtained from the product website.
- When to use it
- Useful for coding teams and AI agents running OpenAI Codex workflows who want to shrink task context and keep a record of savings and usage. Consider it when audit-ready evidence of context compression matters more than running a local tool.
- Requirements
- A remote Streamable HTTP endpoint; no local package or runtime is needed. A paid plan from the product website and a bearer token sent in the Authorization header are required for production calls. An MCP client that supports remote Streamable HTTP servers is needed.
Installation
In SourceWeft
- Open Rtkcontext Mcp in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. 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/com.clauxel.rtkcontext%2Frtkcontext-mcp/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.Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"rtkcontext": {
"type": "http",
"url": "https://rtkcontext.clauxel.com/mcp"
}
}
}README
RTK Context Compressor
Hosted MCP for OpenAI Codex context compressor.
RTK Context Compressor is a paid remote MCP endpoint for OpenAI Codex context compressor. It exposes structured JSON tools, a public server card, token-based access, usage receipts, and audit-ready workflow evidence for AI agents and coding teams.
Public Endpoints
- Website: https://rtkcontext.clauxel.com/?utm_source=github&utm_medium=directory&utm_campaign=sbl202605r25
- MCP endpoint: https://rtkcontext.clauxel.com/mcp
- Server card: https://rtkcontext.clauxel.com/.well-known/mcp/server-card.json
- Registry name:
com.clauxel.rtkcontext/rtkcontext-mcp
Access
This is a paid hosted remote MCP. Production calls require a bearer token issued from the product website.
Unauthenticated browser visits to /mcp return a clear JSON error instead of internal details.
Tools
compress_context_for_taskestimate_context_savingsissue_context_receiptread_compression_history
Quick Start
- Open the website and choose a plan.
- Create or request an API token.
- Add the endpoint to an MCP client that supports Streamable HTTP remote servers.
- Send JSON-RPC requests with the bearer token.
Useful Links
- Product page: https://rtkcontext.clauxel.com/?utm_source=github&utm_medium=directory&utm_campaign=sbl202605r25
- Pricing: https://rtkcontext.clauxel.com/?utm_source=github&utm_medium=directory&utm_campaign=sbl202605r25#pricing
- Server card: https://rtkcontext.clauxel.com/.well-known/mcp/server-card.json
- MCP endpoint: https://rtkcontext.clauxel.com/mcp
Status
This repository is a public documentation and directory-submission reference for the hosted service. It does not contain the private production source code.
Source: README.md at commit 04697ee
Tools
0Version history
1- v1.0.0LatestSep 16, 2026
Score
50% 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
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declaredRequired10 pts
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
Declare a license in the repository or the registry entry.