Chorus
REMOTE · CHORUSKEEPSAKE.COM
Gathers voice, video and written messages from a group into one book for one person.
Available components
Last scanned (12 hours ago)
Scores higher than 84% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Communication
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. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability63
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 3435 tokens (~180/item across 19 items; 19 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 20 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 21 Nov 26 0
- Tool “find_my_book” rewrote its description, which is the text the model reads security
- “find_my_book” added an optional parameter “waiting” cosmetic
- “start_book” added an optional parameter “waiting” cosmetic
- “find_my_book” dropped the optional parameter “code” cosmetic
- “start_book” dropped the optional parameter “code” cosmetic
- 19 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- 16 Nov 26 0
- Stability: 0.97 → pass security
- 15 Nov 26 0
- Stability: pass → 0.97 functional
- 11 Nov 26 0
- Stability: 0.97 → pass security
- 10 Nov 26 0
- Schema quality: 3034 → 3341 ▼ functional
- Stability: pass → 0.97 functional
- New tool “arrange_the_book” functional
- 9 Nov 26 0
- Stability: 0.97 → pass security
- 8 Nov 26 0
- Stability: pass → 0.97 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Probed https://choruskeepsake.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=choruskeepsake.com | CN=WE1,O=Google Trust Services,C=US | 12 Nov 2026 | 11 Feb 2027 | ECDSA 256 | ECDSA-SHA256 | 17a4612fad84160b0e07b22ab9785758 |
| SANs: choruskeepsake.com, new.choruskeepsake.com, *.new.choruskeepsake.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of choruskeepsake.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| choruskeepsake.com. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains; preload |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://choruskeepsake.com/mcp | Verified | 200 | |
| http (plaintext) | http://choruskeepsake.com/mcp | HTTPS enforced | 301 | https://choruskeepsake.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
add_people Name the people the book is waiting on, with an address where there is one. ~103
Records who is expected to record. A person with an email address can be emailed the invitation and the reminders; a person with only a name is reached in a group chat, and the reminder message names them. Adding a person sends nothing.
| Name | Type | Req | Description |
|---|---|---|---|
| book | string | yes | The book’s handle. |
| people | array | yes | The people, each as a name, or as a name and an email address. A name on its own is somebody reached in a group chat. |
No output schema declared.
No examples provided.
arrange_the_book Put the people in order, and set the title and the cover. ~307
Sets the order the people print in, takes a person’s pages out or puts them back, and changes the book’s title and its cover: a photo or one of six colours on the front, the line under the title, and what the back carries. It moves pages and changes no word on them, and a person’s own pages stay together. Returns the people in their new order, the cover as it stands, anything refused with its reason, and a picture of the opening page. A book that has gone to the printer stays as it is.
| Name | Type | Req | Description |
|---|---|---|---|
| book | string | yes | The book’s handle. |
| cover | object | – | Any of: front, photo or colour; colour, one of forest, navy, black, grey, red and tan; title_colour, light or dark; from, the line under the title; back, one of line, names, photo, words and plain; b… |
| leave_out | array | – | Names whose pages come out of the book. The pages stay in the editor. |
| order | array | – | Names as they print on the pages, in the order they should come. Anybody not named follows in the order they had. |
| put_back | array | – | Names whose pages go back into the book. |
| title | string | – | The book’s title, one line of up to 40 characters. |
No output schema declared.
No examples provided.
book_status Who has recorded, who is still out, and how long is left. ~81
Returns who is in with their name and relationship, how many voices, videos and written messages have come in, how many carried a photo, who the organiser is still waiting on, the days left before collecting stops, and next: the day to chase the ones still out and the day to close the book.
| Name | Type | Req | Description |
|---|---|---|---|
| book | string | yes | The book’s handle. |
No output schema declared.
No examples provided.
change_the_book Change the closing date, the questions and steps, or what people may send. ~234
Changes the settings the organiser can change on the site: the day collecting stops, the questions people answer, whether they may send voice, video or writing, which one the button offers first, and whether the people recording are offered to chip in towards the printed book. Nobody is told about a change.
| Name | Type | Req | Description |
|---|---|---|---|
| answer_with | array | – | Any of voice, video and written. |
| book | string | yes | The book’s handle. |
| chip_in | boolean | – | true offers everyone who records the chance to put money towards the printed book, which comes off what the organiser pays; false stops offering it. |
| closes_on | string | – | The day collecting stops, as a date. It means stop collecting rather than finished. |
| lead_with | string | – | Which one the big button offers first. |
| questions | array | – | The questions people answer, up to twelve. |
| steps | array | – | The whole list of steps, in order, in the shape a new book takes them. It replaces the steps the book had. An empty list goes back to plain questions. A person who already answered keeps their page. |
No output schema declared.
No examples provided.
chase_the_missing Remind the people who have not recorded yet. ~105
Works out who is still out, emails a reminder to the ones with an address, and hands back a message naming them, ready for the group chat and ready for one person. A person gets at most one reminder a day and three in all, and never one after they have said stop.
| Name | Type | Req | Description |
|---|---|---|---|
| also_email | boolean | – | false returns the message and the taps and sends nothing. Without it, the reminder is emailed. |
| book | string | yes | The book’s handle. |
No output schema declared.
No examples provided.
close_collecting Stop collecting, and get the link that plays every message. ~47
Stops new messages arriving and returns the final counts with the gift link. Nothing is deleted and nothing is finished; it can be reopened.
| Name | Type | Req | Description |
|---|---|---|---|
| book | string | yes | The book’s handle. |
No output schema declared.
No examples provided.
find_my_book Get back into a book when the handle is gone. ~148
Given the email address a book belongs to, Chorus emails that address a sign-in link and returns waiting, and nothing about the books. Given the address and waiting, once the person has tapped the link, it returns every book on that account with its handle. Nobody types anything into the chat. An address new to Chorus is let in at once, with no books yet. Holding the mailbox is the proof, so a book cannot be found by guessing an address.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | The email address the book belongs to. | |
| waiting | string | – | The waiting the first answer gave back, once the person has tapped the sign-in link. Without it, Chorus emails a link. |
No output schema declared.
No examples provided.
get_links The collecting link, the gift link, and a message to send with them. ~46
Returns the link to forward to contributors, the link that plays every message straight through, and a short message the organiser can paste alongside.
| Name | Type | Req | Description |
|---|---|---|---|
| book | string | yes | The book’s handle. |
No output schema declared.
No examples provided.
get_style Read how each page of the book looks, part by part. ~90
Reads the book’s style file: every part of a person’s page, with its size, place, typeface, colour and alignment, what each part means, the limits the print rules keep, and the people who have pages.
| Name | Type | Req | Description |
|---|---|---|---|
| book | string | yes | The book’s handle. |
| person | string | – | A name as it prints on their pages, for that person’s pages as they print. |
No output schema declared.
No examples provided.
order Hand the organiser a payment page for the option they chose. ~105
Returns a payment link for one of the three ways to keep the book: voices, book, or keepsake, which is the printed hardcover. The price is on Stripe’s page, which takes the card and, on the keepsake, the postal address. This tool never takes a card and never names a price.
| Name | Type | Req | Description |
|---|---|---|---|
| book | string | yes | The book’s handle. |
| option | string | yes | voices, book, or keepsake. Only the keepsake is printed and posted. |
No output schema declared.
No examples provided.
order_status Whether it is paid, and where the printer is with it. ~48
Returns whether the book has been paid for and which option was bought, and on a printed one the stage the printer is at with the tracking.
| Name | Type | Req | Description |
|---|---|---|---|
| book | string | yes | The book’s handle. |
No output schema declared.
No examples provided.
preview_pages Pictures of the real pages, as the book prints. ~104
Returns pictures of the spreads the book prints, laid out by the same code that makes the printer’s file: a page by its number, a person’s first page, or the first message when neither is given.
| Name | Type | Req | Description |
|---|---|---|---|
| book | string | yes | The book’s handle. |
| pages | array | – | Page numbers, up to four. Each picture is the spread the page is on. |
| person | string | – | A name as it prints, for that person’s first page. |
No output schema declared.
No examples provided.
read_the_messages What people said, written out. ~73
Returns every message with who left it and what they said. A written message reads back whatever was paid; a voice or a video is written out on the tier that includes the words, and where it is not, the tool says so rather than half-answering.
| Name | Type | Req | Description |
|---|---|---|---|
| book | string | yes | The book’s handle. |
No output schema declared.
No examples provided.
reopen_collecting Let messages in again, with a new closing date if there is one. ~66
Reopens a book that was closed or whose date ran out, and returns the collecting link to send round again.
| Name | Type | Req | Description |
|---|---|---|---|
| book | string | yes | The book’s handle. |
| closes_on | string | – | A new day to stop collecting, as 2026-11-14. |
No output schema declared.
No examples provided.
send_feedback Tell the people who make Chorus what went wrong or was missing. ~170
Sends a short note to the people who make Chorus about a tool that failed or returned something unexpected, a request no tool covers, or a description that was unclear. Email addresses and phone numbers are taken out before the note is kept. It changes nothing on any book and emails nobody.
| Name | Type | Req | Description |
|---|---|---|---|
| book | string | – | The book’s handle, when the note is about one book. |
| kind | string | – | broken, missing, confusing or idea. |
| tool | string | – | The Chorus tool the note is about, when there is one. |
| trying_to | string | – | What the person wanted done, in a few words, for example order a second printed copy. |
| what_happened | string | yes | What went wrong, what was missing or what was unclear, in a sentence or two. |
No output schema declared.
No examples provided.
send_it_out Send the link to everyone, and get the tap that puts it in a group chat. ~106
Emails the invitation once to every person added with an address, and returns a tap that opens WhatsApp, a text or a mail draft with the message and the link already written, for the family group and for anyone with no address. Nobody gets the invitation twice, and each caller has a daily limit on emails.
| Name | Type | Req | Description |
|---|---|---|---|
| also_email | boolean | – | false returns the taps and sends nothing. Without it, the invitation is emailed. |
| book | string | yes | The book’s handle. |
No output schema declared.
No examples provided.
set_style Change how the pages look, through the print rules, and see them. ~258
Changes any line of the book’s style file, for every page or for one person, and returns what was set, what a print rule changed with its reason, what was refused with its reason, and pictures of the pages as they now print. A path is a part and a property, such as codes.size_mm, codes.align, words.size_pt, heading.italic, photo.grayscale, ink or margins_mm.top. A smaller code on the right, for the voice note only, is [{path:"codes.size_mm",value:15},{path:"codes.align",value:"right"},{path:"codes.which",value:"voice"}]. Green ink on Niamh’s pages only is [{path:"ink",value:"#1F4D2B",person:"Niamh"}]. reset: true takes every change off and goes back to the standard page.
| Name | Type | Req | Description |
|---|---|---|---|
| book | string | yes | The book’s handle. |
| changes | array | – | Each change: path (a part and a property, as the style file lists them), value, and person when it is for one person’s pages only. |
| reset | boolean | – | true takes every change off, back to the standard page, before the listed changes apply. |
No output schema declared.
No examples provided.
start_book Start a Chorus book, and get the one link to forward. ~814
Starts a book of voice, video and written messages and returns its handle and the single link the organiser sends to everyone taking part. The book is for one person or a couple, or it goes by a title when it is for nobody in particular: a family’s recipes, a class’s year, a team’s goodbye. Gathering is free, and the people recording need no app and no account. It needs organiser_email, the address Chorus lets the organiser know about responses at, unless they are signed in through the connector. The book is made at once and the link comes back. Chorus emails the link to that address and emails it each time somebody responds, and the book moves into their account when they sign in with it or open keep_link.
| Name | Type | Req | Description |
|---|---|---|---|
| answer_with | array | – | Any of voice, video and written. Voice and written when not said. |
| closes_on | string | – | Optional. The day collecting stops, as 2026-11-14. Without it the book stays open until it is closed, and a date can be set at any time after. A printed copy wanted for a day needs collecting to stop… |
| expecting | array | – | Who is expected to record, by name or role, without email addresses. The book’s status names the ones still out. |
| lead_with | string | – | Which of those is the big button on a contributor’s phone. |
| occasion | string | – | A big birthday, A wedding, A new baby, As they grow, In memory, or Something else. Plain words are matched to one of those. |
| organiser_email | string | – | Where Chorus lets the organiser know about responses. Needed unless they are signed in through the connector. The link is emailed there too. |
| questions | array | – | The questions everybody answers, up to 12, each one line of up to 200 characters that a person can answer out loud in a minute or two. In a book with subject_name, {name} in a question becomes that n… |
| steps | array | – | What each person is given, in order, one screen each, when the book needs more than questions. Each step is { kind, text }: words (a question answered by voice, video or writing, text required), song… |
| subject_name | string | – | Who the book is for, when it is for one person or a couple, as the organiser says it, for example Mum. A book needs subject_name, title or both, and a book for one person needs only subject_name. |
| title | string | – | The book’s title, in the person’s words, for example The Kelly family recipes. One line, up to 40 characters. |
| waiting | string | – | Optional. The waiting a Chorus sign-in link went out with, once the organiser has tapped that link, which puts the book straight into their account. Without it the book is made at once. |
No output schema declared.
No examples provided.
their_own_link The separate link for the person the book is about. ~80
Returns the second link, which puts questions to the person the book is for about their own life. It refuses on a memorial, a new baby and an as they grow book, where the person cannot answer. The link is for that one person, and a group chat gets the collecting link.
| Name | Type | Req | Description |
|---|---|---|---|
| book | string | yes | The book’s handle. |
No output schema declared.
No examples provided.
How do I install the Chorus MCP server?
Chorus is a hosted endpoint at https://choruskeepsake.com/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.
remote · choruskeepsake.com
claude mcp add --transport http com-choruskeepsake-chorus 'https://choruskeepsake.com/mcp'
What is the Chorus MCP server?
Chorus is an MCP server listed in the public MCP registry as com.choruskeepsake/chorus. Gathers voice, video and written messages from a group into one book for one person. This page covers its hosted endpoint (https://choruskeepsake.com/mcp).
Is the Chorus MCP server safe to use?
Chorus scores 84 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 Chorus MCP server expose?
Chorus exposes 19 tools: start_book, get_links, add_people, send_it_out, chase_the_missing, and 14 more. Their descriptions and schemas cost roughly 2,985 tokens of context every time the server is loaded.
Does the Chorus MCP server require authentication?
No. We connected to Chorus without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Chorus MCP server still maintained?
Chorus is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Chorus MCP server?
VerifyMCP ran 13 checks on Chorus, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.