Zephex
Run hosted code analysis, architecture review, package audit, and security checks through Zephex’s 10-tool MCP gateway from your agent.
Overview
Zephex is a MCP server for the Ship phase that provides a hosted gateway with 10 tools for code analysis, architecture review, package audit, and security checks.
What is this MCP server?
- Hosted streamable-HTTP MCP at zephex.dev/mcp with Bearer mcp_sk API key
- 10 MCP tools spanning code analysis, architecture, package audit, and security
- Remote gateway—no local clone required for tool invocation
- Version 1.0.0 with dashboard auth at zephex.dev/dashboard
- 10 MCP tools advertised for analysis, architecture, package audit, and security
- Registry version 1.0.0
- Remote endpoint https://zephex.dev/mcp with required Bearer authorization
What problem does it solve?
You ship with scattered npm audit tabs and ad-hoc reviews because your agent lacks one authenticated pipeline for architecture and security analysis.
Who is it for?
Indie devs shipping Node or polyglot repos who want agent-driven package and security passes via a single remote MCP.
Skip if: Air-gapped-only workflows or teams that refuse cloud tokens on codebase metadata.
What do I get? / Deliverables
After you connect Zephex, your agent can run consolidated analysis and audit tools before merge or release.
- Agent-invoked architecture, code, package, and security findings from 10 Zephex tools
- Pre-release audit trail you can paste into PR or ship checklists
Recommended MCP Servers
Journey fit
How it compares
Authenticated cloud analysis MCP with 10 tools, not a local-only grep skill or generic linter config.
Common Questions / FAQ
Who is Zephex for?
Solo builders and small teams using MCP agents who need code, architecture, package, and security analysis from zephex.dev without maintaining local scanner glue.
When should I use Zephex?
Use it in Ship security and review before releases, and again after major dependency or architecture changes during Build.
How do I add Zephex to my agent?
Create a Bearer token on zephex.dev/dashboard, add remote MCP https://zephex.dev/mcp with the Authorization header, and connect from Claude Code, Cursor, or any streamable-http MCP client.