# BriefMe (remote · briefme.us)

Meeting agenda timer for AI assistants: build agendas in chat, share a live synced countdown.

- Trust score: 78/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-24

## Components

- remote · `briefme.us`: 78/100 (this document), [markdown](https://verifymcp.io/servers/us-briefme-agenda-timer/briefme.md), [page](https://verifymcp.io/servers/us-briefme-agenda-timer/briefme)

## Channel facts

- Endpoint: `https://briefme.us/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-24.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (update_agenda).
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 70/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1795 tokens (~224/item across 8 items; 8 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 87/100
  - Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the BriefMe MCP server?

BriefMe is a hosted endpoint at https://briefme.us/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http us-briefme-agenda-timer 'https://briefme.us/mcp'
```

### Cursor

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

### VS Code

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

### Codex

```toml
[mcp_servers.us-briefme-agenda-timer]
url = "https://briefme.us/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "us-briefme-agenda-timer": {
      "type": "remote",
      "url": "https://briefme.us/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add us-briefme-agenda-timer --url 'https://briefme.us/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  us-briefme-agenda-timer:
    url: "https://briefme.us/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "us-briefme-agenda-timer": {
      "Transport": "http",
      "Url": "https://briefme.us/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add us-briefme-agenda-timer -t streamable-http -u 'https://briefme.us/mcp'
```

### Other

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

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-24 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-21 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-19 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-17 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-15 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-13 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-12 (score 72, 0)

- [security] Tool “add_block” rewrote its description, which is the text the model reads
- [cosmetic] “add_block” reworded the description of “after_block_id”

### 2026-09-11 (score 72, +4)

- [security improvement] Injection markers: fail → pass
- [security] The server rewrote its instructions, which are the text every model session reads
- [security] New tool “rotate_edit_token”, which the server declares destructive
- [security] Tool “add_block” rewrote its description, which is the text the model reads
- [security] Tool “create_agenda” rewrote its description, which is the text the model reads
- [security] Tool “get_agenda” rewrote its description, which is the text the model reads
- [security] Tool “reorder_blocks” rewrote its description, which is the text the model reads
- [security] Tool “update_agenda” rewrote its description, which is the text the model reads
- [security] Tool “update_block” rewrote its description, which is the text the model reads
- [security] Tool “update_agenda” is now declared destructive
- [security] Tool “update_block” is now declared destructive
- [functional improvement] Schema quality: 316 → 224
- [functional improvement] Tool “add_block” now declares an output schema
- [functional improvement] Tool “create_agenda” now declares an output schema
- [functional improvement] Tool “get_agenda” now declares an output schema
- [functional improvement] Tool “remove_block” now declares an output schema
- [functional improvement] Tool “reorder_blocks” now declares an output schema
- [functional improvement] Tool “update_agenda” now declares an output schema
- [functional improvement] Tool “update_block” now declares an output schema
- [functional] First check of Tool coverage: 100
- [cosmetic] “update_block” reworded the description of “block_type”
- [cosmetic] “add_block” reworded the description of “block_type”

## MCP tools (8)

### `create_agenda` (~367 tokens)

Create a meeting 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, timeboxes, a run of show, a workshop or standup schedule, or to keep a meeting on time. Not for calendar scheduling or note-taking, and a two-item chat needs no timer.

Returns edit_url (the private control page: start, pause, advance and finish the meeting, and edit blocks by hand), share_url (the read-only live timer for attendees, safe to post anywhere) and edit_token (needed by every other BriefMe tool, and the only way back into this agenda). The user needs both links.

When the blocks depart from BriefMe's standard shape — an opening, a wrap-up, planned breaks — the result also carries structure_suggestions, each naming the block to add and its length; add_block and reorder_blocks apply them.

Block durations add up to the meeting length; when none is given, a standup is about 15 minutes, a 1:1 about 30, sprint planning 60 to 90. Most agendas are three to eight blocks. Titles are read off a wall-sized countdown, so six words or fewer read best; a description is useful only when the title alone is ambiguous.

Agendas expire after 7 days and cannot be recovered afterwards.

Input parameters:

- `blocks` (array, required): The agenda blocks, in the order they will run.
- `language` (string): The user's conversation language as a two-letter ISO 639-1 code (e.g. 'de'). Localizes the standard block titles quoted in structure_suggestions. Unsupported values fall back to English.
- `title` (string, required): Short name for the meeting, e.g. "Weekly engineering sync".

Output parameters:

- `blocks` (array): The blocks in the order they run.
- `edit_token` (string): What every other tool takes. Keep it for the rest of the conversation.
- `edit_url` (string): The user's private control page. Give it to the user; never post it anywhere shared.
- `expires_at` (string|null): ISO 8601. null when the agenda is saved to an account and does not expire.
- `instructions` (string): Read this first: how to reply to the user.
- `share_url` (string): The read-only agenda with the live timer; safe to give to attendees.
- `structure_suggestions` (array): Present only when the agenda lacks an opening, a closing or a required break. Apply with add_block and reorder_blocks before replying.
- `title` (string)
- `total_seconds` (integer): Sum of every block's duration_seconds.
- `upgrade_hint` (string): Present only on a free-tier agenda.

### `get_agenda` (~121 tokens)

Read a meeting agenda

Reads back the current state of an agenda, including the id of every block. Needed when
block ids are unknown — typically at the start of a new conversation where the user has
pasted an edit token; after any BriefMe mutation the current state is already in hand.

Takes edit_token only. A share link or share URL does not open an agenda here: one known
only by its share link cannot be read or edited through this connector, only re-created.

Input parameters:

- `edit_token` (string, required): The edit_token returned by create_agenda.

Output parameters:

- `blocks` (array): The blocks in the order they run.
- `expires_at` (string|null): ISO 8601. null when the agenda is saved to an account and does not expire.
- `share_url` (string): The read-only agenda with the live timer; safe to give to attendees.
- `title` (string)
- `total_seconds` (integer): Sum of every block's duration_seconds.

### `update_agenda` (~57 tokens)

Rename a meeting agenda

Renames the agenda. Blocks are untouched — the block tools change those.

Returns the full updated agenda.

Input parameters:

- `edit_token` (string, required): The edit_token returned by create_agenda.
- `title` (string, required): The new meeting title.

Output parameters:

- `blocks` (array): The blocks in the order they run.
- `expires_at` (string|null): ISO 8601. null when the agenda is saved to an account and does not expire.
- `share_url` (string): The read-only agenda with the live timer; safe to give to attendees.
- `title` (string)
- `total_seconds` (integer): Sum of every block's duration_seconds.

### `add_block` (~180 tokens)

Add a block to an agenda

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 existing block. Returns the full updated
agenda, so no get_agenda call is needed afterwards.

Input parameters:

- `after_block_id` (string): Insert directly after this block id. Omit to add at the end.
- `block_type` (string, required): Internal classification for aggregate analysis, inferred from the content; shown on no BriefMe page.
- `description` (string): Optional one-line note, only when the title is ambiguous.
- `duration_seconds` (integer, required): How long this block runs, in seconds.
- `edit_token` (string, required): The edit_token returned by create_agenda.
- `title` (string, required): Short, active, scannable on a countdown screen.

Output parameters:

- `blocks` (array): The blocks in the order they run.
- `expires_at` (string|null): ISO 8601. null when the agenda is saved to an account and does not expire.
- `share_url` (string): The read-only agenda with the live timer; safe to give to attendees.
- `title` (string)
- `total_seconds` (integer): Sum of every block's duration_seconds.

### `update_block` (~208 tokens)

Change one 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 call.

Changes one block only: it does not reorder, add or remove anything, and there is no
whole-agenda replace. get_agenda returns the current block ids. Returns the full updated
agenda.

Input parameters:

- `block_id` (string, required): The id of the block to change, from create_agenda or get_agenda.
- `block_type` (string): New internal classification (aggregate analysis only; shown on no BriefMe page). Omit to leave unchanged.
- `description` (string|null): New note. Send null to clear it. Omit to leave unchanged.
- `duration_seconds` (integer): New duration in seconds. Omit to leave unchanged.
- `edit_token` (string, required): The edit_token returned by create_agenda.
- `title` (string): New title. Omit to leave unchanged.

Output parameters:

- `blocks` (array): The blocks in the order they run.
- `expires_at` (string|null): ISO 8601. null when the agenda is saved to an account and does not expire.
- `share_url` (string): The read-only agenda with the live timer; safe to give to attendees.
- `title` (string)
- `total_seconds` (integer): Sum of every block's duration_seconds.

### `remove_block` (~99 tokens)

Remove a 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. Removing a block
shortens the meeting — it does not redistribute that time to the other blocks.

Returns the full updated agenda.

Input parameters:

- `block_id` (string, required): The id of the block to remove.
- `edit_token` (string, required): The edit_token returned by create_agenda.

Output parameters:

- `blocks` (array): The blocks in the order they run.
- `expires_at` (string|null): ISO 8601. null when the agenda is saved to an account and does not expire.
- `share_url` (string): The read-only agenda with the live timer; safe to give to attendees.
- `title` (string)
- `total_seconds` (integer): Sum of every block's duration_seconds.

### `reorder_blocks` (~109 tokens)

Reorder the blocks of an agenda

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 reorders: it cannot add, remove or edit a block. get_agenda
returns the current ids.

Returns the full updated agenda.

Input parameters:

- `block_ids` (array, required): Every current block id, exactly once, in the order you want them to run.
- `edit_token` (string, required): The edit_token returned by create_agenda.

Output parameters:

- `blocks` (array): The blocks in the order they run.
- `expires_at` (string|null): ISO 8601. null when the agenda is saved to an account and does not expire.
- `share_url` (string): The read-only agenda with the live timer; safe to give to attendees.
- `title` (string)
- `total_seconds` (integer): Sum of every block's duration_seconds.

### `rotate_edit_token` (~113 tokens)

Regenerate the edit link

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, browser and bookmark
that held them — the remedy when an edit link was shared by mistake.

Returns the full agenda with the new edit_url and edit_token. The previous ones cannot be
restored. Agendas expire after 7 days and cannot be recovered afterwards.

Input parameters:

- `edit_token` (string, required): The current edit_token — the one being replaced.

Output parameters:

- `blocks` (array): The blocks in the order they run.
- `edit_token` (string): What every later tool call takes from now on; the previous token is dead.
- `edit_url` (string): The user's new private control page; the previous link is dead.
- `expires_at` (string|null): ISO 8601. null when the agenda is saved to an account and does not expire.
- `instructions` (string): Read this first: how to reply to the user.
- `share_url` (string): The read-only agenda with the live timer; safe to give to attendees.
- `title` (string)
- `total_seconds` (integer): Sum of every block's duration_seconds.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/us-briefme-agenda-timer/briefme#diagnostics

## Score history

- 2026-09-24: 78
- 2026-09-23: 77
- 2026-09-22: 77
- 2026-09-21: 77
- 2026-09-20: 76
- 2026-09-19: 76
- 2026-09-18: 75
- 2026-09-17: 75
- 2026-09-16: 74
- 2026-09-15: 74
- 2026-09-14: 73
- 2026-09-13: 73
- 2026-09-12: 72
- 2026-09-11: 72
- 2026-09-10: 68
- 2026-09-09: 67
- 2026-09-08: 67
- 2026-09-07: 66
- 2026-09-06: 66
- 2026-09-05: 65
- 2026-09-04: 65
- 2026-09-03: 64
- 2026-09-02: 64
- 2026-09-01: 63
- 2026-08-31: 63
- 2026-08-30: 63
- 2026-08-29: 62

## Common questions

### What is the BriefMe MCP server?

BriefMe is an MCP server listed in the public MCP registry as us.briefme/agenda-timer. Meeting agenda timer for AI assistants: build agendas in chat, share a live synced countdown. This page covers its hosted endpoint (https://briefme.us/mcp).

### Is the BriefMe MCP server safe to use?

BriefMe scores 78 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the BriefMe MCP server expose?

BriefMe exposes 8 tools: create_agenda, get_agenda, update_agenda, add_block, update_block, and 3 more. Their descriptions and schemas cost roughly 1,254 tokens of context every time the server is loaded.

### Does the BriefMe MCP server require authentication?

No. We connected to BriefMe without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the BriefMe MCP server still maintained?

BriefMe is still listed as active in the MCP registry. We last reached this channel on 24 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://briefme.us/mcp
- Website: https://briefme.us/
- Changelog RSS feed: https://verifymcp.io/servers/us-briefme-agenda-timer/briefme.xml
- Changelog JSON feed: https://verifymcp.io/servers/us-briefme-agenda-timer/briefme.json
- HTML version of this page: https://verifymcp.io/servers/us-briefme-agenda-timer/briefme