BriefMe MCP server
us.briefme/agenda-timerbriefme.usstreamable-httpv1.1.1Scanned
Meeting agenda timer for AI assistants: build agendas in chat, share a live synced countdown.
12 tools: 7 can delete or cancel things, 1 do something that can't be undone, 1 change things and 3 only read.
- Reads private data · 0
- Reads text others write · 10
- Can send data out · 0
- 1 finding
Tools listed without sign-in. Remote posture
With Anlyon
7 tools here can delete or cancel things and 1 does something that can't be undone. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the BriefMe MCP server can do
The BriefMe MCP server is published by briefme.us, a domain the MCP Registry verified. It has 12 tools. It can delete or cancel things (7 tools: update_agenda, update_block, remove_block, reorder_blocks and 3 more), do things that cannot be undone, such as sending, paying or publishing (create_agenda) and create or change data (1 tool: add_block). 3 tools only read.
10 tools bring in text other people can write (create_agenda, get_shared_agenda, update_agenda and 7 more).
The fixed checks matched 1 finding (tool-shadowing). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.
Last scanned Nov 10, 2026, version 1.1.1.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
12 tools
Deletes or cancels 7Claude Code: deny
delete_agendaDeletes an agenda and its timer history permanently.Reads text others writeNo findings
Why it is in this group
- The name "delete_agenda" says "delete": a word for removing or ending something.
- The server marks it destructive (destructiveHint: true).
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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 agenda the user has explicitly confirmed; the delete-agenda skill asks first. release_agenda instead takes a saved agenda out of a linked account and keeps its share link alive for a while. Returns {deleted: true, share_token}.
Annotations the server declares
- title: Delete an agenda
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: true
- openWorldHint: true
release_agendaTakes one agenda out of the BriefMe account to free a slot.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it destructive (destructiveHint: true).
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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 any anonymous agenda. The release is final — a released agenda cannot be returned to the account and list_agendas no longer shows it — so it fits an agenda the user has explicitly chosen to drop.
Annotations the server declares
- title: Remove an agenda from the account
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: true
- openWorldHint: true
remove_blockRemoves one block from an agenda.Reads text others writeNo findings
Why it is in this group
- The name "remove_block" says "remove": a word for removing or ending something.
- The server marks it destructive (destructiveHint: true).
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- title: Remove a block
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: true
- openWorldHint: true
reorder_blocksPuts the agenda's blocks into the order given.Reads text others writeNo findings
Why it is in this group
- The description's first verb is "put": a word for a change.
- The server marks it destructive (destructiveHint: true).
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- title: Reorder the blocks of an agenda
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: true
- openWorldHint: true
rotate_edit_tokenReplaces an agenda's edit token and edit link with new ones.Reads text others writeNo findings
Why it is in this group
- The name "rotate_edit_token" says "edit": a word for a change.
- The description says "cannot be restored".
- The server marks it destructive (destructiveHint: true).
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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, unless the agenda is saved to a linked BriefMe account, the new edit_token. The previous ones cannot be restored. Agendas expire after 7 days and cannot be recovered afterwards.
Annotations the server declares
- title: Regenerate the edit link
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: false
- openWorldHint: true
update_agendaRenames the agenda.Reads text others writeNo findings
Why it is in this group
- The name "update_agenda" says "update": a word for a change.
- The server marks it destructive (destructiveHint: true).
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Renames the agenda. Blocks are untouched — the block tools change those. Returns the full updated agenda.
Annotations the server declares
- title: Rename a meeting agenda
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: true
- openWorldHint: true
update_blockChanges one block, identified by block_id.Reads text others writeNo findings
Why it is in this group
- The name "update_block" says "update": a word for a change.
- The server marks it destructive (destructiveHint: true).
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- title: Change one block
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: true
- openWorldHint: true
Can't be undone 1Claude Code: ask
create_agendaCreates a timed meeting agenda — a shareable countdown timer that walks attendees through timeboxed topics in sync.Reads text others writeNo findings
Why it is in this group
- The name "create_agenda" says "create": a word for a change.
- The description says "cannot be recovered".
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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 share_token (what later calls take), share_url (the read-only live timer for attendees, safe to post anywhere) and edit_url (the private control page: start, pause, advance and finish the meeting, and edit blocks by hand). Without a linked BriefMe account it also returns edit_token, which later calls take instead of an account. 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. Include the opening, the wrap-up and any planned break in this first call: every change afterwards is a separate confirmation for the user. Agendas expire after 7 days and cannot be recovered afterwards.
Annotations the server declares
- title: Create a meeting agenda
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
Changes things 1Claude Code: ask
add_blockAdds one block to an existing agenda: at the end, above a final wrap-up, or directly after after_block_id.Reads text others writeNo findings
Why it is in this group
- The name "add_block" says "add": a word for a change.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- title: Add a block to an agenda
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
Only reads 3Show 3 read-only tools
get_agendaReads back the current state of an agenda, including the id of every block.No findings
Why it is in this group
- The name "get_agenda" says "get": a word for reading.
Description, as the server wrote it 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; after any BriefMe mutation the current state is already in hand. Identifies the agenda by share_token for an agenda saved to a linked BriefMe account, or by the edit_token create_agenda returned, which authorizes on its own. A share link alone does not open an agenda for editing: get_shared_agenda reads the public agenda behind one, without edit access.
Annotations the server declares
- title: Read a meeting agenda
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
list_agendasLists every agenda saved in the signed-in BriefMe account, newest first, with the share_token every other tool takes.1 finding
Why it is in this group
- The name "list_agendas" says "list": a word for reading.
Findings
- Warn
The description contains "every other tool", wording about other tools or servers.
What this check looks forMatched text
description: "...unt, newest first, with the share_token every other tool takes. Useful at the start of a conver..."
Description, as the server wrote it 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 the user refers to an agenda made earlier ("run last week's sprint planning again"), and after create_agenda reports the account is full. Returns limit, retained and slots_left alongside the agendas. It returns share links only — the private control link comes from create_agenda.
Annotations the server declares
- title: List the account's agendas
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write10
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:20 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 9
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- https://briefme.us/.well-known/oauth-protected-resource/mcp
- Authorization servers
- https://briefme.us
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- yes
- Client ID metadata documents
- no
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 9 tools that change things (7 destructive, 1 irreversible, 1 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://briefme.us/mcp: tools/list returned 12 tools to an anonymous client, including update_agenda (destructive), update_block (destructive), remove_block (destructive), reorder_blocks (destructive), rotate_edit_token (destructive) and 4 more
Findings
Matches of fixed checks, with the text they matched.
- Warnlist_agendas
The description contains "every other tool", wording about other tools or servers.
What this check looks forMatched text
description: "...unt, newest first, with the share_token every other tool takes. Useful at the start of a conver..."
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools10 changed.~10 changedView diff
- Changed:add_blockChanges thingsannotations
- Changed:create_agendaCan't be undoneannotations
- Changed:delete_agendaDeletes or cancelsannotations
- Changed:get_shared_agendaOnly readsannotations
- Changed:release_agendaDeletes or cancelsannotations
- Changed:remove_blockDeletes or cancelsannotations
- Changed:reorder_blocksDeletes or cancelsannotations
- Changed:rotate_edit_tokenDeletes or cancelsannotations
- Changed:update_agendaDeletes or cancelsannotations
- Changed:update_blockDeletes or cancelsannotations
Install
Pinned to version 1.1.1. Values in angle brackets are yours to fill in.
claude mcp add --transport http agenda-timer https://briefme.us/mcpclaude mcp add --transport http agenda-timer https://briefme.us/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__agenda-timer__list_agendas",
"mcp__agenda-timer__get_agenda",
"mcp__agenda-timer__get_shared_agenda"
],
"ask": [
"mcp__agenda-timer__create_agenda",
"mcp__agenda-timer__add_block"
],
"deny": [
"mcp__agenda-timer__update_agenda",
"mcp__agenda-timer__update_block",
"mcp__agenda-timer__remove_block",
"mcp__agenda-timer__reorder_blocks",
"mcp__agenda-timer__rotate_edit_token",
"mcp__agenda-timer__release_agenda",
"mcp__agenda-timer__delete_agenda"
]
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as agenda-timer. Review it before you use it.
Capability tags behind 10 rules
- mcp__agenda-timer__create_agenda untrusted-input
- mcp__agenda-timer__get_shared_agenda untrusted-input
- mcp__agenda-timer__update_agenda untrusted-input
- mcp__agenda-timer__add_block untrusted-input
- mcp__agenda-timer__update_block untrusted-input
- mcp__agenda-timer__remove_block untrusted-input
- mcp__agenda-timer__reorder_blocks untrusted-input
- mcp__agenda-timer__rotate_edit_token untrusted-input
- mcp__agenda-timer__release_agenda untrusted-input
- mcp__agenda-timer__delete_agenda untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/us.briefme/agenda-timer/verify?hash=4eb3486c2e5b710c5d787f39de473a7163365708f777aaed91887a6052617644" | jq -e '.changed == false'Pinned hash 4eb3486c2e5b, from Nov 10, 2026, 05:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/us.briefme/agenda-timer/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/us.briefme/agenda-timer)Source: MCP Registry. Synced Nov 10, 2026, 05:18 UTC.
BriefMe MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the BriefMe MCP server safe?
- No scan can promise that. What its definitions show: 12 tools, 9 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the BriefMe MCP server delete data?
- Yes. 7 tools can delete, cancel or revoke something: update_agenda, update_block, remove_block, reorder_blocks, rotate_edit_token, release_agenda and 1 more.
Can the BriefMe MCP server do things that cannot be undone?
- Yes. 1 tool can send, pay, publish or merge: create_agenda.
What tools does the BriefMe MCP server have?
- 12 tools: 7 destructive, 1 irreversible, 1 write, 3 read. update_agenda, update_block, remove_block, reorder_blocks, rotate_edit_token, release_agenda, delete_agenda, create_agenda and 4 more.
Does the BriefMe MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the BriefMe MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the BriefMe MCP server changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Nov 10, 2026. Every change is on this page and in its Atom feed.