Monitor · Audit · Alert · Discover

The ops layer

MCP was missing.

Teams run 10–20 MCP servers with no visibility into which are slow, which fail silently, or which tools are called most. MCPHub is the control plane they're missing.

mcphub.dev/dashboard

Total Servers

14

Healthy

12

Tool Calls (24h)

2,847

Avg Latency

23ms

ServerStatusLatencyCalls (24h)
filesystem-mcphealthy2ms1,247
github-mcphealthy18ms891
postgres-mcpwarning124ms432
slack-mcphealthy34ms203

Servers Supported

unlimited

100%

Tool Calls Captured

via transparent proxy

<1s

Real-time Latency

WebSocket push

<5s

Alert Delivery

Slack + webhook

The Problem

MCP went from zero to ubiquitous in 8 months.

The protocol is everywhere. The tooling layer doesn't exist yet. Teams manage their MCP servers the same way they managed servers before Kubernetes — manually, with prayer.

Zero visibility

No way to know which servers are slow, which fail silently, or which tools are called most.

Silent failures

Servers degrade. Latency spikes. Error rates climb. Nobody knows until users start complaining.

Ad hoc management

No registry. No audit trail. No cost visibility. Just scattered configs and tribal knowledge.

Agents

Five agents. One control plane.

Each agent handles a specific layer of the ops stack. Together they give you complete coverage of your MCP infrastructure — from discovery to alerting.

Server Registry

Catalog of all MCP servers with metadata, version, and owner. One place to discover what's running.

Health Prober

On-demand pings measuring latency, error rate, and availability across every registered server.

Tool Call Logger

Intercepts every tool invocation through the transparent proxy — duration, output size, caller identity.

Usage Analytics

Which tools get called most, by which agents, at what cost. Pre-aggregated hourly for instant queries.

Alert System

Configurable rules fire when a server degrades or goes offline. Slack webhook + generic HTTP delivery.

More in v0.2
Architecture

How it works.

MCPHub sits as a transparent reverse proxy in front of your MCP servers. Zero changes required to existing infrastructure.

01

Register your servers

Add MCP server endpoints to the registry. MCPHub stores metadata, ownership, and connection details.

02

Route through the proxy

Point your MCP clients to MCPHub's transparent proxy. Zero changes to your existing servers required.

03

Monitor in real-time

Watch live health status, tool call volume, and latency on the dashboard via WebSocket push.

04

Get alerted on failures

Configurable alert rules fire via Slack or webhook when servers degrade or go offline.

Request flow

MCP Client

Claude / Agent

MCPHub Proxy

/proxy/{id}/mcp

MCP Server

filesystem / github

PostgreSQL

audit log + analytics

Redis

pub/sub · streams · cache

WebSocket

real-time push

Get Started

Start monitoring your

MCP layer today.

The gap is wide open. Be the team with visibility before everyone else catches up.

Open Dashboard