# Briefme Agenda Timer MCP server

Source: https://glimind.com/server/mcp-registry%2Fus.briefme%2Fagenda-timer
Registry id: `mcp-registry/us.briefme/agenda-timer`
Status: live (checked 2026-10-27T02:27:24.597Z)

## Verdict

Briefme Agenda Timer MCP server answered 99.93% of Glimind's liveness checks over 30 days, better than 32% of MCP servers, with 1286 ms median handshake and 8 outages in 90 days. Its agent-readiness grade is A (98/100) across 12 tools, costing an agent about 3,493 tokens to load. Checked every few minutes; no tool is ever called.

## Measurements (30 days)

| Metric | Value | Better than |
|---|---|---|
| Uptime, 30 days | 99.93% | 32% of MCP servers |
| Median handshake latency | 1286 ms | 13% of MCP servers |
| p95 handshake latency | 3994 ms | — |
| Checks in 30 days | 4,906 | — |
| Outages, 90 days | 8 | — |
| Median recovery | 7 min | — |
| Agent-readiness score | 98/100 (A) | 92% of MCP servers |
| Tools | 12 | — |
| Tool-list size for an agent | ~3,493 tokens | 43% of MCP servers |
| Days observed | 29 | — |

## Install

```json
{
  "mcpServers": {
    "briefme-agenda-timer-mcp-server": {
      "type": "http",
      "url": "https://briefme.us/mcp"
    }
  }
}
```

Claude Code:

```sh
claude mcp add --transport http briefme-agenda-timer-mcp-server https://briefme.us/mcp
```

## Tools (12)

- `add_block`: Adds one block to an existing agenda: at the end, above a final wrap-up, or directly after after_block_id. Adds only — it does not reorder or change any existin
- `create_agenda`: Creates a timed meeting agenda — a shareable countdown timer that walks attendees through timeboxed topics in sync. Use when the user wants a meeting timer, tim
- `delete_agenda`: Deletes an agenda and its timer history permanently. Its share and edit links stop working the moment this returns, and nothing can be recovered. Meant for an a
- `get_agenda`: Reads back the current state of an agenda, including the id of every block. Needed when block ids are unknown — for example at the start of a new conversation; 
- `get_shared_agenda`: Reads the public agenda behind a BriefMe share link — the same blocks, timings and timer status the link's own page shows. Use when someone has a BriefMe share 
- `list_agendas`: Lists every agenda saved in the signed-in BriefMe account, newest first, with the share_token every other tool takes. Useful at the start of a conversation when
- `release_agenda`: Takes one agenda out of the BriefMe account to free a slot. The agenda is not deleted now: its share link keeps working for 7 more days and then it expires like
- `remove_block`: Removes one block from an agenda. The remaining blocks keep their ids and their order. An agenda must keep at least one block, so this fails on the last one. Re
- `reorder_blocks`: Puts the agenda's blocks into the order given. block_ids must contain every current block id exactly once — none missing, none extra, none repeated. This only r
- `rotate_edit_token`: Replaces an agenda's edit token and edit link with new ones. The previous edit_token and edit_url stop working the moment this returns, for every assistant, bro
- `update_agenda`: Renames the agenda. Blocks are untouched — the block tools change those. Returns the full updated agenda.
- `update_block`: Changes one block, identified by block_id. Only the supplied fields change; anything omitted keeps its current value exactly, so a one-field edit is a one-field

Measured by Glimind (https://glimind.com): MCP handshake + tool list only, no tool is ever called. CC BY 4.0.