ScreenParty
REMOTE · SCREENPARTY.HUITONGDESK.COM
Create watch-together rooms, scheduled watch parties and branded class links. No sign-up.
Available components
Last scanned (22 hours ago)
Scores higher than 60% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Entertainment and Games
Recent critical change
Authorization (1 Nov 2026). See the changelog before you install this server.
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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (update_watch_party). See how to fix → View diagnostics → Fail
- 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 Usability69
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1741 tokens (~217/item across 8 items; 8 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 Management70
- Stability observed for 21 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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.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 9 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 +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.
- 19 Nov 26 +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.
- 17 Nov 26 +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.
- 14 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 8 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 6 Nov 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → 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://screenparty.huitongdesk.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=huitongdesk.com | CN=WE1,O=Google Trust Services,C=US | 19 Oct 2026 | 17 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | b80089909760b845132d4935293dc064 |
| SANs: huitongdesk.com, *.huitongdesk.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 screenparty.huitongdesk.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| huitongdesk.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=15552000 |
| content-security-policy | frame-ancestors 'self'; object-src 'none'; base-uri 'self' |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://screenparty.huitongdesk.com/mcp | Verified | 200 | |
| http (plaintext) | http://screenparty.huitongdesk.com/mcp | HTTPS enforced | 301 | https://screenparty.huitongdesk.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 →
cancel_watch_party Cancel a scheduled watch party ~133
Cancels a watch party (a room made with create_watch_room, same room_code): its countdown page and link stop working. Needs the organiser_key (or organiser_link) that create_watch_room returned, so only the organiser can cancel. A room that is already open carries on until everyone leaves. Cannot be undone; confirm with the user first.
| Name | Type | Req | Description |
|---|---|---|---|
| organiser_key | string | – | The organiser_key from create_watch_room. |
| organiser_link | string | – | Alternatively, the organiser_link from create_watch_room. |
| room_code | string | – | The 5-character room code. Not needed when organiser_link is given. |
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | – | Error code when ok is false. |
| ok | boolean | yes | false when the call failed; then code says why. |
| room_code | string | – | The cancelled room code. |
No examples provided.
create_branded_link Create a branded watch-together link ~279
Creates a permanent public page (…/r/<slug>) with a name, an optional one-line description, colour and video. Everyone who opens it lands in that page's room, any time, so it suits teachers, classes, clubs and communities who reuse one link every week (for a one-off, use create_watch_room). Returns public_link to share and a private edit_link: the user opens it to add a logo and background and download a poster with a QR code, and it is needed for update_branded_link and delete_branded_link. Give edit_link only to the user, never to guests.
| Name | Type | Req | Description |
|---|---|---|---|
| color | string | – | Optional theme colour as #rrggbb. |
| name | string | yes | Name shown on the page, e.g. "Ms. Lee's English Class". |
| slug | string | – | Optional. The link ending: 3-30 lowercase Latin letters, digits and hyphens (e.g. lee-english). Made from the name if omitted. |
| tagline | string | – | Optional one line, e.g. "Every Tuesday at 8 pm". |
| video_url | string | – | Optional video to load in the room. A direct video link (mp4, webm, m3u8) or a public YouTube video URL. Paid streaming services are not supported. |
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | – | Error code when ok is false. |
| edit_link | string | – | Private edit link. |
| ok | boolean | yes | false when the call failed; then code says why. |
| public_link | string | – | Link to share. |
| slug | string | – | The link ending. |
No examples provided.
create_watch_room Create a watch-together room ~323
Creates a private ScreenParty room where friends watch the same video in sync, in their browsers, with chat and voice. Use it when the user wants to watch something together now, or plan a watch party at a set time. Without start_time the room is ready now: the first person to open room_link becomes the host (controls playback), so tell the user to open it before sharing. With start_time it returns a countdown page with "add to calendar" for guests; the room opens 15 minutes early, and organiser_link lets the user open it any time and host it. Share room_link or schedule_page with guests; keep organiser_link and organiser_key for the user only (they also change it with update_watch_party and cancel it with cancel_watch_party). The room made here is what the *_watch_party tools call a watch party — same room_code.
| Name | Type | Req | Description |
|---|---|---|---|
| start_time | string | – | Optional. ISO 8601 date-time WITH a time zone, e.g. 2026-11-07T20:00:00+08:00 (ask the user for their time zone if unknown). Omit for a room that opens now. Up to 60 days ahead. |
| title | string | – | What people will watch, e.g. "Lesson 3: Past tense". Defaults to "Watch party". |
| video_url | string | – | Optional video the room opens with. A direct video link (mp4, webm, m3u8) or a public YouTube video URL. Paid streaming services are not supported. |
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | – | Error code when ok is false. |
| ok | boolean | yes | false when the call failed; then code says why. |
| opens_at | string | – | ISO time guests can enter (15 minutes before). |
| organiser_key | string | – | Private: needed to cancel with cancel_watch_party. |
| organiser_link | string | – | Private: opens the room as host, even before it opens to guests. |
| room_code | string | – | 5-character room code. |
| room_link | string | – | Link guests open to join the room. |
| schedule_page | string | – | Countdown page with "add to calendar"; best link to share for a later party. |
| starts_at | string | – | ISO time it starts. |
No examples provided.
delete_branded_link Delete a branded link ~137
Permanently deletes a branded page made with create_branded_link; its public link and posters stop working. Needs the private edit_link (or slug and edit_key). Cannot be undone; confirm with the user first.
| Name | Type | Req | Description |
|---|---|---|---|
| edit_key | string | – | The key after #k= in the edit link. |
| edit_link | string | – | The private edit link returned by create_branded_link (…/r/<slug>/edit#k=<key>). Alternatively pass slug and edit_key. |
| slug | string | – | The page's slug (the part after /r/). Needed with edit_key when edit_link is not given. |
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | – | Error code when ok is false. |
| ok | boolean | yes | false when the call failed; then code says why. |
| slug | string | – | The deleted slug. |
No examples provided.
get_branded_link Look up a branded link ~91
Shows what a branded page (…/r/<slug>) currently says: name, description, colour, video, whether it has a logo or background, and whether people are in its room right now. Use it before changing a page or to check a slug the user mentions. Read-only; needs no key.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | The slug after /r/, or the whole public link. |
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | – | Error code when ok is false. |
| color | string | – | #rrggbb. |
| has_background | boolean | – | – |
| has_logo | boolean | – | – |
| live | boolean | – | Someone is in the room now. |
| name | string | – | Name. |
| ok | boolean | yes | false when the call failed; then code says why. |
| public_link | string | – | Public link. |
| slug | string | – | Slug. |
| tagline | string | – | One-line description. |
| video_url | string | – | Video the room opens with, if any. |
No examples provided.
get_watch_party Look up a watch party ~134
Looks up a watch party — a room made with create_watch_room, now or scheduled — by its 5-character code (from create_watch_room or from a ScreenParty link such as …/s/AB2CD or …room.html?room=AB2CD). Returns its title, start time, whether guests can enter yet and whether people are in it right now. Use it to answer "when does it start?" or "is it open?". Read-only; it never reveals who is in the room.
| Name | Type | Req | Description |
|---|---|---|---|
| room_code | string | yes | The 5-character room code, e.g. AB2CD. |
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | – | Error code when ok is false. |
| live | boolean | – | Someone is in the room now. |
| ok | boolean | yes | false when the call failed; then code says why. |
| open_to_guests | boolean | – | – |
| opens_at | string | – | ISO time guests can enter. |
| room_code | string | – | Room code. |
| room_link | string | – | Join link. |
| schedule_page | string | – | Countdown page. |
| starts_at | string | – | ISO start time. |
| title | string | – | Title of a scheduled party. |
No examples provided.
update_branded_link Change a branded link ~263
Changes the name, description, colour or video of a branded page made with create_branded_link. Pass only the fields to change; the link itself (slug) stays the same, so posters and shared links keep working. Needs the private edit_link (or slug and edit_key). Pass video_url as an empty string to remove the video. Logo and background are changed on the edit page, not here.
| Name | Type | Req | Description |
|---|---|---|---|
| color | string | – | New theme colour as #rrggbb. |
| edit_key | string | – | The key after #k= in the edit link. |
| edit_link | string | – | The private edit link returned by create_branded_link (…/r/<slug>/edit#k=<key>). Alternatively pass slug and edit_key. |
| name | string | – | New name. |
| slug | string | – | The page's slug (the part after /r/). Needed with edit_key when edit_link is not given. |
| tagline | string | – | New one-line description; empty string removes it. |
| video_url | string | – | New video, or empty string for none. A direct video link (mp4, webm, m3u8) or a public YouTube video URL. Paid streaming services are not supported. |
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | – | Error code when ok is false. |
| ok | boolean | yes | false when the call failed; then code says why. |
| public_link | string | – | Public link (unchanged). |
| slug | string | – | Slug. |
No examples provided.
update_watch_party Change a watch party ~199
Changes the start time and/or title of a watch party (a room made with create_watch_room, same room_code). The link stays the same, so invitations already sent keep working — prefer this over cancelling and creating a new one. Needs the organiser_key (or organiser_link) from create_watch_room. Guests who already added the old time to their calendar should be told to update it.
| Name | Type | Req | Description |
|---|---|---|---|
| organiser_key | string | – | The organiser_key from create_watch_room. |
| organiser_link | string | – | Alternatively, the organiser_link from create_watch_room. |
| room_code | string | – | The 5-character room code. Not needed when organiser_link is given. |
| start_time | string | – | New start: ISO 8601 date-time WITH a time zone, e.g. 2026-11-08T21:00:00+08:00. Up to 60 days ahead. |
| title | string | – | New title. |
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | – | Error code when ok is false. |
| ok | boolean | yes | false when the call failed; then code says why. |
| opens_at | string | – | ISO time guests can enter. |
| room_code | string | – | Room code (unchanged). |
| schedule_page | string | – | Countdown page (same link). |
| starts_at | string | – | ISO start time now. |
| title | string | – | Title now. |
No examples provided.
How do I install the ScreenParty MCP server?
ScreenParty is a hosted endpoint at https://screenparty.huitongdesk.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 · screenparty.huitongdesk.com
claude mcp add --transport http com-huitongdesk-screenparty-watch-together 'https://screenparty.huitongdesk.com/mcp'
What is the ScreenParty MCP server?
ScreenParty is an MCP server listed in the public MCP registry as com.huitongdesk.screenparty/watch-together. Create watch-together rooms, scheduled watch parties and branded class links. No sign-up. This page covers its hosted endpoint (https://screenparty.huitongdesk.com/mcp).
Is the ScreenParty MCP server safe to use?
ScreenParty scores 74 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 ScreenParty MCP server expose?
ScreenParty exposes 8 tools: create_watch_room, get_watch_party, update_watch_party, cancel_watch_party, create_branded_link, and 3 more. Their descriptions and schemas cost roughly 1,559 tokens of context every time the server is loaded.
Does the ScreenParty MCP server require authentication?
No. We connected to ScreenParty without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the ScreenParty MCP server still maintained?
ScreenParty 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 ScreenParty MCP server?
VerifyMCP ran 13 checks on ScreenParty, 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.