Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Sleeper Hit Studio — Public Discovery

REMOTE · SLEEPERHIT.STUDIO

Browse published podcasts, video shows, and screenplays. Read-only public discovery.

0 this week 85 Trust /100

Last scanned (20 hours ago)

Scores higher than 86% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Entertainment and Games

Trust breakdown (7 categories)

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
Schema Quality & AI Usability77
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1365 tokens (~124/item across 11 items; 10 tools + 1 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 Coverage83
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 50% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 12 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
What we tested

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 →

Changelog

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.

  • 9 Nov 26 +1
    • Stability: 0.97 → pass security
  • 8 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 7 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 2 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
  • 1 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • New resource “Published shows” functional
  • 28 Oct 26 0
    • The server rewrote its instructions, which are the text every model session reads security
  • 27 Oct 26 0
    • The server rewrote its instructions, which are the text every model session reads security
Diagnostics

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://sleeperhit.studio/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=sleeperhit.studio CN=YE1,O=Let's Encrypt,C=US 4 Nov 2026 2 Feb 2027 ECDSA 256 ECDSA-SHA384 6a374e84e89da38c2881431dd9ee7e6cbce
SANs: *.sleeperhit.studio, sleeperhit.studio
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
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 sleeperhit.studio. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
studio. DS published 35741 8 Verified
sleeperhit.studio. 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

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://sleeperhit.studio/api/mcp Verified 200
http (plaintext) http://sleeperhit.studio/api/mcp HTTPS enforced 301 https://sleeperhit.studio/api/mcp
MCP tools · 10 exposed · ~457 tokens

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 →

Tool Tokens
fetch ~45

Fetch the full public discovery document for a search result by ID. Compatible with ChatGPT deep research and company knowledge.

NameTypeReqDescription
idstringyesSearch result ID returned by the search tool.

No output schema declared.

No examples provided.

find_projects ~51

List public projects for a writer. Results include project hub URLs and public asset summaries.

NameTypeReqDescription
querystring–Optional title, genre, logline, or synopsis text.
writerSlugstringyes–

No output schema declared.

No examples provided.

find_writers ~86

Search opt-in public Sleeper Hit Studio writer profiles.

NameTypeReqDescription
formatstring–Filter by public discovery format.
genrestring–Filter by public discovery genre.
limitnumber–Maximum writers to return.
querystring–Name, location, headline, summary, specialty, or genre.
specialtystring–Filter by public writer specialty.

No output schema declared.

No examples provided.

get_access_info ~53

Read what Sleeper Hit Studio can do without an account, what requires one, and the signup URL for each intent. Call this before telling a user you cannot create something here — creation lives on the separate authenticated connector.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_project_summary ~34

Get one public project summary for a writer.

NameTypeReqDescription
projectSlugstringyes–
writerSlugstringyes–

No output schema declared.

No examples provided.

get_public_pitch_assets ~29

List writer-approved public pitch deck assets for a writer.

NameTypeReqDescription
writerSlugstringyes–

No output schema declared.

No examples provided.

get_writer_profile ~31

Get a public writer profile by slug, including public projects and shared assets.

NameTypeReqDescription
slugstringyes–

No output schema declared.

No examples provided.

list_project_assets ~36

List writer-approved public share URLs for a specific project.

NameTypeReqDescription
projectSlugstringyes–
writerSlugstringyes–

No output schema declared.

No examples provided.

list_writer_assets ~28

List all writer-approved public share URLs for a writer.

NameTypeReqDescription
writerSlugstringyes–

No output schema declared.

No examples provided.

search ~64

Search opted-in public writer profiles, project summaries, and writer-approved public assets. Compatible with ChatGPT deep research and company knowledge.

NameTypeReqDescription
querystringyesSearch query for published shows, writers, projects, genres, formats, accolades, table reads, pitch assets, or trailers.

No output schema declared.

No examples provided.

Install

How do I install the Sleeper Hit Studio — Public Discovery MCP server?

Sleeper Hit Studio — Public Discovery is a hosted endpoint at https://sleeperhit.studio/api/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 · sleeperhit.studio

# add to Claude Code
claude mcp add --transport http studio-sleeperhit-public-discovery 'https://sleeperhit.studio/api/mcp'
Common questions

What is the Sleeper Hit Studio — Public Discovery MCP server?

Sleeper Hit Studio — Public Discovery is an MCP server listed in the public MCP registry as studio.sleeperhit/public-discovery. Browse published podcasts, video shows, and screenplays. Read-only public discovery. This page covers its hosted endpoint (https://sleeperhit.studio/api/mcp).

Is the Sleeper Hit Studio — Public Discovery MCP server safe to use?

Sleeper Hit Studio — Public Discovery scores 85 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 Sleeper Hit Studio — Public Discovery MCP server expose?

Sleeper Hit Studio — Public Discovery exposes 10 tools: search, fetch, find_writers, get_writer_profile, find_projects, and 5 more. Their descriptions and schemas cost roughly 457 tokens of context every time the server is loaded.

Does the Sleeper Hit Studio — Public Discovery MCP server require authentication?

No. We connected to Sleeper Hit Studio — Public Discovery without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Sleeper Hit Studio — Public Discovery MCP server still maintained?

Sleeper Hit Studio — Public Discovery 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 Sleeper Hit Studio — Public Discovery MCP server?

VerifyMCP ran 13 checks on Sleeper Hit Studio — Public Discovery, 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.