> ## Documentation Index
> Fetch the complete documentation index at: https://docs.getmcpulse.com/llms.txt
> Use this file to discover all available pages before exploring further.

# The MCP list

> The home screen: every tracked server, its calls in the last 30 days, and its first-call success rate.

`/` is the MCP list — one full-width row per tracked server.

| Column             | What it shows                                                |
| ------------------ | ------------------------------------------------------------ |
| Name               | What you called it                                           |
| Created            | When the MCP was made                                        |
| Calls (30d)        | Tool calls in the last 30 days                               |
| First-call success | The share of calls that got what the model wanted first time |

**Thirty days, because that is what the [overview](/metrics/overview) opens on**, and both figures say so on the row.

It was seven, and the same server then read 2,027 calls at 84% on the row and 3,680 at 86% one click in — two correct answers to two different questions, with only the calls column carrying a window. Nobody reads that as two windows; they read it as the list being out of date, and they are right to, because nothing on the row said otherwise. The row is the page's opening figure, so clicking through has to confirm it.

## It refreshes like every other panel

Both figures come from `tool_hours`, so this page polls on the same 30-second metrics cadence as the overview. It was the one screen that did not: the home page held numbers that went stale the moment it loaded, while the overview one click in refreshed itself — two answers to *is this current* about the same server.

## A row does one thing

Clicking a row opens the MCP. There is nothing else on it.

Renaming, keys and deletion all live **inside** the MCP, which means there is nothing destructive sitting beside the link people click all day — and one place to change each rather than two.

## Zero is an answer

A server that has never been called shows `0` and `0%`, not a dash and not an empty state. Nothing recorded reads as zero, never as "not yet": a complete answer of *nothing happened* is worth more than a shrug.

The one exception is a genuinely unknown figure. First-call success is computed by the [nightly pass](/api/concepts/nightly-pass), so an MCP whose only calls arrived today has calls but no rate yet — that reads as *not yet computed*, because a zero there would claim every call failed.

## Search

The list carries its own search box in its header, always rendered. It matches on name.

## The sample sorts last

Every new account is seeded with a [sample MCP](/mcps/sample), badged as one and sorted below your own servers — or the customer's own MCPs sit underneath ours forever.

## Creating one

**New MCP** opens a slide-over. Every panel in MCPulse that asks something of you is a slide-over, including the confirms. See [Create an MCP](/mcps/create).