Zephex

io.github.Tanbir404Published by GitHub account Tanbir404v1.0.0Updated Oct 24, 2026

MCP gateway with 10 tools for code analysis, architecture, package audit & security.

VerifiedStreamable HTTPWeb executableDeveloper ToolsSecurity & Monitoring

Overview

AI-generated overview

A remote MCP gateway offering ten tools for code analysis, architecture review, package auditing and security checks.

What you can do
Zephex is a hosted MCP gateway that exposes ten tools covering code analysis, architecture review, package auditing and security checks. The assistant connects to it over streamable HTTP at a remote endpoint, so the analysis runs on the provider's side rather than locally. The manifest does not list the individual tools, so the exact capabilities are only described at a high level.
When to use it
Worth considering when you want an assistant to inspect code, review architecture, or audit dependencies and security without running a local analysis tool. Less suitable if you need to know the exact tool set in advance or must keep source code on your own machine.
Requirements
A remote MCP client that supports streamable HTTP. A bearer token is required, sent in the Authorization header, obtained from the provider's dashboard. No local runtime or packages are needed.
Before you install
The required Authorization bearer token is a secret; keep it out of logs and shared configurations. Code and repository content sent to the tools is processed by a third-party hosted service, so consider whether that is acceptable for private or proprietary code. The manifest does not list the tools, so review what each one does before use.

Installation

In SourceWeft

  1. Open Zephex in the dashboard and add it to a workspace.
  2. Connect Authorization token credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.Tanbir404%2Fzephex/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "zephex": {
      "type": "http",
      "url": "https://zephex.dev/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.