@arcwall/mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ARCWALL_API_KEY | Yes | Your API key from https://arcwall.io |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| arcwall_scan_secretsB | Scan workspace for hardcoded API keys, passwords, private keys, tokens, and credentials. Run before committing or deploying. |
| arcwall_scan_mcpA | Scan MCP server configurations for prompt injection, excessive permissions, and unverified server origins. Scans .cursor/mcp.json, .vscode/mcp.json, .claude/mcp.json and other MCP config files. |
| arcwall_scan_agent_instructionsA | Scan agent instruction files for security vulnerabilities. Covers CLAUDE.md, .cursorrules, .windsurfrules, AGENTS.md and other formats. Detects prompt injection, sensitive data, and missing guardrails. |
| arcwall_threat_modelB | Generate a STRIDE threat model for the current codebase. Identifies trust boundary gaps, authorization issues, data flow exposures, and architectural risks. Results saved to Arcwall dashboard. |
| arcwall_check_promptA | Test a system prompt for injection vulnerabilities, jailbreak susceptibility, missing guardrails, and excessive agency. Include test messages to check multi-turn vulnerabilities. |
| arcwall_pre_commitA | Security check before committing. Scans staged files for secrets and checks MCP configs. Returns CLEAR TO COMMIT or BLOCKED with issues to fix. |
| arcwall_scan_dependenciesA | Check dependencies for known CVEs. Scans package.json for vulnerable packages with safe version recommendations. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Each tool targets a distinct security concern: prompt injections, pre-commit checks, agent instructions, dependencies, MCP configs, secrets, and threat modeling. No two tools overlap in purpose.
All tools share the 'arcwall_' prefix and use descriptive verb-noun or noun phrases. Minor inconsistency: 'check' vs 'scan' verbs, but overall pattern is clear and predictable.
Seven tools cover the essential scanning and security assessment needs for a development workflow. The count is well-scoped without being too few or too many.
Covers major security scanning areas (prompts, secrets, dependencies, configs). Minor omission might be runtime monitoring, but the set is fairly complete for its stated purpose.