Documentation Index
Fetch the complete documentation index at: https://docs.ultra.security/llms.txt
Use this file to discover all available pages before exploring further.
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:
| Metric | Description |
|---|
| Server Name | The configured name of the upstream server |
| Transport | Badge showing the transport used to reach the server (stdio, http, or sse) |
| Request Count | Total number of MCP requests handled |
| Success Rate | Percentage of requests that completed successfully |
| Unique Tools | Number of distinct tools called on this server |
| Avg Latency | Average response time in milliseconds |
| Gateways | Number of gateways routing traffic to this server |
| Users | Number of users interacting with this server |
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
A table of every tool called on this server:
| Column | Description |
|---|
| Tool Name | The MCP tool identifier |
| Calls | Total number of times this tool was called |
| Success | Number of successful calls |
| Errors | Number of failed calls |
| Avg Latency | Average response time for this tool |
Gateways Tab
Shows which gateways are routing traffic to this server:
| Column | Description |
|---|
| Gateway | Gateway name (resolved from the gateway ID) |
| Requests | Total requests from this gateway |
| Success | Successful request count |
| Errors | Error count |
| Avg Latency | Average latency from this gateway |
Users Tab
Shows which users are interacting with this server:
| Column | Description |
|---|
| User | User name or email |
| Requests | Total requests from this user |
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.
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
