From cybersec-toolkit
Validates MCP server Python sources are in sync with bash source-of-truth definitions for tools, profiles, Docker images, and pipx binary names.
How this skill is triggered — by the user, by Claude, or both
Slash command
/cybersec-toolkit:mcp-sync-checkThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
The MCP server hardcodes data that's also defined in bash. Drift breaks AI tool suggestions silently.
The MCP server hardcodes data that's also defined in bash. Drift breaks AI tool suggestions silently.
| Python (mcp_server/) | Bash (lib/, scripts/, profiles/) |
|---|---|
tools_db.py → PIPX_BIN_NAMES | scripts/verify.sh → _PIPX_BIN_NAMES |
tools_db.py → MODULE_DESCRIPTIONS | lib/common.sh → MODULE_DESCRIPTIONS |
tools_db.py → DOCKER_IMAGES | lib/installers.sh → ALL_DOCKER_IMAGES |
profiles.py → PROFILES | profiles/*.conf files |
python3 scripts/validate_mcp_sync.py
Output:
0 errors → both sides match. Done.lib/installers.sh → ALL_DOCKER_IMAGES+=("img|label") →
mcp_server/tools_db.py → add to DOCKER_IMAGES dict.
scripts/verify.sh → _PIPX_BIN_NAMES["pypi-name"]="bin-name" →
mcp_server/tools_db.py → add to PIPX_BIN_NAMES dict.
lib/common.sh → MODULE_DESCRIPTIONS["mod"]="desc" →
mcp_server/tools_db.py → add to MODULE_DESCRIPTIONS dict.
profiles/myprof.conf → set PROFILE_DESC and MODULES →
mcp_server/profiles.py → add to PROFILES dict with same modules list.
This is rare and usually wrong. Bash is the source of truth. If a tool is only known to MCP, the install side won't be able to install it. Fix bash first, then mirror.
Re-run:
python3 scripts/validate_mcp_sync.py
cd mcp_server && uv run --group dev pytest tests/ -q
Both must pass.
npx claudepluginhub 26zl/cybersec-toolkit --plugin cybersec-toolkitHandles Claude Code MCP integration: installs/manages servers (HTTP/SSE/stdio), scopes, enterprise configs, OAuth auth, resources/@mentions, prompts, limits, security; delegates to docs-management.
Detects MCPProxy connection by checking for mcp__MCPProxy__* tools, suggests /mcp reconnect if missing, and guides MCP tools usage over HTTP API for debugging.
Checks and configures MCP servers in .mcp.json for project integration. Use for setup, status checks, adding core servers like context7 and sequential-thinking, or specific ones like playwright.