Skip to main content
The Servers page in Ultra Hub provides visibility into all upstream MCP servers used across your organization. See which servers are active, how they’re performing, and who’s using them.

Server List

The main view shows a card for each MCP server with key metrics: Click any server card to view detailed information.
The transport badge is derived from the most recent trace for each server, so it reflects how the server is actually being reached. Older traces recorded before this field was captured appear without a badge.

Blocking a server

Admins see a Block action on each row. Clicking it opens a confirmation dialog and creates an organization-wide rule that denies every tool call to that server, for every user. Blocked servers can be reviewed, edited, or unblocked from the Governance page.

Server Detail View

The detail view provides in-depth metrics and breakdowns for a single server. The server’s transport type (stdio, http, or sse) appears as a badge next to the server name in the page header, making it easy to tell at a glance how Ultra is reaching the server.

Stats Overview

At the top, summary cards show:
  • Total Requests — Lifetime request count
  • Success Rate — Overall success percentage
  • Errors — Total error count
  • Tools — Number of unique tools available
  • Avg Latency — Average response time

Tools Tab

A table of every tool called on this server: Use this to identify your most-used tools, spot error-prone tools, and find performance bottlenecks.

Gateways Tab

Shows which gateways are routing traffic to this server:

Users Tab

Shows which users are interacting with this server:

Requests Tab

A full paginated trace history for this server. Each entry links to the detailed trace view. Use Load More to page through older requests. In Hub mode, both this tab and the Overview preview show who made each request, linked to that user’s identity.

Use Cases

  • Performance monitoring — Identify slow servers or tools that need optimization
  • Usage analysis — Understand which servers and tools your team relies on most
  • Troubleshooting — Drill into error patterns by server, tool, gateway, or user
  • Capacity planning — Track request volumes and gateway counts to plan infrastructure