INDIVIDUAL MCP TOOL

audit_headers

Audit a public HTTPS URL the user deployed — security grade A–F, SSL, headers, cookies, health (ALIVE/DEGRADED/BROKEN), exposed secrets, tech stack.

zephex.devnone authenticationAvailability not checked

LIVE ENDPOINT

https://zephex.dev/mcp

No auth detected

Connect to this endpoint to inspect the live schema for audit_headers and invoke it with your own arguments.

{}

Inferred read-only · medium confidence · heuristic, not a guarantee.

CONNECT WITH APPROVAL

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.zephex]
url = "https://zephex.dev/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "zephex": {
      "type": "http",
      "url": "https://zephex.dev/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: zephex
Remote MCP URL: https://zephex.dev/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "zephex": {
      "url": "https://zephex.dev/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "zephex": {
      "type": "http",
      "url": "https://zephex.dev/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "zephex",
  "transport": "streamable-http",
  "url": "https://zephex.dev/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

check_package — Verify a public registry package before the agent recommends, installs, or changes a dependency.
check_test — Run the project's real test suite and return structured health — the same engine as the terminal command zephex check test.
explain_architecture — Map how files in the user's project connect — which files are hubs, what imports what, where auth/API/database live.
find_code — Search the user's project when you do not know which file holds something.
get_project_context — Answer what the user's project is — name, stack, how to run/test/build, auth, database, deploy, folder layout — from their files on disk, not from training data.
keep_thinking — Structure multi-step debugging and planning across tool calls — not a one-shot think.
project_memory — Save project notes that must survive this chat — rules, conventions, decisions, gotchas, preferences.
read_code — Read a known symbol or file from the user's project without dumping the whole tree.