CodeWallDocs
Reference

Access Requirements

Network and infrastructure prerequisites for CodeWall to reach your targets.

Network access

CodeWall's testing infrastructure must be able to reach your target over the network.

Public targets

No special configuration needed. If your application is accessible from the public internet, CodeWall can test it.

Private / firewalled targets

If your target is behind a firewall or IP allowlist, add CodeWall's IP ranges. See Configure Server Access for instructions.

Port requirements

PortProtocolPurpose
443HTTPSPrimary — most web applications and APIs
80HTTPRedirect testing, non-TLS applications
CustomTCPAny custom port your application runs on

CodeWall will test on whatever port your target is accessible on. Specify custom ports in the target URL (e.g., https://app.example.com:8443).

DNS resolution

The target hostname must resolve to a routable IP address from CodeWall's infrastructure. If your target uses:

  • Public DNS — no configuration needed
  • Private DNS — contact support for custom DNS setup
  • IP-only access — provide the IP address directly as the target

TLS / SSL

  • CodeWall supports TLS 1.2 and 1.3
  • Self-signed certificates are supported (the agent will accept them)
  • CodeWall will flag SSL/TLS weaknesses as informational findings

MCP server requirements

For MCP server testing, CodeWall needs to connect to the server over one of two transports:

TransportRequirement
SSEA publicly reachable SSE endpoint URL
stdioA shell command to start the server process, plus any required environment variables

The server must respond to standard MCP protocol messages including tool listing and tool invocation.

LLM application requirements

For LLM application testing, CodeWall needs:

RequirementDescription
API endpointA reachable HTTP endpoint for the chat or completion API
Request formatOpenAI-compatible, Anthropic Messages API, or a custom Jinja2 template
Response extractionFor custom formats, a JSONPath expression to extract the assistant response