Slim Guard MCP server
76% fewer MCP tokens in our standard benchmark. Same upstream call. Exact recovery.
188 stars29 downloads/wk
Reviews
Write oneNobody has reviewed Slim Guard yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Slim Guard tools (3)
write = sends, deletes, buys or postsRead from the package source without running it. The installed server may list more.
addAdds two numbers and returns the result
echoEchoes back the input message
get_timeReturns current timestamp as ISO string
Public scan report
scanner v0.1.9 · 2026-09-24 · same rubric, same numbers if you re-run it
- Code scan63 source files scanned25/25
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitylocal package, no credentials required12/15
- Maintenancelast push 42 days ago12/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
What the publisher says
From the Slim Guard repository's README, as published. We do not edit it. Read it on GitHub
MCP Slim Guard
MCP Slim Guard gives a host one deliberate way to reach authorized upstream tools. It keeps input schemas intact, validates calls before the upstream is invoked, and can recover an oversized result exactly without repeating that invocation.
Choose a mode
Compact is the default for start. Native is the default installation plan for Codex. Compact is the default for Claude Code; Claude Code supports Compact and Extreme installation plans, not Native.
All modes apply the same allow/deny authorization. Compact and Extreme return at most three discovery matches, each with the original required fields, enums, and nested schema. A call is validated against that original schema before the upstream server is contacted.
find_tool rejects unknown fields and queries longer than 256 Unicode code points locally. It searches only the current authorized catalog and never falls back to an unauthorized entry.
Quick start
0.1.1-alpha.2 is a source candidate and is not published to npm yet. From a reviewed checkout of this candidate:
npm ci
npm run build
npm link
cd /path/to/project-with-mcp-config
mcp-slim-guard init
mcp-slim-guard validate
# Run the default Compact mode.
mcp-slim-guard startinit writes mcp-slim-guard.yml with version 2. The file contains upstream and security settings only. Select a mode in the host command, not in YAML.
# Inspect a host-specific plan without changing host files.
mcp-slim-guard plan --host codex
mcp-slim-guard plan --host claude-code --mode extreme
# Verify the configured runtime without changing Host configuration or calling a business Tool.
mcp-slim-guard verify --host codex
# Apply a reviewed plan.
mcp-slim-guard install --host codex --mode nativeHost entries
For Codex, use Native when you want the normal authorized MCP catalog:
[mcp_servers.slim_guard]
command = "mcp-slim-guard"
args = ["start", "--mode", "native"]
cwd = "/absolute/path/to/project"For Claude Code, use Compact by default:
{
"mcpServers": {
"slim-guard": {
"command": "mcp-slim-guard",
"args": ["start", "--mode", "compact"],
"cwd": "/absolute/path/to/project"
}
}
}See host setup for the full configuration and verification steps.
Configuration
version: 2
tools:
allow:
- "upstream_*"
deny:
- "*_delete_*"
ssrf:
mode: block
block_private_ips: true
allow_domains: []
block_domains: []
rate_limit:
default: "60/min"
injection_detection:
enabled: true
sensitivity: medium
mode: block
audit:
output: file
filePath: mcp-slim-guard-audit.log
servers:
upstream:
command: npx
args: ["-y", "@your/mcp-server"]Version 1 configuration is intentionally unsupported. The removed compressor section is rejected rather than migrated automatically.
Repair an invalid call
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Install directly
Runs npx -y mcp-slim-guard on your machine. Read the scan report first; the gateway never runs local packages.
claude mcp add mcp-slim-guard -- npx -y mcp-slim-guard
Slim Guard: common questions
- Is Slim Guard MCP server safe?
- Yes, by our scan: it is graded A (88/100). Read the Slim Guard safety report
- How do I install Slim Guard?
- It runs on your machine. Copy the Claude Code, Claude Desktop or Cursor config from the install section.
- Does Slim Guard need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is Slim Guard maintained?
- The last commit was 42 days ago (2026-08-14). The latest release is v0.1.1-alpha.1.
- What can I use instead of Slim Guard?
- Servers from other publishers that do the same job: Codebase Memory MCP server, Honcho MCP server and Trace MCP server. Compare all Slim Guard alternatives.
Alternatives to Slim Guard
Same job from other publishers: the closest match first, then the best rated.
- Codebase MemoryCodebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.not reviewedWidely usedC
- HonchoMemory that reasons: continual learning for stateful agents. Better context, fewer tokens.not reviewedEstablishedA
TraceCode graph MCP: 81 languages, 88 frameworks, 72.7% fewer PR-review tokens, comprehension at paritynot reviewedEstablishedA