ReelRecs

warnings

mcp.reelrecs.com

Find movies and shows for tonight with current trends, mood, taste and streaming options.

https://mcp.reelrecs.com/mcpWebsiteOAuthMCP 2025-11-25v0.1.0last checked 4 Nov 2026spoke MCP on 1 of 1 check (30 days)initialize in 462 ms

Last checked 4 Nov 2026

✓Answered the MCP handshake (MCP 2025-11-25)
✓Auth detected: OAuth
✓Lists 13 tools
!1 warning
✓Spoke MCP on 1 of 1 check (30 days)

Will my client connect?

Decided from what the probe found at the endpoint, and from what each client's own documentation says it can complete. Every row carries the day that documentation was read.

✓Claude CodeConnects with setup

Neither RFC 7591 registration nor a Client ID Metadata Document is advertised, so register a client with the issuer yourself and give Claude Code the client ID.

claude mcp add --transport http --client-id <your-client-id> --client-secret --callback-port 8080 reelrecs https://mcp.reelrecs.com/mcp

Claude Code docs · read on 2026-08-30

✓Claude (claude.ai & Desktop)Connects with setup

Neither RFC 7591 registration nor a Client ID Metadata Document is advertised, so register a client with the issuer yourself and give Claude (claude.ai & Desktop) the client ID.

Settings → Connectors → Add custom connector, then paste https://mcp.reelrecs.com/mcp. Under Advanced settings, enter the OAuth Client ID and Secret the issuer gave you.

Claude (claude.ai & Desktop) docs · read on 2026-08-30

✕ChatGPTNot supported

Registering a client by hand is not a flow ChatGPT documents, and this server advertises none that it does.

ChatGPT docs · read on 2026-08-30

✓CursorConnects with setup

Neither RFC 7591 registration nor a Client ID Metadata Document is advertised, so register a client with the issuer yourself and give Cursor the client ID.

{
  "mcpServers": {
    "reelrecs": {
      "url": "https://mcp.reelrecs.com/mcp"
    }
  }
}

Cursor docs · read on 2026-08-30

✓VS Code (Copilot)Connects with setup

Neither RFC 7591 registration nor a Client ID Metadata Document is advertised, so register a client with the issuer yourself and give VS Code (Copilot) the client ID.

{
  "servers": {
    "reelrecs": {
      "oauth": {
        "clientId": "<your-client-id>"
      },
      "type": "http",
      "url": "https://mcp.reelrecs.com/mcp"
    }
  }
}

VS Code (Copilot) docs · read on 2026-08-30

How to authenticate

Checked against the endpoint by our probe on 4 Nov 2026. These are the capabilities the server advertises, not a prediction about any particular client.

Scheme	OAuth
Issuer	https://mcp.reelrecs.com
Dynamic client registration	✕Not advertised A client that cannot register itself needs credentials issued out of band before it can begin the flow.
Client ID Metadata Document	✕Not advertised
PKCE	✓S256
Grant types	authorization_code, refresh_token
Scopes	recommendations:personal, bookmarks:read, ratings:read, watchplus:read
Protected-resource metadata	✓Published (RFC 9728)
Anonymous access	Handshake succeeds; 13 tools listable
Credentials demanded in prose	✕recommend_titles, get_charts, get_watch_options, get_my_profile, recommend_for_me, get_my_ratings, get_my_bookmarks, report_recommendation_feedback These tools are listed anonymously and their own descriptions ask for an account or key, but no challenge is issued — so a client has nothing to act on and the refusal arrives as a tool error.
Documentation	https://reelrecs.com/assistants/

What the probe found

warningTools needing credentials are listed without a challenge

8 of the 13 tools listed anonymously say in their own descriptions that they need an account or a key (recommend_titles, get_charts, get_watch_options, get_my_profile, recommend_for_me, get_my_ratings, get_my_bookmarks, report_recommendation_feedback), but the endpoint issued no WWW-Authenticate challenge. The requirement is stated only in prose, so a call reaches the tool and comes back as a tool error instead of an authorization step.

No CORS headers for browser-based clients

A cross-origin preflight came back without Access-Control-Allow-Origin, so the endpoint is reachable from native clients only — code running in a web page is stopped by the browser before a request is ever sent.

13 tools usable without signing in

The server exposes a public surface before authorization: search_titles, recommend_titles, get_title_peers, get_charts, get_watch_options, get_my_profile, recommend_for_me, get_my_ratings, get_my_bookmarks, get_my_watchplus_groups, get_watchplus_context, recommend_for_group, report_recommendation_feedback.

No server card

Neither the reserved <endpoint>/server-card location nor the domain's /.well-known/ai-catalog.json describes this endpoint (SEP-2127), so a client that discovers servers by domain will not find it.

Tools

get_chartsget_my_bookmarksget_my_profileget_my_ratingsget_my_watchplus_groupsget_title_peersget_watch_optionsget_watchplus_contextrecommend_for_grouprecommend_for_merecommend_titlesreport_recommendation_feedbacksearch_titles

Contract history

4 Nov 2026v0.1.0first recorded contract

Watch this server

Save its public contract as a baseline and manage breaking-change email alerts.

Set up a watch

Route it through the gateway

Put this endpoint behind one find_tools / call_tool pair with the rest of your servers. Part of Pro.

Add to my gateway

Own this server?

Sponsor this listing

Pins it in a sponsor slot on the directory front page for 30 days, labelled Sponsored.

Status badge

Status for a README, from the last probe — cached an hour, so up to seven hours behind the endpoint. Links back to this page.

[![MCP status](https://mcpi.app/servers/reelrecs/badge.svg)](https://mcpi.app/servers/reelrecs)