Developer · Remote MCP server
Zephex
MCP gateway with 10 tools for code analysis, architecture, package audit & security.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.Tanbir404/zephex- Version
- 1.0.0
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP
- Published
- 2026-05-12
- Updated
- 2026-05-12
- Publisher
- Tanbir404 (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/Tanbir404) · how
- Website
- zephex.dev
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://zephex.dev/mcp | Authorization (required, secret) |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 404)
- Handshake
- HTTP 404
- Checked on
- 2026-10-05
How to connect Zephex
Zephex is a remote MCP server: there is nothing to install. Its endpoint is https://zephex.dev/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
The registry entry declares an HTTP header for the connection: Authorization (required, secret). A secret header usually carries an API key or token issued by the service; clients that accept custom headers set it with the server's URL.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| Zendriver MCPUndetectable browser automation for LLM agents, spoken over MCP. | Local · stdio |
| ZenLink MCPBrowser automation for MCP clients via Zen Browser. Parallel multi-tab, content extraction. | Local · stdio |
| Zenrows MCPZenrows MCP server - Fetch, Extract, Batch, and Browser Sessions for AI coding assistants. | Remote & Local · HTTP, stdioLive check: sign-in required |
| Zentric Protocol MCPPrompt injection + PII detection for LLM apps and agent pipelines. Deterministic, sub-25ms. | Local · stdio |
| Zephyr Scale MCPZephyr Scale on self-hosted Jira Server/DC: test cases, cycles, executions, plans and attachments. | Local · stdio |
| zermAgent utility belt: memory, locks, webhook inboxes, timers, DNS, email, URL, timezone, cron. | Remote · HTTPLive check: ✓ handshake |
| Zero Core ToolsWeb scraping, code review, content gen, sentiment. Zero Core Tools. | Remote & Local · HTTPLive check: ✓ handshake |
| Zero Core VerifyPost-tx outcome verification via LLM-as-judge. Zero Core Verify. | Remote & Local · HTTPLive check: ✓ handshake |