mcpserver.lol
registry/sipcode
Connection check local install

sipcode

Context hygiene for Claude Code: drift detection, re-read dedup, and token analytics.

Tools 15
GitHub stars 46
Installs / wk
Licence MIT
Transport stdio
Last checked never

Tools & capabilities

15 tools

Read from the published package source — this server runs locally, so there is no endpoint to query. Names are taken from the code, not observed at runtime, and descriptions are often absent.

audit_latest_session from source
Audit a Claude Code session and return a JSON report of where tokens went: total spend, output ratio, duplicate file reads, idle context, top expensive tool calls, and an estimate…
estimate_task_cost from source
Predict what a coding task will cost across models (Opus / Sonnet / Haiku) before the user runs it. Returns a JSON cost prediction with a confidence band and per-model token estima…
forecast_monthly_spend from source
Projects month-end Claude spend at the user
get_agent_score from source
Run Sipcode
get_drift_report from source
Detect context/cost drift: whether the user
get_project_manifest from source
Return the Sipcode project manifest for a given directory. The manifest is a compressed <2k-token codebase map (file tree, hot files, framework fingerprint, detected patterns) gene…
get_proxy_stats from source
Return aggregated Sipcode proxy rewrite stats: total invocations, per-rewriter counts, and estimated saved tokens (heuristic). Use when the user asks
get_proxy_status from source
Report whether the Sipcode proxy is installed plus its accumulated rewrite stats. Read-only. Use when the user asks
get_session_stats from source
Return cross-session token analytics (totals, per-session breakdown, top expensive sessions) as JSON, read from the local Claude Code transcripts. Use when the user asks
get_sipcode_info from source
Return the installed Sipcode version, the list of registered MCP tools, the Node runtime version, and the host platform. Use this whenever the user asks
get_today_summary from source
Daily dashboard — answers
install_proxy from source
Install the Sipcode runtime proxy: writes the PreToolUse hook and registers it in ~/.claude/settings.json so Claude Code rewrites tool inputs for compact output. WRITES to settings…
list_recent_sessions from source
List the user
uninstall_proxy from source
Remove the Sipcode proxy hook from ~/.claude/settings.json and delete the hook script. WRITES to settings.json. Use when the user asks to
verify_sipcode_impact from source
Prove that Sipcode is actually saving the user tokens by A/B-comparing their token spend before vs after they installed Sipcode