
Execute context-window-optimizer-mcp
io.github.EvozimPublished by GitHub account Evozimv2.0.0Updated Oct 24, 2026
Premium agentic endpoint for context-window-optimizer-mcp.
Overview
A remote MCP endpoint for context-window-optimizer-mcp that requires a per-request crypto payment signature to use.
- What you can do
- Connects an assistant to a hosted premium endpoint for context-window-optimizer-mcp over SSE, with no tools listed in the manifest. Access is gated by an x402 V2 payment: each request carries a signed authorization for a small USDC charge on Base Mainnet. The manifest gives no further detail on what the endpoint returns, so its actual capabilities cannot be confirmed from the supplied information.
- When to use it
- Only when you already intend to use this specific premium context-window-optimizer endpoint and are prepared to pay per request in USDC on Base Mainnet. Most users should look for a free or better-documented alternative first, since the available description does not explain what the server does.
- Requirements
- A remote SSE endpoint at the provider's host; no local runtime or package is needed. A wallet able to produce an EIP-3009 TransferWithAuthorization signature, sent in the Payment-Signature header, and enough USDC on Base Mainnet to cover the stated charge per request. No account or API key is declared.
Installation
In SourceWeft
- Open Execute context-window-optimizer-mcp in the dashboard and add it to a workspace.
- 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%2Fcontext-window-optimizer-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": {
"execute-context-window-optimizer": {
"type": "sse",
"url": "https://api.m2mcent.com/context-window-optimizer-mcp/sse"
}
}
}Tools
0Version history
1- v2.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.