Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add commands/superclaude-org/superclaude_plugin/verify-mcpgit clone --depth 1 https://github.com/SuperClaude-Org/SuperClaude_PluginWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/commands/superclaude-org/superclaude_plugin/verify-mcp)<a href="https://agentmods.dev/commands/superclaude-org/superclaude_plugin/verify-mcp"><img src="https://agentmods.dev/badge/commands/superclaude-org/superclaude_plugin/verify-mcp.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00007 | $0.00620 |
| Opus 5 | $0.00003 | $0.00310 |
| Sonnet 5 | $0.00001 | $0.00124 |
| Haiku 4.5 | $0.00001 | $0.00062 |
Grade B, and why
verify-mcp scanned grade B with 1 finding against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 6d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
cat ~/.claude/settings.local.json | grep -A 5 "airis-mcp-gateway" || echo "Not found in user settings" How it starts
The opening of the file, as written. The whole thing — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/sc:verify-mcp - MCP Server Verification
You are now in MCP Verification Mode. Your goal is to check the status of MCP servers and guide the user through any necessary setup.
Verification Steps
1. Check Prerequisites
# Check if uvx is available
uvx --version
# Check if the plugin's MCP server configuration exists
cat ~/.claude/settings.local.json | grep -A 5 "airis-mcp-gateway" || echo "Not found in user settings"
2. Check MCP Server Status
Use the Bash tool to check:
# List configured MCP servers
claude mcp list
# Test AIRIS MCP Gateway connection (if available)
claude mcp get airis-mcp-gateway
3. Report Status
Provide a clear status report:
✅ Working:
- List MCP servers that are properly configured and responding
- Confirm which tools are available
⚠️ Needs Attention:
- Missing prerequisites (e.g., uvx not installed)
- MCP servers configured but not responding
- Missing optional API keys
❌ Not Configured:
- MCP servers that should be available but aren't configured
4. Provide Guidance
For any issues found, provide specific commands to fix them:
Missing uvx:
# Install uv (includes uvx)
pip install uv
# or
brew install uv
Plugin MCP Not Starting:
# Check plugin is installed
/plugin list
# Reinstall plugin if needed
/plugin update sc@superclaude-official
Missing API Keys (optional):
# Add to your shell profile (~/.zshrc, ~/.bashrc, etc.)
export TAVILY_API_KEY="your-key-here"
export TWENTYFIRST_API_KEY="your-key-here"
5. Troubleshooting
If AIRIS MCP Gateway is not working:
- Check logs: Look for error messages in Claude Code output
- Test uvx directly:
uvx --from git+https://github.com/agiletec-inc/airis-mcp-gateway airis-mcp-gateway --help - Verify network access: Ensure you can access GitHub
- Check Claude Code version: MCP server support requires recent version
Summary Format
Present findings in a clear table:
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 6d ago First seen · 101 lines · 7 tokens per session scan B 3fb23558fdf5
verify-mcp is a command published in the GitHub repository SuperClaude-Org/SuperClaude_Plugin (55 stars, last pushed 15d ago), licensed MIT. It adds 7 tokens to every session and 620 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.