Chorus
REMOTE · CHORUSKEEPSAKE.COM · SCANNED SEP 20
Gathers voice, video and written messages from a group into one book for one person.
Available components
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. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. 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 Usability79
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1569 tokens (~112/item across 14 items; 14 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 Management40
- Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 15 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
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'
{
"mcpServers": {
"com-choruskeepsake-chorus": {
"url": "https://choruskeepsake.com/mcp"
}
}
} {
"servers": {
"com-choruskeepsake-chorus": {
"type": "http",
"url": "https://choruskeepsake.com/mcp"
}
}
} [mcp_servers.com-choruskeepsake-chorus] url = "https://choruskeepsake.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-choruskeepsake-chorus": {
"type": "remote",
"url": "https://choruskeepsake.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-choruskeepsake-chorus --url 'https://choruskeepsake.com/mcp' --transport streamable-http
mcp_servers:
com-choruskeepsake-chorus:
url: "https://choruskeepsake.com/mcp" {
"McpServers": {
"com-choruskeepsake-chorus": {
"Transport": "http",
"Url": "https://choruskeepsake.com/mcp"
}
}
} assistant mcp add com-choruskeepsake-chorus -t streamable-http -u 'https://choruskeepsake.com/mcp'
{
"mcpServers": {
"com-choruskeepsake-chorus": {
"type": "http",
"url": "https://choruskeepsake.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 0
- Schema quality: 830 → 1569 ▼ functional
- Destructive annotations: pass → 100 functional
- New tool “add_people” functional
- New tool “change_the_book” functional
- New tool “chase_the_missing” functional
- New tool “find_my_book” functional
- New tool “read_the_messages” functional
- New tool “send_it_out” functional
- New tool “their_own_link” functional
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Sept 26 0
- Stability: unverified → 0.03 ▲ functional
- 8 Sept 26 +38
- Authorization: unverified → partial ▲ security
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- MCP protocol: unverified → fail ▼ functional
- Tool coverage: unverified → 100 ▲ functional
- First check of Schema quality: fail functional
- First check of Schema quality: excellent functional
- First check of Destructive annotations: pass functional
- First check of Schema quality: fail functional
- First check of Tool coverage: 100 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 20 Sept 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=YE2,O=Let's Encrypt,C=US | 4 Aug 2026 | 2 Nov 2026 | ECDSA 256 | ECDSA-SHA384 | 56d01288e4956758d5b3f01b0fc0b65cfa4 |
| SANs: *.choruskeepsake.com, *.choruskeepsakes.com, *.spremtlabs.com, choruskeepsake.com, choruskeepsakes.com, spremtlabs.com | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
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. | present | 19718 | 13 | Verified |
| choruskeepsake.com. | absent | 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. ~114
Records who is expected to record. Somebody with an email address can be written to by send_it_out and reminded by chase_the_missing; somebody with only a name is reached in a group chat and their name is what the chase reads out. Adding a person sends nothing on its own.
| Name | Type | Req | Description |
|---|---|---|---|
| book | string | yes | The handle start_book gave you. |
| 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.
book_status Who has recorded, who is still out, and how long is left. ~64
Returns who is in with their name and relationship, how many voices, videos and written messages have landed, how many carried a photo, who the organiser is still waiting on, and the days left before collecting stops.
| Name | Type | Req | Description |
|---|---|---|---|
| book | string | yes | The handle start_book gave you. |
No output schema declared.
No examples provided.
change_the_book Change the closing date, the questions, or what people may send. ~139
Changes the settings the organiser can change on the site: the day collecting stops, the questions people are asked, whether they may send voice, video or writing, and which one the button offers first. Nobody is told about a change.
| Name | Type | Req | Description |
|---|---|---|---|
| answer_with | array | – | Any of voice, video and written. |
| book | string | yes | The handle start_book gave you. |
| 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 are asked, up to twelve. |
No output schema declared.
No examples provided.
chase_the_missing Remind the people who have not recorded yet. ~109
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 asked to stop.
| Name | Type | Req | Description |
|---|---|---|---|
| also_email | boolean | – | Leave it out to send the reminder. Set it false to get the message and the taps only. |
| book | string | yes | The handle start_book gave you. |
No output schema declared.
No examples provided.
close_collecting Stop collecting, and get the link that plays every message. ~49
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 handle start_book gave you. |
No output schema declared.
No examples provided.
find_my_book Get back into a book when the handle is gone. ~115
Call it with the email address the book belongs to and Chorus sends that address a six digit code, returning nothing about the books. Call it again with the address and the code and it hands back every book on that account with its handle. Holding the mailbox is the proof, so a book cannot be found by guessing an address.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | – | The six digit code that was emailed. Leave it out on the first call to have one sent. |
| string | yes | The email address the book belongs to. |
No output schema declared.
No examples provided.
get_links The collecting link, the gift link, and a message to send with them. ~48
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 handle start_book gave you. |
No output schema declared.
No examples provided.
order Hand the organiser a payment page for the option they chose. ~127
Returns a payment link for one of the three ways to keep the book: voices, book, or keepsake, which is the printed hardcover. Stripe shows the price and takes the card and, on the keepsake, the postal address. This tool never takes a card and never names a price. Read the prices from https://choruskeepsake.com/llms.txt when the person asks what it costs.
| Name | Type | Req | Description |
|---|---|---|---|
| book | string | yes | The handle start_book gave you. |
| 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. ~50
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 handle start_book gave you. |
No output schema declared.
No examples provided.
read_the_messages What people said, written out. ~75
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 handle start_book gave you. |
No output schema declared.
No examples provided.
reopen_collecting Let messages in again, with a new closing date if there is one. ~68
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 handle start_book gave you. |
| closes_on | string | – | A new day to stop collecting, as 2026-11-14. |
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 hands back 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 is written to twice by this tool.
| Name | Type | Req | Description |
|---|---|---|---|
| also_email | boolean | – | Leave it out to send the invitation. Set it false to get the taps only and send nothing. |
| book | string | yes | The handle start_book gave you. |
No output schema declared.
No examples provided.
start_book Start a Chorus book for a person, and get the one link to forward. ~299
Starts a book of voice, video and written messages for one person, and returns the single link the organiser sends to everyone taking part. Gathering is free and the people recording need no app and no account. Use this as soon as somebody wants to collect messages from a group for one person, whether or not there is an occasion.
| Name | Type | Req | Description |
|---|---|---|---|
| answer_with | array | – | Any of voice, video and written. Voice and written when not said. |
| closes_on | string | – | The day collecting stops, as 2026-11-14. Allow three weeks before the day if a printed copy is wanted. |
| expecting | array | – | Who is expected to record, by name or role, so book_status can say who is still out. Never email addresses. |
| 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 | yes | The organiser’s email. The book belongs to this address and they get in with a six digit code. |
| questions | array | – | Questions to ask, if the organiser wants their own. The set for the occasion is used when this is left out. |
| subject_name | string | yes | Who the book is for, as the organiser says it, for example Mum. |
No output schema declared.
No examples provided.
their_own_link The separate link for the person the book is about. ~81
Returns the second link, which asks the person the book is for about their own life rather than about somebody else. It refuses on a memorial, a new baby and an as they grow book, where the person cannot answer, and it is never the link to put in a group chat.
| Name | Type | Req | Description |
|---|---|---|---|
| book | string | yes | The handle start_book gave you. |
No output schema declared.
No examples provided.
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 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 Chorus MCP server expose?
Chorus exposes 14 tools: start_book, get_links, add_people, send_it_out, chase_the_missing, and 9 more. Their descriptions and schemas cost roughly 1,444 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 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.