Studio Signal
NPM · @STUDIOSIGNAL/MCP-SERVER · 2 COMPONENTS · SCANNED AUG 3
AI-powered media & entertainment intelligence — research, briefs, and market data.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score →
Supply Chain Security63
- No malware found by supply-chain analysis.Pass
- CVE data not yet available for this package.Unverified
- No install/post-install scripts declared.Pass
- Dependency-health data not yet available.Unverified
Provenance & Transparency19
- Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 0 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability0
- Schema quality not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet.Unverified
Stability & Change Management0
- Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet.Unverified
Tool Coverage0
- Tool coverage not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet.Unverified
Capabilities0
- Protocol version not yet verified: we do not have a sandbox capture of the MCP handshake this version of the package performs yet.Unverified
Unverified: 4 categories
Categories scored 0 because our sandbox run of this package has not given us the schema these checks need to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until the capture succeeds. We are working through the fleet, so this normally clears without any action from you. How we score packages →
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · @studiosignal/mcp-server
claude mcp add vfxprojoe-studio-signal -- npx -y @studiosignal/mcp-server
codex mcp add vfxprojoe-studio-signal -- npx -y @studiosignal/mcp-server
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"vfxprojoe-studio-signal": {
"type": "local",
"command": [
"npx",
"-y",
"@studiosignal/mcp-server"
],
"enabled": true
}
}
} openclaw mcp add vfxprojoe-studio-signal --command npx --arg -y --arg @studiosignal/mcp-server
mcp_servers:
vfxprojoe-studio-signal:
command: "npx"
args: ["-y", "@studiosignal/mcp-server"] {
"mcpServers": {
"vfxprojoe-studio-signal": {
"command": "npx",
"args": [
"-y",
"@studiosignal/mcp-server"
]
}
}
} 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.
- 3 Aug 26 −40
- Known CVEs: partial → unverified ▼ security
- Stability: 0.20 → unverified ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Dependency health: partial → unverified ▼ functional
- Package version: 1.4.5 → 1.4.6 functional
- 2 Aug 26 +42
- Provenance: unverified → fail ▼ security
- Install scripts: unverified → pass ▲ security
- Known CVEs: unverified → partial ▲ security
- Malware scan: unverified → pass ▲ security
- Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
- Capabilities: pass → unverified ▼ functional
- Dependency health: unverified → partial ▲ functional
- Schema quality: unverified → excellent ▲ functional
- Maintenance: unverified → pass ▲ functional
- Stability: unverified → 0.20 ▲ functional
- License: unverified → pass ▲ functional
- Licence: MIT functional
- 1 Aug 26 +21
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- MCP protocol: unverified → pass ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- 31 Jul 26 −40
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 +7
No change was recorded against any check on this day. Schema Quality & AI Usability went from 0 to 28.
- 28 Jul 26 −7
- First check of Schema quality: unverified functional
- 27 Jul 26 40
First indexed and scored.
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 3 Aug 2026 · Analysed npm/@studiosignal/[email protected]
Provenance none
Ecosystem: npm · Outcome: none
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.
ask_kai ~232
Ask Kai Rivers, an AI M&E research analyst, any question about media & entertainment. Returns a full Pro research report with inline numbered citations ([1], [2], …) and a linked "Sources" list. **Speed:** Every query uses Gemini Pro + Google Search grounding. Expect **~2–4 minutes** for a cited report. When presenting the report, preserve the inline [n] markers and the Sources list. IMPORTANT: Use this tool for AD-HOC research. Examples: - "What's happening in the streaming wars?" - "Full report on Frame.io competitive positioning" - "Competitor research: Signiant vs Aspera" - "Analyze Disney's Q2 earnings" Do NOT use this for "today's brief" or "today's pre-built deep dive" — use get_daily_brief or get_deep_dive instead.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Research question for Kai. Use "competitor research: X vs Y" for head-to-head comparisons, "SWOT analysis of X" only when SWOT is requested, "X Q2 earnings" for financial analysis. |
No output schema declared.
No examples provided.
get_daily_brief ~126
Fetch TODAY's pre-built Studio Signal executive intelligence brief — a curated summary of top M&E stories, market movers, and strategic implications, generated every morning. Use this tool ONLY when the user asks for today's existing brief, such as: - "What's today's brief?" - "Give me the morning brief" - "Daily summary" / "Morning update" - "Show me the brief" Do NOT use this for research requests like "brief me on Netflix" or "give me a brief about Disney" — those are ad-hoc research and should use ask_kai instead.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_deep_dive ~134
Fetch TODAY's pre-built Studio Signal deep dive — a comprehensive analysis expanding on the morning brief's most impactful stories with strategic implications, competitive analysis, and market outlook. Use this tool ONLY when the user asks for today's existing deep dive, such as: - "What's today's deep dive?" - "Show me the deep dive" - "Pull up the deep dive" Do NOT use this when the user wants a NEW deep dive on a specific topic like "do a deep dive on Netflix" or "deep dive into Disney's strategy" — those are ad-hoc research requests and should use ask_kai instead.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_stocks ~97
Get live M&E sector stock data — prices, changes, market caps, and analyst ratings for 30+ media & entertainment companies including NFLX, DIS, CMCSA, WBD, PARA, SPOT, ROKU, and more.
| Name | Type | Req | Description |
|---|---|---|---|
| symbols | string | — | Comma-separated ticker symbols to filter (e.g., "NFLX,DIS,NVDA"). Omit to get all 30+ M&E stocks. |
No output schema declared.
No examples provided.
get_usage ~73
Check your Studio Signal API usage — calls used this period, free calls remaining from the one-time 50-call allowance, and estimated cost. Billing starts at $0.30/call with graduated volume discounts to $0.25 above 1,000 and $0.20 above 10,000 calls a month.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.